Noise Protocol Framework
Qu'est-ce que Noise Protocol Framework ?
Noise Protocol FrameworkA composable framework by Trevor Perrin for building modern, formally analyzable secure channel protocols out of Diffie-Hellman, HKDF, and AEAD — the cryptographic core of WireGuard, Signal's I/O Pipe, and many newer protocols.
The Noise Protocol Framework, designed by Trevor Perrin and now standardized at noiseprotocol.org, is a meta-spec for building secure-channel handshakes from a small, well-understood set of primitives: an elliptic-curve Diffie-Hellman function (typically X25519), a hash (typically SHA-256 or BLAKE2s), an AEAD (typically AES-GCM or ChaCha20-Poly1305), and HKDF-style symmetric mixing. A Noise protocol is identified by a pattern (e.g. `Noise_IK_25519_ChaChaPoly_BLAKE2s`) describing exactly which handshake messages flow in which direction and which pre-shared knowledge each side starts with. Standard patterns cover one-way (`N`), interactive (`XX`, `IK`, `XK`, `NK`), and post-quantum hybrid variants. Noise is the cryptographic core of WireGuard (`Noise_IK_25519_ChaChaPoly_BLAKE2s`), Signal's I/O Pipe, the Lightning Network's BOLT-8, and many newer protocols that want modern, formally analyzable handshakes without inventing custom cryptography. Formal verification work (Bhargavan et al., Donenfeld) and the framework's design constraints make it a popular choice when TLS is too heavy or too flexible.
● Exemples
- 01
WireGuard uses `Noise_IK_25519_ChaChaPoly_BLAKE2s` for its one-round-trip mutual authentication between peers with known long-term static keys.
- 02
A peer-to-peer protocol uses Noise XX over QUIC to handshake without exposing peer identities to passive observers.
● Questions fréquentes
Qu'est-ce que Noise Protocol Framework ?
A composable framework by Trevor Perrin for building modern, formally analyzable secure channel protocols out of Diffie-Hellman, HKDF, and AEAD — the cryptographic core of WireGuard, Signal's I/O Pipe, and many newer protocols. Cette notion relève de la catégorie Cryptographie en cybersécurité.
Que signifie Noise Protocol Framework ?
A composable framework by Trevor Perrin for building modern, formally analyzable secure channel protocols out of Diffie-Hellman, HKDF, and AEAD — the cryptographic core of WireGuard, Signal's I/O Pipe, and many newer protocols.
Comment fonctionne Noise Protocol Framework ?
The Noise Protocol Framework, designed by Trevor Perrin and now standardized at noiseprotocol.org, is a meta-spec for building secure-channel handshakes from a small, well-understood set of primitives: an elliptic-curve Diffie-Hellman function (typically X25519), a hash (typically SHA-256 or BLAKE2s), an AEAD (typically AES-GCM or ChaCha20-Poly1305), and HKDF-style symmetric mixing. A Noise protocol is identified by a pattern (e.g. `Noise_IK_25519_ChaChaPoly_BLAKE2s`) describing exactly which handshake messages flow in which direction and which pre-shared knowledge each side starts with. Standard patterns cover one-way (`N`), interactive (`XX`, `IK`, `XK`, `NK`), and post-quantum hybrid variants. Noise is the cryptographic core of WireGuard (`Noise_IK_25519_ChaChaPoly_BLAKE2s`), Signal's I/O Pipe, the Lightning Network's BOLT-8, and many newer protocols that want modern, formally analyzable handshakes without inventing custom cryptography. Formal verification work (Bhargavan et al., Donenfeld) and the framework's design constraints make it a popular choice when TLS is too heavy or too flexible.
Comment se défendre contre Noise Protocol Framework ?
Les défenses contre Noise Protocol Framework combinent habituellement des contrôles techniques et des pratiques opérationnelles, comme détaillé dans la définition ci-dessus.
Quels sont les autres noms de Noise Protocol Framework ?
Noms alternatifs courants : Noise framework, Noise handshake.
● Termes liés
- cryptography№ 352
Échange de clés Diffie–Hellman
Protocole à clé publique permettant à deux parties de dériver un secret partagé sur un canal non sûr sans jamais le transmettre, fondé sur la difficulté du logarithme discret.
- cryptography№ 284
Curve25519
Courbe elliptique de Montgomery concue par Daniel J. Bernstein, utilisee dans la fonction Diffie-Hellman X25519 normalisee par RFC 7748 avec ~128 bits de securite.
- cryptography№ 179
ChaCha20-Poly1305
Construction AEAD associant le chiffrement en flux ChaCha20 a l'authentificateur a usage unique Poly1305, normalisee par RFC 8439 pour TLS 1.3 et WireGuard.
- cryptography№ 021
AEAD (Authenticated Encryption with Associated Data)
A symmetric encryption primitive that provides confidentiality, integrity, and authenticity in one operation, with the ability to bind unencrypted 'associated data' (headers, routing info) to the ciphertext's authentication tag.
- cryptography№ 910
Confidentialité persistante (PFS)
Propriété d'un protocole garantissant que la compromission ultérieure des clés long terme ne permet pas de déchiffrer les sessions passées.
- network-security№ 1279
TLS (Transport Layer Security)
Protocole cryptographique standardisé par l'IETF qui fournit confidentialité, intégrité et authentification au trafic entre deux applications en réseau.