How freedomofpress/securedrop works
Main Components
a. User-Facing Interfaces:
• Source Interface (port 8080) - For whistleblowers
• Journalist Interface (port 8081) - For media organization staff
• Admin Interface - For system administration
b. Server Components:
• Application Server
• Apache Web Server
• Python Flask Applications
• Redis Queue Worker
• Database (SQLite/Alembic for migrations)
• Monitor Server
• OSSEC (Security monitoring)
• Postfix (Email alerts)
c. Security Components:
• Tor Hidden Services
• GPG Encryption System
• Two-Factor Authentication
• AppArmor Profiles
Key Relationships
a. Data Flow:
• Source → Tor Network → Source Interface → Encrypted Storage
• Journalist → Tor Network → Journalist Interface → Encrypted Storage
• Monitor Server → Admin Email Alerts
• Worker Processes → Database/File Operations
b. Security Boundaries:
• Network Isolation
• Encryption Boundaries
• Access Control Points
Specific Implementation Details
[Public Internet Zone]
• ↓ (Tor Network)
[Network Boundary]
• ↓
[Application Zone]
• Source Interface (Flask App)
• Journalist Interface (Flask App)
• Admin Interface
• ↓
[Storage Zone]
• Encrypted Submissions
• Database
• GPG Keys
[Monitoring Zone]
• OSSEC
• Postfix
Critical Subsystems to Highlight
• Authentication System
• Two-factor authentication
• Session management
• Encryption Pipeline
• GPG encryption for submissions
• Storage encryption
• Queue Management
• Redis for background jobs
• Worker processes
• Monitoring System
• OSSEC integration
• Alert generation
Implementation Notes
Technical details such as:
• Python/Flask backend
• SQLite database
• Redis queue
• Apache web server
• Tor hidden services
• System dependencies
• Layered visualization
• Security notation
• Clear connection routing
• Export in high resolution
• Collaborative editing