How geph-official/geph5 works
Main components
• Binaries:
– geph5-client and geph5-client-gui: The client interfaces that initiate sessions and interact with the broker. Note that the GUI client directly calls Rust protocol libraries.
– geph5-broker: The central authentication and routing server. It now exposes a JSON-RPC API (with ed25519 signatures for integrity-critical responses) and acts as the intermediary for client authentication and route establishment.
– geph5-bridge: A component that connects the client and exit by providing transport bridges using multiplexed TCP streams.
– geph5-exit: Handles the exit side of connections (similar in role to a network proxy/VPN exit point).
• Libraries: There are multiple libraries (e.g., sillad, picomux, nanorpc, nano-influxdb, arc-writer, etc.) that provide functionality, communication protocols, and networking abstractions shared across binaries.
Relationships and interactions
• Transport Mechanism: Within the bridge component (and parts of the client/VPN lock in geph5-client), highlight that data is sent over multiplexed TCP streams instead of relying on unreliable packet-based transports.
Important architectural patterns or design principles
• Config-Driven Architecture: Emphasize that the project takes a config file–driven approach rather than relying on extensive command-line parameters.
• Simplified Session Handling: Note that sessions are created and used until breakage and then restarted, rather than relying on complex “hot-swap” mechanisms.
• JSON-RPC and Ed25519 Signature Use: Explain that the broker uses a simple JSON-RPC API for communication and cryptographic measures for security-critical responses.
• Clear Separation of Concerns: The division between authentication (broker), transport bridging (bridge), final exit functionality (exit), and client logic is a core design principle.
– Workspace container dividing “Binaries” and “Libraries.”
– A separate Libraries node listing shared protocol and network libraries (for instance, sillad, picomux, nanorpc-sillad, etc.).
– From Client to Broker (session initiation and control traffic).
– From Broker to Bridge and Exit (to set up and manage routes).
• Labels for each node indicating its primary responsibilities (e.g., “Broker – Central JSON-RPC API service with session management”).