[noise] Implementation: Revision 10 - Noise_IS, with a few deviations

[Jason A. Donenfeld]

On Oct 17, 2015 2:50 AM, "Trevor Perrin" <trevp at trevp.net> wrote:
> > There is no maximum length limit, though the MTU controls this
implicitly.
>
> Is there a reason 65535-byte messages are too short?

No. And in all likelihood, they'll be sufficient. MTU is generally around
1500. Jumbo frames increases that to 9000. I've never heard of anything
close to 65535. But... I have no idea about the conditions of next year's
networks. And I don't see a reason to artificially limit things (beyond
size_t).

> > The first handshake message contains a timestamp, to prevent replay
attacks,
> > as part of its payload.
>
> Not really a deviation, you can put whatever you want in the payload.

Right, but it does change (strengthen) the security characteristics of
Noise_IS. IMHO, this stamp should be mandated, or at the very least
recommended, by the spec.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://moderncrypto.org/mail-archive/noise/attachments/20151017/b4be173e/attachment.html>