[messaging] RFC: async NaCl relay

U.Mutlu for-gmane at mutluit.com
Fri Dec 18 04:22:24 PST 2015

this looks very interessting and I wish you much success with the project.

But it should be done so that even when a relay node gets operated
by the enemy, the user data should still be secure/protected.
Just my 2 cents.

Max Skibinsky wrote on 12/18/2015 01:19 AM:
> Gents, we recently open sourced a couple of our infrastructure projects,
> and I'm hoping that it would be interesting to the folks here to review our
> codebase with a fresh set of eyes.
> The main project is a "dead-drop" communication relay built around the NaCl
> library. The idea is to have interchangeable relays with a global address
> space (hash of identity keys) that keeps pass-through messages in
> memory-only storage and are automatically cleared after a few days.
> We were fortunate to have Yevgeniy Dodis help us with the design of the
> crypto-schema for this relay, yet obviously there is a noticeable distance
> from theoretical security to a provably secure codebase. We have done a few
> rounds of internal reviews so far - if this is something that interests
> you, we would really appreciate any feedback at *crypto at vault12.io
> <crypto at vault12.io>*
> Quick summary: https://bit.ly/zax_relay
> Relay codebase: https://github.com/vault12/zax
> Technical spec: https://bit.ly/nacl_relay_spec
> Reference client: https://github.com/vault12/glow
> Test relay: https://zax_test.vault12.com/ (30m data expiration)
> - ℳ
> blog <http://skibinsky.com/>
> *linkedin <http://bit.ly/max-li>*

More information about the Messaging mailing list