[noise] "have one joint and keep it oiled"

[Alexey Ermishkin]

This is the link I was talking about
https://cloud.google.com/security/encryption-in-transit/application-layer-transport-security/




 

From: Trevor Perrin [mailto:trevp at trevp.net] 
Sent: Friday, December 29, 2017 6:28 AM
To: Alexey Ermishkin <scratch.net at gmail.com>
Cc: Tony Arcieri <bascule at gmail.com>; David Wong <davidwong.crypto at gmail.com>; noise <noise at moderncrypto.org>
Subject: Re: [noise] "have one joint and keep it oiled"

 

 

On Thu, Dec 28, 2017 at 4:08 PM, Alexey Ermishkin <scratch.net at gmail.com <mailto:scratch.net at gmail.com> > wrote:

I don’t think we need canonicalization (yet) because it’s basically a write-once operation.

Might be useful with some kind of certificates, but even then it’s not a big deal. We can just treat whatever message as an array of bytes and forbid editing.

 

Agreed we don't currently need canonical-form serialization for anything.  However, we currently get good test coverage with our test vector format.  If we support higher-level protocol contents that can be encoded different ways (like proto3) then we lose the ability to test them so easily.  Something to keep in mind.

 

 

BTW looks like Google uses some homegrown protocol instead of TLS inside their infrastructure. Seems like a good place for NoiseSocket to fit in 😊

 

Not sure exactly what you're referring to, any links?

 

 

Trevor

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://moderncrypto.org/mail-archive/noise/attachments/20171229/fe095921/attachment.html>