A secure AES-GCM encryption utility with user-friendly features
Project description
secure-string-cipher
A security-focused AES-256-GCM encryption CLI tool with passphrase vault and modern cryptographic defaults.
Features
- AES-256-GCM encryption for text and files with authenticated encryption
- Argon2id key derivation – memory-hard, GPU/ASIC resistant
- Key commitment scheme – prevents partitioning oracle attacks
- Key-file support – use any file as encryption key via
--key-file(SHA-256 → Argon2id) - OS Keychain integration – store vault in macOS Keychain, Windows Credential Vault, or Linux Secret Service
- Hidden password input – passwords hidden in interactive terminals, visible for scripts/tests
- Inline passphrase generation – type
/genat any password prompt - Encrypted passphrase vault with HMAC-SHA256 integrity verification
- Secure memory handling via libsodium (PyNaCl) when available
- Timing-safe operations – constant-time comparisons prevent side-channel attacks
- Rate limiting – exponential backoff on failed decrypt/vault attempts
- Secure shred – multi-pass overwrite file deletion
- Chunked file streaming (256 KiB) for low memory usage
- Automatic vault backups (last 5 kept)
Documentation
- API Reference — Complete programmatic API documentation
- Keychain Backend — OS keychain integration guide
- Developer Guide — Development workflow and tooling
- Contributing — Contribution guidelines
- Security Policy — Supported versions and vulnerability reporting
- Cryptographic Design — Design document for security auditors
- Dependency Audit — Supply-chain security audit report
- Changelog — Release history
Quick Start
# Install from PyPI
pip install secure-string-cipher
# Run interactive CLI
ssc start
# Or use non-interactive CLI
ssc --help
Installation
# Recommended: install with pipx
pipx install secure-string-cipher
# Or with pip
pip install secure-string-cipher
# Or from source (dev/install with uv)
git clone https://github.com/TheRedTower/secure-string-cipher.git
cd secure-string-cipher
uv sync --extra dev --locked
# Run tooling with the locked environment
uv run --locked ssc --help
Requires Python 3.12+
Usage
Non-Interactive CLI (ssc)
For scripting and automation, use the ssc command:
# Encrypt text
ssc encrypt -t "Secret message"
# Encrypt a file
ssc encrypt -f document.pdf
# Encrypt using a key file
ssc encrypt -f document.pdf --key-file /path/to/key.pem
# Decrypt a file (restores original filename by default)
ssc decrypt -f document.pdf.enc
# Decrypt with an explicit output path
ssc decrypt -f document.pdf.enc --output document.pdf
# Decrypt without restoring the stored filename
ssc decrypt -f document.pdf.enc --no-restore-filename
# Decrypt using a vault password
ssc decrypt -f document.pdf.enc --vault my-server
# Decrypt using a key file
ssc decrypt -f document.pdf.enc --key-file /path/to/key.pem
# Store a password in vault
ssc store my-server
# Auto-generate and store a password
ssc store backup-key --generate
# Vault management
ssc vault list
ssc vault delete old-key
ssc vault export backup.json
ssc vault import backup.json # validates header and integrity before replacing
Exit codes: 0=success, 1=input error, 2=auth error, 3=vault error, 4=file error
Security: Passwords are never passed via command line arguments (prevents shell history exposure). All passwords are prompted interactively or retrieved from the vault.
Interactive CLI (ssc start)
For interactive use, run:
ssc start
You'll see this menu:
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ AVAILABLE OPERATIONS ┃
┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ ┃
┃ TEXT & FILE ENCRYPTION ┃
┃ ┃
┃ [1] Encrypt Text -> Encrypt a message (base64) ┃
┃ [2] Decrypt Text -> Decrypt an encrypted message ┃
┃ [3] Encrypt File -> Encrypt a file (creates .enc) ┃
┃ [4] Decrypt File -> Decrypt an encrypted file ┃
┃ ┃
┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ PASSPHRASE VAULT (Optional) ┃
┃ ┃
┃ [5] Generate Passphrase -> Create random password ┃
┃ [6] Store in Vault -> Save passphrase securely ┃
┃ [7] Retrieve from Vault -> Get stored passphrase ┃
┃ [8] List Vault Entries -> View all stored labels ┃
┃ [9] Manage Vault -> Update, delete, export ┃
┃ ┃
┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ SECURITY TOOLS ┃
┃ ┃
┃ [10] Secure Shred -> Permanently delete a file ┃
┃ [11] Use Key File -> Encrypt/decrypt w/ key file ┃
┃ ┃
┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ [0] Exit -> Quit application ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
Choose an option and follow the prompts.
Quick Passphrase Generation
When prompted for a password during encryption, you can type /gen (or /generate or /g) to instantly generate a strong passphrase:
Enter passphrase: /gen
🔑 Auto-Generating Secure Passphrase...
✅ Generated Passphrase:
8w@!-@_#M)wF,Qn(ms.Uv+3z
Entropy: 155.0 bits
💾 Store this passphrase in vault? (y/n) [n]: y
Enter a label for this passphrase: backup-2025
Enter master password to encrypt vault: ••••••••••••
✅ Passphrase 'backup-2025' stored in vault!
✅ Using this passphrase for current operation...
Generated passphrases have 155+ bits of entropy and can be stored directly in the encrypted vault.
Passphrase Vault
The vault stores passphrases encrypted with your master password at ~/.secure-cipher/passphrase_vault.enc:
- Generate & store – Option 5 or
/genduring encryption - Manual storage – Option 6 for existing passphrases
- Retrieve/manage – Options 7-9 for lookup, listing, and deletion
All vault operations use HMAC integrity verification and maintain automatic backups.
OS Keychain Integration
Optionally store your vault in the OS keychain for added security:
# Existing pipx install: add keychain support to the pipx venv
pipx inject secure-string-cipher keyring
# New pipx install with keychain support
pipx install 'secure-string-cipher[keychain]'
# Or for a normal pip/venv install
python -m pip install 'secure-string-cipher[keychain]'
# Migrate existing vault to keychain
ssc vault migrate --to keychain
# Migrate back to file if needed
ssc vault migrate --to file
See docs/KEYCHAIN.md for full setup instructions per platform.
Docker
Use the pre-built image (Python 3.14-alpine based):
# Pull and run
docker pull ghcr.io/theredtower/secure-string-cipher:latest
docker run --rm -it ghcr.io/theredtower/secure-string-cipher:latest
# Or with Docker Compose
git clone https://github.com/TheRedTower/secure-string-cipher.git
cd secure-string-cipher
docker compose up -d
docker compose exec cipher ssc start
To encrypt files in your current directory:
docker run --rm -it \
-v "$PWD:/data" \
ghcr.io/theredtower/secure-string-cipher:latest
With persistent vault and backups:
docker run --rm -it \
-v "$PWD/data:/data" \
-v "$PWD/vault:/vault" \
-v "$PWD/backups:/backups" \
ghcr.io/theredtower/secure-string-cipher:latest
Image details: ~65MB Alpine-based, runs as non-root (UID 1000), network-isolated.
Programmatic API
Use secure-string-cipher as a library in your Python projects:
Text Encryption
from secure_string_cipher import encrypt_text, decrypt_text
# Encrypt a message
ciphertext = encrypt_text("Secret message", "MySecurePass123!")
print(ciphertext) # Base64-encoded string
# Decrypt it back
plaintext = decrypt_text(ciphertext, "MySecurePass123!")
print(plaintext) # "Secret message"
File Encryption
from secure_string_cipher import encrypt_file, decrypt_file
# Encrypt a file (explicit output path)
encrypt_file("document.pdf", "document.pdf.enc", "MySecurePass123!")
# Decrypt it (explicit output path)
output_path, metadata = decrypt_file("document.pdf.enc", "document.pdf", "MySecurePass123!")
File operations refuse symlinked inputs/outputs (except system-managed paths like /var) to prevent path hijacking.
Passphrase Generation
from secure_string_cipher import generate_passphrase
# Generate a 24-character passphrase (155+ bits entropy)
passphrase = generate_passphrase(length=24)
print(passphrase)
Vault Operations
from secure_string_cipher import PassphraseVault
# Create or open vault
vault = PassphraseVault()
# Store a passphrase
vault.store_passphrase("my-server", "MySecurePass123!", master_password="VaultMaster456!")
# Retrieve it
password = vault.retrieve_passphrase("my-server", master_password="VaultMaster456!")
# List all labels (requires master password)
labels = vault.list_labels(master_password="VaultMaster456!")
# Update an entry
vault.update_passphrase("my-server", "NewPass789!", master_password="VaultMaster456!")
# Delete an entry
vault.delete_passphrase("my-server", master_password="VaultMaster456!")
Security Utilities
from secure_string_cipher import (
check_password_strength,
constant_time_compare,
has_secure_memory,
)
# Validate password strength
is_strong, issues = check_password_strength("weak")
if not is_strong:
print(f"Password issues: {issues}")
# Constant-time comparison (prevents timing attacks)
if constant_time_compare(user_input, stored_hash):
print("Match!")
# Check if libsodium secure memory is available
if has_secure_memory():
print("Using libsodium for secure memory zeroing")
Security
| Component | Implementation | Details |
|---|---|---|
| Encryption | AES-256-GCM | Authenticated encryption, 128-bit tags |
| Key Derivation | Argon2id | 64MB memory, 3 iterations, parallelism 4 |
| Key Commitment | HMAC-SHA256 | Prevents partitioning oracle attacks |
| Vault Integrity | HMAC-SHA256 | Detects tampering before decryption |
| Memory Security | libsodium | sodium_memzero() via PyNaCl |
| Timing Safety | Constant-time | All password/hash comparisons |
| Rate Limiting | Exponential backoff | Active on vault unlock, text decrypt, and file decrypt |
| Vault Import | SSCVAULT validation | Header, hex salt, and HMAC separators verified; 0o600 enforced |
Additional protections: Path traversal prevention, symlink attack detection, atomic writes, user-only file permissions (600), 12-character minimum password with complexity requirements.
Password input: When running interactively, passwords are hidden (using getpass). When stdin is piped or redirected (scripts, automation, tests), passwords are visible. This allows both secure interactive use and scriptable automation.
Python memory limitations: Even with libsodium, Python strings are immutable and GC may copy objects. Use has_secure_memory() to check libsodium availability.
Development
git clone https://github.com/TheRedTower/secure-string-cipher.git
cd secure-string-cipher
uv sync --extra dev --locked
# Run checks with the locked environment
uv run --locked ruff check src tests
uv run --locked ruff format --check src tests
uv run --locked mypy src
uv run --locked pytest tests/ --cov=secure_string_cipher --cov-report=xml --cov-fail-under=85
See DEVELOPER.md for detailed development workflow and CONTRIBUTING.md for contribution guidelines.
License
MIT License. See LICENSE for details.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file secure_string_cipher-1.3.0.tar.gz.
File metadata
- Download URL: secure_string_cipher-1.3.0.tar.gz
- Upload date:
- Size: 255.4 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
6902be7cd74b639cfdff125c0e2afaadf1b00a1703c5e50007c108836fa22aa7
|
|
| MD5 |
a71f9e00bf3873ff930f75da99341a25
|
|
| BLAKE2b-256 |
69ffe62f78d8bd809f8d31abb6587d741e0b0b8eb019be035490b7865fa46c9c
|
Provenance
The following attestation bundles were made for secure_string_cipher-1.3.0.tar.gz:
Publisher:
release.yml on TheRedTower/secure-string-cipher
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
secure_string_cipher-1.3.0.tar.gz -
Subject digest:
6902be7cd74b639cfdff125c0e2afaadf1b00a1703c5e50007c108836fa22aa7 - Sigstore transparency entry: 1738426795
- Sigstore integration time:
-
Permalink:
TheRedTower/secure-string-cipher@f7ff04c4d5a0adc0cbdc3cb841d5048f2f14dcac -
Branch / Tag:
refs/tags/v1.3.0 - Owner: https://github.com/TheRedTower
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@f7ff04c4d5a0adc0cbdc3cb841d5048f2f14dcac -
Trigger Event:
push
-
Statement type:
File details
Details for the file secure_string_cipher-1.3.0-py3-none-any.whl.
File metadata
- Download URL: secure_string_cipher-1.3.0-py3-none-any.whl
- Upload date:
- Size: 72.3 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
cedc0052302b4a46619557bea8f88a456295845c2bc5439acd240dcf33f7b10a
|
|
| MD5 |
d9c5ae509c8c2739e8aaa45feb48f82b
|
|
| BLAKE2b-256 |
32e8591ddfda0092102b122f3ccb546ab3caee80cb84f05e882233231a32275d
|
Provenance
The following attestation bundles were made for secure_string_cipher-1.3.0-py3-none-any.whl:
Publisher:
release.yml on TheRedTower/secure-string-cipher
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
secure_string_cipher-1.3.0-py3-none-any.whl -
Subject digest:
cedc0052302b4a46619557bea8f88a456295845c2bc5439acd240dcf33f7b10a - Sigstore transparency entry: 1738426845
- Sigstore integration time:
-
Permalink:
TheRedTower/secure-string-cipher@f7ff04c4d5a0adc0cbdc3cb841d5048f2f14dcac -
Branch / Tag:
refs/tags/v1.3.0 - Owner: https://github.com/TheRedTower
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@f7ff04c4d5a0adc0cbdc3cb841d5048f2f14dcac -
Trigger Event:
push
-
Statement type: