769735c4ed
Bumps [loader-utils](https://github.com/webpack/loader-utils) from 1.2.3 to 1.4.2. - [Release notes](https://github.com/webpack/loader-utils/releases) - [Changelog](https://github.com/webpack/loader-utils/blob/v1.4.2/CHANGELOG.md) - [Commits](https://github.com/webpack/loader-utils/compare/v1.2.3...v1.4.2) --- updated-dependencies: - dependency-name: loader-utils dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> |
||
|---|---|---|
| dist | ||
| src | ||
| .dockerignore | ||
| .gitignore | ||
| Dockerfile | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| screenshot.png | ||
| webpack.config.js | ||
Luzifer / webtotp
webtotp is a small web-based utility to create ad-hoc TOTP codes like the Google Authenticator would. The tool does not send any data to any service but is based fully in your browser.
My specific usecase for this is I do have accounts which OTP secrets are stored outside of my TOTP generator as usually I don't need to access those accounts and if I would add those secrets to my TOTP generator I would have a lot more entries in it. So I do store the secrets in a safe place and needed a convenient generator to generate single OTP tokens from them.
You can even send the page with the OTP code to someone by appending the secret to the URL in the hash part:
https://webtotp.example.com/#mysecret
As long as you make sure it is in the hash-part (behind the #) the browser will not send the secret to the server but keep it locally in the browser. When sending the URL containing the secret make sure you are using a secured transport like OTS to ensure the chat / email provider is not able to fetch those secrets from the URL.
Installation
Either use the provided Docker image:
# docker run --rm -ti -p 3000:3000 luzifer/webtotp
Or compile the code yourself and just put the generated files somewhere:
# npm ci && npm run build
# tree dist
dist
├── app.js
└── index.html
0 directories, 2 files