How hattorius/cipherdrop works
Main Components
a. Client-Side (Frontend)
• File Upload Interface
• Client-Side Encryption Layer
• File Download Interface
b. Backend Server (Rust)
• HTTP Server Layer
• Route Handlers
• File Processing System
• Encryption Layer
c. Storage Systems
• PostgreSQL Database
• S3 Storage (Multiple Buckets)
d. External Services
• Tor Network Integration (for .onion access)
Key Relationships to Highlight
a. Double Encryption Flow:
• Client-side encryption
• Server-side encryption
• Private key/nonce retention on client
b. Storage Flow:
• File upload path
• Database metadata storage
• S3 storage distribution
Specific Implementation Details
[Client Browser] --> [Frontend (Static Files)]
• index.html
• CSS/JS files
• Client-side encryption
[Frontend] <--> [Backend Server (Rust)]
• Routes (/upload, /download, etc.)
• File processing
• Secondary encryption
[Backend Server] <--> [PostgreSQL Database]
• File metadata
• S3 bucket configurations
[Backend Server] <--> [S3 Storage]
• Multiple buckets
• Encrypted file storage
Important Architectural Aspects to Emphasize
a. Security Flow:
• Client-side encryption (first layer)
• Server-side encryption (second layer)
• Key management (client-side only)
b. Data Flow:
• File upload path
• File download path
• Metadata management
c. Storage Architecture:
• Database schema (files, s3_buckets, file_to_bucket tables)
• S3 bucket distribution
Additional Notes
• A section showing the Docker containerization
• Separation between development and production environments
• Diesel ORM integration with PostgreSQL
• Migration system