How aironou/master-password works
Main Components
a. Core Algorithm Layer:
• Located in platform-independent/c/core
• Represents the central password generation algorithm
• Algorithm versions (v0-v3)
b. Platform-Specific Implementations:
• iOS/macOS (platform-darwin)
• Android (platform-android)
• Java GUI (platform-independent/java/gui)
• Web Interface (platform-independent/web)
• CLI Interface (platform-independent/c/cli)
c. Data Management Layer:
• Model components (platform-independent/java/model)
• Data persistence
• User preferences storage
Architecture Representation
┌─────────────────────── User Interfaces ───────────────────────┐
• ┌─────┐ ┌──────┐ ┌───────┐ ┌─────┐ ┌────────────┐ │
• iOS │ │macOS │ │Android│ │ Web │ │Java Desktop│ │
• ┬──┘ └───┬──┘ └───┬───┘ └──┬──┘ └─────┬──────┘ │
• ┼────────────┼────────┼──────────┼───────────┼───────────┘
┌─────┼────────────┼────────┼──────────┼───────────┼───────────┐
• Platform-Specific Implementations │ │
• ┼────────┼──────────┼───────────┘ │
• Native Bridges and JNI Interfaces │
• ┬───────────────────────────────┘
┌─────────────────────────────┼───────────────────────────────┐
• Core Password Generation Algorithm │
• ┌─────────────┐ ┌────────────────┐ ┌──────────────┐ │
• Algorithm V0-3│ │Crypto Services │ │Type Templates│ │
• ┘ └────────────────┘ └──────────────┘ │
• ┘
Key Elements to Highlight
• Blue: User Interface components
• Green: Core algorithm components
• Yellow: Platform-specific implementations
• Gray: Supporting services
b. Connection Types:
Additional Details
Annotations for:
• Security boundaries
• Data persistence locations
• Cross-platform communication channels
• Algorithm version compatibility
Implementation Notes
• Relationship between the C core (platform-independent/c/core) and platform-specific implementations
• Shared model layer (platform-independent/java/model)
• Test coverage and validation paths
• Build and deployment pipelines
Architectural Patterns to Emphasize
• Core algorithm isolation
• Platform abstraction layers
• Cross-platform compatibility
• Security boundaries
• Data persistence strategies
Remember to include a note about the project's transition to Spectre, indicating this as a historical reference architecture that's being modernized in the new implementation.