[noise] Another go implementation

[Stephen Touset]

The first two issues have been fixed. Strangely, I could have sworn that
the KDF issue *used* to work, due to how (I thought) slices were
implemented. That doesn't seem to be the case, so I'm simply copying the
bytes back into the message used for the next iteration.

Thanks for your feedback; let me know if there's anything else you notice.
This is my first go project, so I'm bound to have made mistakes. Tests and
documentation are forthcoming.


On Sat, Jul 12, 2014 at 8:22 AM, Jonathan Rudenberg <jonathan at titanous.com>
wrote:

>
> On Jul 11, 2014, at 3:51 PM, Stephen Touset <stephen at squareup.com> wrote:
>
> > I was working on this before I heard someone else had worked on an
> implementation. Mine supports opening and closing boxes, and also begins to
> implement pipes. I have basic syn/ack (for lack of a better term) support
> for boxes sent through pipes, but I haven't yet written the code to allow
> sending only bodies. That should come in short order.
> >
> > I'd love to see if the two existing implementations interoperate
> successfully!
> >
> >         https://github.com/stouset/go.noise
>
> I started implementing a compatibility test for our implementations and
> ran into the following initial issues:
>
> 1) You don’t appear to be setting the default cv=zeros[CV_LEN], so the
> ‘extra’ argument to the first KDF is zero-length instead of 48 null bytes.
>
> 2) It looks like the t[0:32] bytes in your KDF are not that of the
> previous iteration.
>
> 3) I think what you are calling the ‘peerEphemeralKey’ is the
> recvr_pubkey. My understanding is that this is actually the long-term
> public key of the peer.
>
> Trevor, please correct me if you see any inaccuracies in my reading of the
> spec.
>
> Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://moderncrypto.org/mail-archive/noise/attachments/20140712/b8c9aac5/attachment.html>