[noise] NoiseSocket and payload padding in handshake messages

[Justin Cormack]

I would assume that many protocols will not use the unencrypted messages
for anything, so using them for padding seems natural (have been planning
to do that for one use case). Encrypted ones can have framing information
so they look much like normal messages so padding should be easy.

On Tue, 17 Apr 2018, 17:31 Trevor Perrin, <trevp at trevp.net> wrote:

> On Tue, Apr 17, 2018 at 4:14 PM, Alexey Ermishkin <scratch.net at gmail.com>
> wrote:
> > Hello everyone,
> > This is when padding was dropped from the handshake
> > https://moderncrypto.org/mail-archive/noise/2017/000931.html
>
> Ah, I missed that, sorry.
>
> Let's take a moment to think about this and make sure we know what
> decision we're making, and why we're making it.
>
> On the one hand, I'm not sure why padding would be less-useful for
> handshake ciphertext than transport ciphertexts.  On the other hand,
> maybe the structure of Noise libraries and the fact that handshake
> payloads are sometimes encrypted and sometimes not, makes this an
> awkward thing to support?
>
> Trevor
> _______________________________________________
> Noise mailing list
> Noise at moderncrypto.org
> https://moderncrypto.org/mailman/listinfo/noise
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://moderncrypto.org/mail-archive/noise/attachments/20180417/1581e983/attachment.html>