<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 27, 2018, at 4:12 PM, dawuud <<a href="mailto:dawuud@riseup.net" class="">dawuud@riseup.net</a>> wrote:</div><div class=""><div class=""><br class="">I am implementing this:<br class=""><a href="https://github.com/katzenpost/docs/blob/master/specs/wire-protocol.rst" class="">https://github.com/katzenpost/docs/blob/master/specs/wire-protocol.rst</a><br class="">However I'm using "Noise_XX_25519_ChaChaPoly_BLAKE2b" instead of<br class="">"Noise_XXhfs_25519+NewHopeSimple_ChaChaPoly_Blake2b". But I might<br class="">later decide to use the rust serde crate for wire command<br class="">serialization if I give up on being bitwise compatible with the golang<br class="">Katzenpost implementation. ( work-in-progress: https://github.com/david415/modem )<br class=""></div></div></blockquote><div><br class=""></div><div>Would be happy to put HFS behind a feature gate in Snow if you or anyone else is up to the task.<div class=""><br class=""></div><div class="">It looks like quininer wrote <a href="https://github.com/quininer/newhope" class="">https://github.com/quininer/newhope</a>, which may at least be a good start.</div></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">Speaking of bitwise compatibility... I noticed that the Noise protocol<br class="">specification does not specify if the prologue is to go before or after<br class="">the handshake message. I have noticed that the golang flynn noise library<br class="">puts the prologue before the handshake ciphertext and the rust snow library<br class="">puts the prologue after the handshake ciphertext.<br class=""></div></div></blockquote><div><br class=""></div><div>Are you talking about the prologue as defined in the Noise, or another type of prologue here?</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">Shouldn't the Noise protocol specify things to the degree that we can<br class="">easiy achieve bitwise compatiblity between language protocol implemenations?<br class=""><br class=""><br class="">Cheers,<br class="">David<br class="">_______________________________________________<br class="">Noise mailing list<br class=""><a href="mailto:Noise@moderncrypto.org" class="">Noise@moderncrypto.org</a><br class="">https://moderncrypto.org/mailman/listinfo/noise<br class=""></div></div></blockquote></div><br class=""></div></div></body></html>