How beac0n/ruroco works
Main Components
a) Client-side Components:
• CLI Client (client)
• GUI Client (client_ui)
• RSA Key Management System
• Configuration Management
b) Server-side Components:
• UDP Server (server)
• Command Executor (commander)
• Configuration System
• Security Components (Blocklist, Validation)
Architectural Layers
1. Client Layer (Local Host)
2. Network Layer
3. Server Layer (Remote Host)
Detailed Component Breakdown
Client Layer:
• UI Components
• CLI Interface
• Slint-based GUI (src/ui/*.slint)
• Client Core
• Command Encoder
• RSA Encryption
• Configuration Manager
• Key Management
• Private/Public Key Generation
• Key Storage
Server Layer:
• UDP Server
• Packet Receiver
• RSA Decryption
• Validation Logic
• Blocklist Management
• Commander Service
• Command Executor
• Permission Management
• Configuration Parser
Data Flow Representation
1. Client → Server
• Encrypted UDP packets
• Command data
• Timestamp
• IP information
2. Server → Commander
• Validated command names
• Execution context
Security Components Highlight
• RSA Encryption/Decryption
• Blocklist System (replay protection)
• IP Validation
• Minimal Rights Management
• Command Restriction System
Specific Implementation Details
Technical specifications:
• UDP Communication
• Systemd Integration
• Fail2ban Integration
• Configuration Format (TOML)
• Yellow highlights: Configuration elements
Component Relationships
Key relationships:
Client ─(UDP)→ Server ─(Unix Socket)→ Commander
• (Config)→ Local Config
Server ←─────┘