ssh-ed25519 implementations
"Mark D. Baushke" <[email protected]> Wed, 10 May 2017 18:39:19 -0700
| Newsgroups | gmane.ietf.secsh |
|---|---|
| Message-ID | <[email protected]> |
[Second attempt. my first attempt got bounced by fraud detection checks for some unknown reason. -- mdb] Hi, Eric Rescorla <[email protected]> has brought to my attention that in https://tools.ietf.org/html/draft-ietf-curdle-ssh-curves-04 it is currently specifying the SSH encoding of secrets on the wire using the mpint process as described in section 5 of [RFC4251] while RFC 7748 describes using a little-endian format: GF(2^448 - 2^224 - 1) and are encoded as an array of bytes, u, in little-endian order such that u[0] + 256*u[1] + 256^2*u[2] + ... + This seems to be what is being implemeneted for [email protected], so I should make an explicit note of this in the draft. However, I am unaware of any curve448-sha512 implementations at present and would like consensus that it should also follow the mpint method rather than the RFC 7748 method. Please reply to [email protected] with your opinions. Thank you, -- Mark