SeedPass: Secure Password Manager
SeedPass is a secure password generator and manager built on Bitcoin's BIP-85 standard. It uses deterministic key derivation to generate passwords that are never stored but can be easily regenerated when needed.
By integrating with the Nostr network, SeedPass ensures that your passwords are safe and accessible across devices.
Get StartedFeatures
- Deterministic password generation using BIP-85
- Encrypted local storage for seeds and sensitive data
- Nostr relay integration for secure backup and retrieval
- Seed/Fingerprint switching for managing multiple profiles
- Checksum verification to ensure script integrity
- Interactive TUI for managing entries and settings
How SeedPass Works
SeedPass uses Bitcoin's BIP-85 standard for deterministic password generation. This means your passwords are not stored but can be regenerated using your master seed and specific indices.
BIP-85 Derivation Tree
The BIP-85 standard allows you to derive multiple child seeds from a single master seed. Each child seed can then be used to generate secure passwords. Here's a simplified illustration:
Master_Seed ├── Child_Seed_0 │ └── Password_A ├── Child_Seed_1 │ └── Password_B ├── Child_Seed_2 │ └── Password_C └── ...
Seed/Fingerprint Switching
SeedPass allows you to manage multiple seed profiles (fingerprints). You can switch between different seeds to compartmentalize your passwords.
Nostr Relay Integration
By integrating with the Nostr network, SeedPass securely backs up your encrypted password index to Nostr relays, allowing you to retrieve your index on multiple devices without compromising security.
Checksum Verification
Built-in checksum verification ensures your SeedPass installation hasn't been tampered with.
Interactive TUI
Navigate through menus to manage entries and settings. Example:
Select an option: 1. Add Entry 2. Retrieve Entry 3. Modify an Existing Entry 4. Settings 5. Exit Enter your choice (1-5):
Roadmap
Phase 1: Core Functionality and Security Enhancements
Goal: Establish a robust foundation with individual entry management, secure seed handling, and seamless Nostr integration.
- Configuration File Management
- Individual JSON File Management
- Enhanced JSON Schema Integration
- Nostr Integration Enhancements
- Backup and Restore Index Option
- Security Enhancements
- Comprehensive Testing and Security Auditing
- Managed Users’ Data Loading
Phase 2: Enhanced Security and Data Management
Goal: Strengthen security features and improve data management capabilities with the new individual entry system.
- Advanced Data Fields and New Kinds
- Family Password Management
- Easy BIP39 Seed Generation for Various Use Cases
- Nostr Public/Private Key Pair Generation
Phase 3: Advanced CLI Functionalities
Goal: Develop a sophisticated Command-Line Interface (CLI) tailored for the individual entry system, enhancing automation and customization.
- Advanced CLI Commands for Entry Management
- Custom Relays Configuration via CLI
- Secure Clipboard Operations
Phase 4: Data Management Enhancements and Integrations
Goal: Further improve data management capabilities and integrate with other platforms using the individual entry system.
- Additional Integrations
- Scalability Enhancements
Phase 5: Documentation, Testing, and Finalization
Goal: Ensure comprehensive documentation, robust testing, and finalize the application for release with the new entry management system.
- Provide Comprehensive Documentation
- Enhance Logging and Monitoring
- Ensure Comprehensive Testing
- Prioritize Security Best Practices
Future Phases (Beyond Initial Roadmap)
Goal: Continuous improvement and feature expansion based on user feedback and emerging needs.
- Continuous Improvement and Feature Expansion
- Scalability and Performance Optimization
Disclaimer
⚠️ Disclaimer: This software was not developed by an experienced security expert and should be used with caution. There may be bugs and missing features. For instance, the maximum size of the index before the Nostr backup starts to have problems is unknown. Additionally, the security of the program's memory management and logs has not been evaluated and may leak sensitive information.