<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>I've tested cacophony vectors from Alex's repo initially and even
      have support for protocol_name field already, but like you've
      said, PSK vectors were failing, so tests are running against those
      in noise-c's repository for now.</p>
    <p>Rhys Weatherley is working on updates in noise-c already
      (<a class="moz-txt-link-freetext" href="https://github.com/rweather/noise-c/issues/24">https://github.com/rweather/noise-c/issues/24</a>), I'll make
      necessary updates shortly after noise-c.</p>
    <pre class="moz-signature" cols="0">Sincerely, Nazar Mokrynskyi
github.com/nazar-pc</pre>
    <div class="moz-cite-prefix">On 10/5/17 5:14 AM, Trevor Perrin
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAGZ8ZG3zHJjFdKD=bK4DwK2n-K5L7voqzxfw+QFSOjn5Ckkr8w@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Wed, Oct 4, 2017 at 11:30 AM,
            Nazar Mokrynskyi <span dir="ltr"><<a
                href="mailto:nazar@mokrynskyi.com" target="_blank"
                moz-do-not-send="true">nazar@mokrynskyi.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div bgcolor="#FFFFFF">
                <p>I've worked on test vectors today and now
                  noise-c.wasm passes all of the vectors included in
                  noise-c repository, so in terms of spec compliance
                  (v30 according to noise-c's website at the moment) it
                  should be on par with noise-c.<br>
                </p>
              </div>
            </blockquote>
            <div>
              <div>Hi Nazar,</div>
              <div><br>
              </div>
              <div>That's great!  Thanks for doing that.</div>
              <div><br>
              </div>
              <div>You might also test with the latest cacophony vectors
                (from Noise wiki, or Alex's repo).  But I think the only
                differences are:</div>
              <div> * The test vector format (it now parses the protocol
                name, instead of having separate JSON fields for
                DH/cipher/hash)</div>
              <div> * PSK handling, which changed in revision 32</div>
              <div><br>
              </div>
              <div>(We should probably version the "cacophony" vectors,
                like include the creation date in the filename or
                something).</div>
              <div><br>
              </div>
              <div>I think Noise-C is up-to-date with revision 31.  The
                substantive changes since then are PSK handling and the
                addition of "rekey" functionality.  <br>
              </div>
              <div><br>
              </div>
              <div>It would be great to update Noise-C for these, since
                WireGuard uses PSKs, and other people might use rekey
                [1].</div>
              <div><br>
              </div>
              <div>But I'll link your implementation on the Website in
                mid-October in either case (I encourage other people to
                take a look and send feedback before then).</div>
              <div><br>
              </div>
              <div>Trevor</div>
              <div><br>
              </div>
              <div>[1] <a
href="https://github.com/Katzenpost/docs/blob/master/specs/wire-protocol.txt"
                  moz-do-not-send="true">https://github.com/Katzenpost/docs/blob/master/specs/wire-protocol.txt</a> </div>
              <div><br>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
  </body>
</html>