How evilsocket/opensnitch works
Main Components Identification
The system consists of three major components that should be prominently featured:
a) Daemon (Core Component):
• Subcomponents:
• Firewall Engine (nftables/iptables)
• Process Monitor (eBPF/audit)
• DNS Monitor
• Connection Manager
• Rules Engine
b) UI Component:
• Connection to daemon via gRPC
• Features:
• Statistics Display
• Rules Editor
• Firewall Configuration
• Multi-node Management
c) eBPF Programs:
• At the bottom
• Connection to kernel space
• Monitoring capabilities
Interaction Flows
• Network traffic flow through the firewall
• Communication between UI and daemon (gRPC)
• eBPF programs interaction with kernel
• Process monitoring flow
• Rules enforcement path
Component Details
For each major component, include:
a) Daemon:
• Core Engine
• * Connection Handling
• * Rule Processing
• * Event Logging
• Firewall Backend
• * NFTables/IPTables Integration
• * Rule Management
• Monitoring Systems
• * Process Monitor
• * Network Monitor
• * DNS Monitor
b) UI:
• User Interface
• * Interactive Prompts
• * Statistics
• * Rule Management
• * System Configuration
• Plugin System
• * Virus Total Integration
• * Custom Extensions
c) eBPF Programs:
• Kernel Probes
• * Process Monitoring
• * Network Tracking
• * DNS Monitoring
External Interactions
Connections to:
• System Firewall
• Network Stack
• Logging Systems
• External Services (optional)
Technical Details
• Protocols Used (gRPC, netlink, etc.)
• Data Flow Types
• Component Types
• Security Boundaries
Architectural Patterns
Following patterns:
• Client-Server Architecture (UI-Daemon)
• Event-Driven System
• Plugin Architecture
• Multi-node Support
This architecture should emphasize OpenSnitch's role as a security tool while showing its extensibility and monitoring capabilities.