implementing-end-to-end-encryption-for-messaging

Imported from WorkNFlow/ai-coffee-shop (.agents/skills/Security/implementing-end-to-end-encryption-for-messaging/SKILL.md). Install upstream with npx skills add WorkNFlow/ai-coffee-shop --skill implementing-end-to-end-encryption-for-messaging. Copyright stays with the author (Apache-2.0).

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

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

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