<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On May 30, 2017, at 8:56 AM, Trevor Perrin <<a href="mailto:trevp@trevp.net" class="">trevp@trevp.net</a>> wrote:</div><div class=""><div class=""><br class="">Cool, I assume that's 250 MB/sec?<br class=""></div></div></blockquote><br class=""><div class="">It’s genuinely showing ~2500MB/s assuming ring’s benchmark tests are also accurate (results matching the similar AES-GCM TLS tests done in <a href="https://github.com/briansmith/crypto-bench" class="">https://github.com/briansmith/crypto-bench</a> when run on my laptop). Running on another server just now I see ~1500MB/s.</div><div class=""><br class=""></div><div class=""><div class="">But if that sounds unrealistic (I’m also skeptical of that performance in production settings), feel free to scour <a href="https://github.com/mcginty/snow/blob/master/benches/benches.rs" class="">https://github.com/mcginty/snow/blob/master/benches/benches.rs</a> and let me know what’s wrong. I haven’t checked the compiled output to see if anything’s getting optimized away, etc.</div></div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div class="">Does *ring* not provide BLAKE2 or X25519, currently?<br class=""></div></div></blockquote><br class=""><div class="">*ring* unfortunately doesn’t provide BLAKE2, and while it supports X25519 it doesn’t allow you to provide your own private key yet. If I have time this week I was considering submitting a PR to get that in though.</div><div class=""><br class=""></div><div class="">Once I also add in feature-gated support for libsodium via a library like sodiumoxide, though, we will have a much better X25519 implementation available quickly.</div><div class=""><br class=""></div></div></body></html>