Terminal UI for 2FAuth.
- Onboarding flow for server URL, PAT, and local password
- Server availability check during setup
- PAT stored in its own file
- Local password protected unlock screen
- Optional launcher install to your
~/.local/bin/2fauth - Password hash stored with salted PBKDF2 and base64 encoding for the hash blob
- Live list of 2FA accounts and OTP codes
uv syncuv run 2FAuth-TUIIf you want direct module run:
uv run python -m twofauth_tuiIf you install the launcher during onboarding, run:
2fauthYou can also install or reinstall the launcher later from dashboard with i
or the Install launcher button.
Data lives in your platform config dir, usually:
~/.config/2FAuth-TUI/
Files:
config.json- server URLpat.token- 2FAuth Personal Access Tokenpassword.json- local password hash record
Base64 is used only to safely store binary hash/salt bytes in JSON. It is not password protection by itself.