[noise] expected length of messages during handshake
piotr.lizonczyk at gmail.com
Thu Nov 9 03:04:38 PST 2017
I’ve recently started implementing NoiseSocket in Python noiseprotocol.
First thought: would be nice to have at least default proposed contents for
negotiation data. Otherwise we’ll likely end up with implementations freely
following structure in Alexey’s go-noisesocket (or e.g. mine if I decide to
come up with my own). Obviously, usage of this default structure won’t be
necessary, nor explicitly suggested.
W dniu czw., 9.11.2017 o 07:21 Trevor Perrin <trevp at trevp.net> napisał(a):
> On Fri, Nov 3, 2017 at 8:37 PM, David Wong <davidwong.crypto at gmail.com>
> >> It's not an either/or, since NoiseSocket is built on top of the Noise
> >> As for encouraging Noise libraries to also implement NoiseSocket or
> >> any other Noise-based protocol: I'd encourage people to experiment
> >> with NoiseSocket. But NoiseSocket is young, and probably needs a lot
> >> more work and implementation/deployment experience before we have any
> >> confidence that it's the right direction.
> >> But to figure that out, we need to try it!
> > Totally,
> > The experiment will also be more productive if we also have some
> > guidance from you as to what we should implement and test :)
> I'm not sure NoiseSocket has been implemented outside of Alexey /
> Virgil Security, so any feedback on that document is useful:
> Is it easy to understand and implement? Does it work for different
> use cases? What else do we need to add or build on top of it, etc.
> Noise mailing list
> Noise at moderncrypto.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Noise