🛡️ Desktop-2FA

A secure, offline two-factor authentication (2FA) manager for desktop environments. Built with Python, featuring strong encryption and no cloud dependencies.

🌐 Landing Page: desktop-2fa.org

✨ Features

📸 Screenshots

Adding a new TOTP entry interactively

Generating a TOTP code for an entry

Renaming an entry with duplicate detection

Viewing version info and listing all entries

🚀 Quick Start

Installation

pip install desktop-2fa

Verify installation:

python -c "import desktop_2fa; print(desktop_2fa.__version__)"
# Output: 0.8.2

Basic Usage

# Initialize a new vault
d2fa vault init

# Add a new TOTP token
d2fa add GitHub GitHub JBSWY3DPEHPK3PXP

# List all entries
d2fa list

# Generate a code
d2fa code GitHub

Choose a vault file for any command with --vault, or set DESKTOP_2FA_VAULT to select one by default. An explicit --vault takes precedence over the environment variable; without either, the default remains ~/.desktop-2fa/vault.

# Use a separate vault for this command
d2fa --vault ./development-vault list

# Show the currently selected vault path
d2fa vault path

Non-Interactive Usage

# Provide password via command line
d2fa --password mypassphrase add GitHub GitHub JBSWY3DPEHPK3PXP

# Provide password via file
d2fa --password-file /path/to/passphrase.txt add GitHub GitHub JBSWY3DPEHPK3PXP

📁 Vault Lifecycle

The vault is an encrypted storage file located by default at ~/.desktop-2fa/vault. A custom path can be selected with --vault or DESKTOP_2FA_VAULT.

Vault Creation

When a command requires a vault and none exists:

1. The CLI prompts for a new password (interactive mode) or requires --password/--password-file (non-interactive mode)
2. An empty encrypted vault is created
3. A confirmation message is always printed: Vault created at <path>

Vault Loading

When a command requires a vault and it exists:

1. The CLI prompts for the existing password (interactive mode) or requires credentials (non-interactive mode)
2. The vault is decrypted and loaded
3. If the password is invalid, the CLI exits with typer.Exit(1)

Duplicate Entry Handling

The rename command enforces deterministic behavior when multiple entries match the target name:

• If multiple entries match the provided name (issuer or account_name), the rename is aborted
• Error message: Error: Multiple entries named '<name>' exist. Operation aborted. Resolve duplicates first.
• No entry is renamed in this case
• This check occurs before any mutation

📖 CLI Commands

Core Commands

Vault Management

Global Options

The --vault option takes precedence over DESKTOP_2FA_VAULT. When neither is provided, Desktop-2FA uses ~/.desktop-2fa/vault. The --json, --raw, --quiet, --copy, and --copy-only options belong to d2fa code; --force is available on vault initialization and import commands.

🔒 Security

The vault uses:

• AES-256-GCM for authenticated encryption
• Argon2id for key derivation (time_cost=4, memory_cost=128MiB, parallelism=2)
• zxcvbn for password strength evaluation
• Versioned header for forward compatibility

Every command requires explicit password authentication. No session-based access.

Password Strength Evaluation

Desktop-2FA uses zxcvbn to evaluate password strength when creating or changing vault passwords:

• Score 0-2 (Weak): Easily guessable passwords (e.g., "password123")
• Score 3-4 (Strong): Resistant to common attacks (recommended)

Examples:

• ❌ Weak: password, 123456, qwerty, admin2024
• ✅ Strong: Battery-Horse-Staple-Correct, Mountain@River*2024, MySecureVault#42

Configuration (~/.config/d2fa/config.toml):

[security]
# Require strong passwords (score >= 3)
reject_weak_passwords = false  # warn but allow | true: reject weak passwords

When reject_weak_passwords = false:

• Weak passwords trigger a yellow warning
• User is prompted to confirm continuation
• Password acceptance is non-blocking

When reject_weak_passwords = true:

• Weak passwords are rejected immediately
• Command exits with error
• User must choose a stronger password

Backward Compatibility: If you have min_password_entropy set in your config (legacy option), it is recognized and treated as equivalent to requiring zxcvbn score >= 3.

Security Hardening (v0.8.0)

Version 0.8.0 maintains all previous security hardening from v0.7.3 and introduces modular architecture for better code isolation:

• Empty passwords are immediately rejected with a clear error message
• Permission errors are distinguished from missing vault files
• No Python stack traces are shown to users
• User-friendly error messages for filesystem permission issues
• Modular design separates CLI and core cryptographic components for enhanced security boundaries
• zxcvbn-based password strength evaluation (new in v0.8.0)

📚 Documentation

🧪 Testing

pytest tests/              # Run all tests
pytest --cov=src/desktop_2fa  # Run with coverage

🏗️ Project Structure

src/desktop_2fa/
├── app/           # Application components
├── cli/           # Command-line interface
├── crypto/        # Encryption utilities
├── totp/          # TOTP generation
├── ui/            # User interface components
├── vault/         # Vault management
└── utils/         # Utilities

📄 License

Apache License 2.0. See LICENSE file.

👤 Author

Łukasz Perek

🏆 Sponsorship

desktop‑2fa is supported through the Kilo OSS Sponsorship Program.

📧 Contact

For questions or support, contact us at contact@desktop-2fa.org

💖 Support the Project

Desktop‑2FA is an independent open‑source tool built with a focus on autonomy, transparency, and offline security. If you find it useful and want to support ongoing development, you can do so through the platforms below:

• Ko‑fi: https://ko-fi.com/lukaszperek
• Buy Me a Coffee: https://buymeacoffee.com/lukaszperek
• AirTM: https://airtm.me/lukper