How domingues/vortex works
Key Components to Include:
Client Layer
• Sub-components:
• Key Management (RSA keys)
• Message Encryption/Decryption
• User Interface
• Transport Adapter
Transport Layer (show both options)
• PostgreSQL Transport
• PostgreSQL Database (with messages table)
• WebSocket Transport
• WebSocket Server (websocket-server.py)
File System Components
• Configuration Files:
• known_users (public keys storage)
• known_rooms (room definitions)
• id_rsa.pub (user's public key)
• id_rsa (user's private key)
Connection Types
• Double lines: Configuration/setup relationships
Specific Instructions:
Client Layer
• [Vortex Client]
• [Key Management]
• [E2EE Module]
• [UI Component]
• [Transport Adapter]
• [Transport Adapter]
• [PostgreSQL Connection] --> [PostgreSQL Database]
• [WebSocket Connection] --> [WebSocket Server]
File System Integration
• [Configuration Files]
• known_users
• known_rooms
• id_rsa.pub
• id_rsa
Data Flow
• Client → Encryption → Transport → Storage
• Storage → Transport → Decryption → Client
Important Elements to Highlight:
Transport Agnosticism
• How the client can switch between PostgreSQL and WebSocket
• Use a switch/multiplexer symbol between transport options
Security Components
• E2EE encryption/decryption points
• Management flow
• Where public/private keys are used
Room Management
• How room configurations are loaded and managed
• Multi-user message distribution
Additional Notes:
• Key exchange process
• Message sending flow
• Message receiving flow
Remember to indicate that this is a proof of concept and include a note about the unaudited status of the security implementation.