<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 6, 2017 at 1:10 AM, Nazar Mokrynskyi <span dir="ltr"><<a href="mailto:nazar@mokrynskyi.com" target="_blank">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">Hello everyone,<br>
<br>
Recently I was looking for crypto protocol for upcoming project and found Noise, which seemed to fit in my use case, but didn't have existing JavaScript implementation.<br>
<br>
So I took noise-c, compiled it with Emscripten to WebAssembly and wrote an OOP wrapper around it almost identically to specification.<br>
<br>
Since I'm not a crypto expert and not familiar with Noise in real-world applications, it would be nice to get some feedback and review from wider community.<br>
<br>
The project itself: <a href="https://github.com/nazar-pc/noise-c.wasm" rel="noreferrer" target="_blank">https://github.com/nazar-pc/<wbr>noise-c.wasm</a></blockquote><div><br></div><div><br></div><div>Hi Nazar,</div><div><br></div><div>Sweet! I added it to the wiki:</div><div><br></div><div><a href="https://github.com/noiseprotocol/noise_wiki/wiki">https://github.com/noiseprotocol/noise_wiki/wiki</a><br></div><div><br></div><div>In the past we've kept new libraries there for awhile, then eventually linked them from main website once we build up a bit of confidence in them.</div><div><br></div><div><br></div><div>I have no experience with WebAssembly, but it seems like a great idea (and a better approach to Javascript crypto than WebCrypto, IMO). </div><div><br></div><div>It would be interesting to see performance comparison between Noise-C compiled natively versus WebAssembly, if you or anyone wanted to run benchmarks.</div><div><br></div><div>Trevor</div><div><br></div></div></div></div>