EncryptedChat
End-to-end encrypted messenger for Android and Windows
What it is about
Every device generates an X25519 key pair during registration. The private key stays in the device's secure storage, only the public key reaches the server. For each message a fresh key is derived via ECDH and HKDF-SHA256, and the content is encrypted with ChaCha20-Poly1305.
The server handles registration, key directory, SignalR relay and attachments — but only ever sees ciphertext. Delivered messages are removed server-side; the offline queue holds them only until delivery. Images are compressed on the client and uploaded separately encrypted.
The limits of the first version are documented rather than glossed over: no double ratchet, and therefore no forward secrecy. A shared project keeps the DTOs of app and server in sync.
Highlights
- X25519 ECDH, HKDF-SHA256 and ChaCha20-Poly1305 as AEAD
- SignalR relay with an offline queue that empties after delivery
- Encrypted image attachments, compressed on the client
- Three projects: MAUI client, ASP.NET Core server and shared DTOs
Screenshots
Screenshots are on their way.