Re: [Curdle] I-D Action: draft-ietf-curdle-ssh-curves-03.txt

[Sean Turner <[e-mail]>]

> On Apr 12, 2017, at 17:14, Mark D. Baushke <[e-mail]> wrote:
> 
> Hi Sean,
> 
> Sean Turner <[e-mail]> writes:
> 
>> Should this be referring to RFC7748 for curves 25519 and 448?
> 
> I think so, and I think it does in section 2.
> 
> https://datatracker.ietf.org/doc/html/draft-ietf-curdle-ssh-curves-03
> Page 3 says:
> 
>   The methods are based on Curve25519 and Curve448 scalar
>   multiplication, as described in [RFC7748].  Private and public keys
>   are generated as described therein.  Public keys are defined as
>   strings of 32 bytes for Curve25519 and 56 bytes for Curve448.
>   Clients and servers MUST fail the key exchange if the length of the
>   received public keys are not the expected lengths, or if the derived
>   shared secret only consists of zero bits.  No further validation is
>   required beyond what is discussed in [RFC7748].  The derived shared
>   secret is 32 bytes when Curve25519 is used and 56 bytes when Curve448
>   is used.  The encodings of all values are defined in [RFC7748].  The
>   hash used is SHA-256 for Curve25519 and SHA-512 for Curve448.
> 
> Could you be more specific as to what change(s) you are suggesting?
> 
> 	-- Mark

Sorry for not being more specific.  There’s still references to the other specs.

OLD:

   This document describes how to implement key exchange based on
   [Curve25519] and [Ed448-Goldilocks] in SSH.

NEW:

   This document describes how to implement key exchange based on
   Curve25519 and Ed448-Goldilocks [RFC7748] in SSH.

spt