Re Implementing End To End Encryption For Messaging

---
name: re-implementing-end-to-end-encryption-for-messaging
description: End-to-end encryption (E2EE) ensures that only the communicating parties can read messages, with no intermediary (including the server) able to decrypt them.
domain: re
category: cryptography
hide: true
license: Apache-2.0
metadata:
  manifest_entry: src/corpus/re-implementing-end-to-end-encryption-for-messaging/SKILL.md
---
# Implementing End-to-End Encryption for Messaging

## Overview

End-to-end encryption (E2EE) ensures that only the communicating parties can read messages, with no intermediary (including the server) able to decrypt them. This skill implements a simplified version of the Signal Protocol's Double Ratchet algorithm, using X25519 for key exchange, HKDF for key derivation, and AES-256-GCM for message encryption.


## When to Use

- When deploying or configuring implementing end to end encryption for messaging capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation

## Common Misconfigurations & Verification

- **No forward secrecy:** encrypting every message under one long-term X25519 shared secret means a single key compromise decrypts the entire history. Implement the Double Ratchet so each message uses a fresh chain key, and **delete each message key immediately after use**.
- **No post-compromise security (no DH ratchet):** without periodic DH ratchet steps, a key compromise also exposes all future messages. Verify a new DH ratchet rekeys the session.
- **Unauthenticated encryption / no AEAD:** use AES-256-GCM (or ChaCha20-Poly1305) and bind associated data (sender/receiver identity, message number) into the tag to prevent reordering and reflection.
- **No identity-key verification (MITM):** the server can swap keys unless users compare safety numbers / fingerprints out-of-band. Pin identity keys.
- **No replay/ordering protection:** track message numbers; reject duplicates and out-of-window indices while still handling legitimate out-of-order delivery.
- **The mandatory tests:** (1) two parties exchange and decrypt correctly; (2) the same plaintext yields **different ciphertexts** each time; (3) a captured old message key **cannot** decrypt a newer message (forward secrecy); (4) a **tampered ciphertext or AAD is REJECTED** by the GCM tag; (5) a replayed message is rejected.

## Prerequisites

- Familiarity with cryptography concepts and tools
- Access to a test or lab environment for safe execution
- Python 3.8+ with required dependencies installed
- Appropriate authorization for any testing activities

## Objectives

- Implement X25519 Diffie-Hellman key exchange for session establishment
- Build the Double Ratchet key management algorithm
- Encrypt and decrypt messages with per-message keys
- Implement forward secrecy (compromise of current key does not reveal past messages)
- Handle out-of-order message delivery
- Implement key agreement using X3DH (Extended Triple Diffie-Hellman)

## Key Concepts

### Signal Protocol Components

| Component | Purpose | Algorithm |
|-----------|---------|-----------|
| X3DH | Initial key agreement | X25519 |
| Double Ratchet | Ongoing key management | X25519 + HKDF + AES-GCM |
| Sending Chain | Per-message encryption keys | HMAC-SHA256 chain |
| Receiving Chain | Per-message decryption keys | HMAC-SHA256 chain |
| Root Chain | Derives new chain keys on DH ratchet | HKDF |

### Forward Secrecy

Each message uses a unique encryption key derived from a ratcheting chain. After a key is used, it is deleted, ensuring that compromise of the current state does not reveal previously sent/received messages.

## Security Considerations

- Delete message keys immediately after decryption
- Implement message ordering and replay protection
- Use authenticated encryption (AES-GCM) for all messages
- Protect identity keys with device-level security
- Verify identity keys out-of-band (safety numbers)

## Validation Criteria

- [ ] X25519 key exchange produces shared secret
- [ ] Messages encrypt and decrypt correctly between two parties
- [ ] Different messages produce different ciphertexts
- [ ] Forward secrecy: old keys cannot decrypt new messages
- [ ] Out-of-order messages can be decrypted
- [ ] Tampered messages are rejected by authentication