Matt Johnston <matt%ucc.asn.au@localhost> writes: > On Tue, Nov 17, 2015 at 04:26:57PM +0100, Niels Möller wrote: >> denis bider <ietf-ssh3%denisbider.com@localhost> writes: >> >> > Overall, though, it seems to be a bikeshed issue - it doesn't >> > really matter either way. >> >> I'd really like to hear more opinions. > > Dropbear implements curve25519-sha256%libssh.org@localhost. My 2c is > to stick with K as an mpint just to avoid unnecessary > change/confusion with RFC 4253 (7.2, deriving keys) and 5656. > In terms of implementation a fixed 32 byte string would have > been simpler, but not worth changing. Agreed. > A small thing, 'k' in draft-josefsson-ssh-curves-01 should > probably be upper case? Yep, fixed. > Is it worth keeping the "Verify that client public key length is 32 > bytes" (or 56) > text of curve25519-sha256%libssh.org.txt@localhost ? I added it. /Simon
Attachment:
signature.asc
Description: PGP signature