WinHello-Crypto
Secure AWS credential storage and file encryption using Windows Hello biometric authentication.
Quick Start
Install
pip install winhello-crypto
AWS Credentials Manager
# Store AWS credentials
aws-hello-creds set myprofile --access-key AKIA... --secret-key secret123
# Use stored credentials
aws-hello-creds get myprofile
# List all profiles
aws-hello-creds list
# Export as environment variables
aws-hello-creds export myprofile
File Encryption
# Encrypt a file
winhello-crypto encrypt myfile.txt
# Decrypt a file
winhello-crypto decrypt myfile.txt.enc
AWS Credentials Manager Commands
Basic Operations
# Store credentials
aws-hello-creds set <profile> --access-key <key> --secret-key <secret> [--session-token <token>] [--region <region>]
# Retrieve credentials
aws-hello-creds get <profile> [--format json|env|ini]
# List all profiles
aws-hello-creds list [--format table|json]
# Delete credentials
aws-hello-creds delete <profile>
# Check if profile exists
aws-hello-creds exists <profile>
Advanced Operations
# Backup all credentials to encrypted file
aws-hello-creds backup --file backup.enc
# Restore credentials from backup
aws-hello-creds restore --file backup.enc
# Rotate credentials (requires AWS CLI configured)
aws-hello-creds rotate <profile>
# Export as environment variables
aws-hello-creds export <profile> [--shell bash|powershell|cmd]
# Copy profile
aws-hello-creds copy <source> <destination>
# Update existing profile
aws-hello-creds update <profile> [--access-key <key>] [--secret-key <secret>] [--session-token <token>] [--region <region>]
File Operations
# Encrypt file with profile credentials
aws-hello-creds encrypt-file <profile> <input-file> [--output <output-file>]
# Decrypt file with profile credentials
aws-hello-creds decrypt-file <profile> <input-file> [--output <output-file>]
File Encryption Commands
# Encrypt file
winhello-crypto encrypt <input-file> [--output <output-file>]
# Decrypt file
winhello-crypto decrypt <input-file> [--output <output-file>]
# Verify integrity
winhello-crypto verify <encrypted-file>
Use Cases
Development Workflows
# Set up dev environment
aws-hello-creds set dev --access-key AKIA... --secret-key secret123 --region us-west-2
aws-hello-creds export dev --shell powershell
# Switch to production
aws-hello-creds export prod --shell powershell
CI/CD Integration
# Backup before deployment
aws-hello-creds backup --file pre-deploy-backup.enc
# Restore if needed
aws-hello-creds restore --file pre-deploy-backup.enc
Secure File Sharing
# Encrypt sensitive files
winhello-crypto encrypt config.json
winhello-crypto encrypt database-backup.sql
# Share encrypted files safely
# Recipients need Windows Hello to decrypt
Security Features
- Windows Hello Integration: Uses biometric authentication (fingerprint, face, PIN)
- AES-256-GCM Encryption: Military-grade encryption for stored credentials
- No Plain Text Storage: All credentials encrypted at rest
- Secure Key Derivation: PBKDF2 with high iteration count
- Memory Protection: Sensitive data cleared from memory after use
Requirements
- Windows 10/11 with Windows Hello enabled
- Python 3.7+
- Biometric device (fingerprint reader, camera) or PIN set up
Troubleshooting
Windows Hello Not Available
Error: Windows Hello is not available on this device
Solution: Enable Windows Hello in Settings > Accounts > Sign-in options
Authentication Failed
Error: User verification failed
Solution:
- Ensure biometric device is working
- Try using PIN if biometric fails
- Check Windows Hello is enabled for apps
Profile Not Found
Error: Profile 'myprofile' not found
Solution: Use aws-hello-creds list to see available profiles
Permission Denied
Error: Access denied to Windows Credential Manager
Solution: Run as administrator or check Windows Credential Manager permissions
Development
# Install development dependencies
pip install -e ".[dev]"
# Run tests
pytest
# Run security checks
bandit -r .
safety check
# Format code
black .
License
Apache License 2.0 - see LICENSE for details.
Metadata
Release files for winhello-crypto 2.1.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| winhello_crypto-2.1.9.tar.gz | 61.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| winhello_crypto-2.1.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 106.6 kB
Release files / winhello_crypto-2.1.9.tar.gz
| Download URL | winhello_crypto-2.1.9.tar.gz |
|---|---|
| Size | 61.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0671a769d503bd16296b732a0f4fbe82f6b05f6459e0daa99227932dd84b3d1
|
|
BLAKE2b-256 checksum How to use checksums |
6d27ff74ede319df7a4d884a8ab5ce8b164a475fd2346436e9d714961de391ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 6, 2025.
Transparency logRelease files / winhello_crypto-2.1.9-py3-none-any.whl
| Download URL | winhello_crypto-2.1.9-py3-none-any.whl |
|---|---|
| Size | 44.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f30ac31df82d56871e862e50f09e458bccce13844172342757b1c8d263d30679
|
|
BLAKE2b-256 checksum How to use checksums |
c504d33ec6551d3f8faa1242e909cb096a3bcbfc4bdbbbc6cb19c1bf40d48b4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 6, 2025.
Transparency log