How davidegalilei/piltover works
Main Components
a) Core Server Components:
• Transport Layer Handler (handles different transport protocols)
• Authorization System
• Message Processing Engine
• TL (Type Language) Serialization System
• Session Management
• Cryptographic Components
b) External Interfaces:
• TCP Socket Interface
• WebSocket Proxy Interface
• Client Connection Handlers
[Client Layer]
• ↓ ↑
[Transport Layer]
• ↓ ↑
[Protocol Layer]
• ↓ ↑
[Core Processing Layer]
• ↓ ↑
[Storage Layer]
Component Details
a) Client Layer:
• Supported clients (Telegram Desktop, WebK, WebZ, Pyrogram, Telethon)
• Both TCP and WebSocket connection paths
b) Transport Layer:
• Different transport types (Abridged, Intermediate, Padded Intermediate, TCP Full, Obfuscated)
• WebSocket proxy component for web clients
c) Protocol Layer:
• MTProto implementation
• Authorization key generation
• RSA encryption/decryption
• Message identification and sequencing
d) Core Processing Layer:
• TL Serialization/Deserialization (JIT-based)
• Message handlers
• Update system
• Session management
e) Storage Layer (planned/future):
• Auth keys storage
• Message storage
• User data storage
• Updates storage
Implementation Details to Highlight
• Flow of the authorization process
• Where RSA key pairs are used
• Demonstrate message flow through the different transport layers
• How the JIT TL serialization works
Connection Flows
• Initial connection and transport detection
• Authorization key generation
• Normal message processing
• Update handling
Additional Elements
• Version/layer information for TL schemas
• Security checkpoints and validation steps
• Where future components will be integrated
Remember to include notes about:
• The experimental nature of the security implementation
• The JIT nature of TL serialization
• The multiple transport protocol support
• The WebSocket proxy requirement for web clients