[noise] Replacing TLS with noise

Scratch scratch.net at gmail.com
Thu Dec 29 00:56:52 PST 2016

Hi Nathan, thanks for the info. I've already took a look at wireguard
and may consider some of its ideas. However I'll stick with TCP for

2016-12-29 13:11 GMT+05:00 Naveen Nathan <naveen at lastninja.net>:
>>    Hello everyone!
>>    I'm looking into implementing a secure transport layer for communication
>>    between micro services. I don't want TLS because I don't need x.509 and
>>    all that stuff. I know that there's a proposal for TLS 1.3 to have a"keys
>>    only" mode, but it's still not accepted and i'm not sure it will get into
>>    standard.Keys are perfectly enough for me. But I also don't want to
>>    invent a bicycle here and use as much already invented things as possible.
>>    Maybe there's whatsapp's packet structure (the new one, with noise)
>>    somewhere? Or maybe someone has already done such a protocol that I could
>>    implement and be compatible?A
>>    Thanks in advance.
> Presently there are only few known applications using Noise:
>  * WhatsApp / Signal
>  * Wireguard
> The internals of Wireguard is pretty well specified in the whitepaper [1]
> and uses the Noise_IK pattern. It aims for the simplicity of "ssh keys" model
> but for VPN. But on top of the protocol itself is a tad bit of complexity
> due to key-rollover and such. I would consider it as a reference, but
> you will probably need to tailor an underlying messaging/transport protocol
> to suit your needs - and probably give extra consideration to section 12
> in the noise spec (Application Responsibilities).
> - Naveen
> [1]: https://www.wireguard.io/papers/wireguard.pdf
> _______________________________________________
> Noise mailing list
> Noise at moderncrypto.org
> https://moderncrypto.org/mailman/listinfo/noise

More information about the Noise mailing list