💾 Archived View for rawtext.club › ~sloum › geminilist › 000496.gmi captured on 2020-10-31 at 01:37:23. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Ciprian Dorin Craciun ciprian.craciun at gmail.com
Tue Mar 10 14:02:12 GMT 2020
- - - - - - - - - - - - - - - - - - - ``` On Tue, Mar 10, 2020 at 3:55 PM Jason McBrayer <jmcbray at carcosa.net> wrote: > If we really wanted to go down this route, Noise protocol is more > comparable to TLS than just using NaCL directly; the Python bindings > seem only about as complex to use as the Python TLS bindings. The only > thing is that Noise has libraries for 5 or 6 languages, compared to how > ubiquitous TLS is. In the interim I've documented my proposal, including a clear diagram,used functions from libsodium and an asessment:* https://github.com/cipriancraciun/gemini-experiments/blob/master/nacl/documentation/protocol-v1.md* https://github.com/cipriancraciun/gemini-experiments/blob/master/nacl/documentation/libsodium-internals.md Now, regarding the Noise protocol, as you've observed there aren'tmany implementations of it; however on the other side the Noiseprotocol is actually a "blueprint" of how to implement securecommunication protocols and doesn't actually specify any cryptographicprimitives; thus all the existing libraries are either incompatiblewith each other or are quite uninteligible (I've looked at a fewRust-based implementations and I wouldn't know where to start usingthem). On the other side my proposal was to get "inspired" from the Noiseprotocol, and then try to provide a simple and clear "recipe" based onthat. Ciprian.