draft-ietf-curdle-ssh-ed25519-ed448-09.txt   draft-ietf-curdle-ssh-ed25519-ed448-10.txt 
Internet Engineering Task Force B. Harris Internet Engineering Task Force B. Harris
Internet-Draft Internet-Draft
Intended status: Standards Track L. Velvindron Updates: RFC4253 (if approved) L. Velvindron
Expires: January 31, 2020 cyberstorm.mu Intended status: Standards Track cyberstorm.mu
July 30, 2019 Expires: March 5, 2020 September 2, 2019
Ed25519 and Ed448 public key algorithms for the Secure Shell (SSH) Ed25519 and Ed448 public key algorithms for the Secure Shell (SSH)
protocol protocol
draft-ietf-curdle-ssh-ed25519-ed448-09 draft-ietf-curdle-ssh-ed25519-ed448-10
Abstract Abstract
This document describes the use of the Ed25519 and Ed448 digital This document describes the use of the Ed25519 and Ed448 digital
signature algorithm in the Secure Shell (SSH) protocol. signature algorithm in the Secure Shell (SSH) protocol.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 31, 2020. This Internet-Draft will expire on March 5, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 32 skipping to change at page 2, line 32
2. Conventions Used in This Document 2. Conventions Used in This Document
The descriptions of key and signature formats use the notation The descriptions of key and signature formats use the notation
introduced in [RFC4251], Section 3 [RFC4251] and the string data type introduced in [RFC4251], Section 3 [RFC4251] and the string data type
from [RFC4251], Section 5 [RFC4251]. from [RFC4251], Section 5 [RFC4251].
2.1. Requirements Language 2.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119] RFC
8174 [RFC8174] when, and only when, they appear in all capitals, as
shown here.
3. Public Key Algorithm 3. Public Key Algorithm
This document describes a public key algorithm for use with SSH in This document describes a public key algorithm for use with SSH in
accordance with [RFC4253], Section 6.6 [RFC4253]. The name of the accordance with [RFC4253], Section 6.6 [RFC4253]. The name of the
algorithm is "ssh-ed25519". This algorithm only supports signing and algorithm is "ssh-ed25519". This algorithm only supports signing and
not encryption. not encryption.
Additionally, this document describes another public key algorithm. Additionally, this document describes another public key algorithm.
The name of the algorithm is "ssh-ed448". This algorithm only The name of the algorithm is "ssh-ed448". This algorithm only
skipping to change at page 3, line 23 skipping to change at page 3, line 26
string "ssh-ed448" string "ssh-ed448"
string key string key
Here 'key' is the 57-octet public key described by [RFC8032], Here 'key' is the 57-octet public key described by [RFC8032],
Section 5.2.5 [RFC8032]. Section 5.2.5 [RFC8032].
5. Signature Algorithm 5. Signature Algorithm
Signatures are generated according to the procedure in [RFC8032], Signatures are generated according to the procedure in [RFC8032],
Section 5.2.6 [RFC8032]. Section 5.1.6 and Section 5.2.6 [RFC8032].
6. Signature Format 6. Signature Format
The "ssh-ed25519" key format has the following encoding: The "ssh-ed25519" key format has the following encoding:
string "ssh-ed25519" string "ssh-ed25519"
string signature string signature
Here 'signature' is the 64-octet signature produced in accordance Here 'signature' is the 64-octet signature produced in accordance
with [RFC8032], Section 5.1.6 [RFC8032]. with [RFC8032], Section 5.1.6 [RFC8032].
skipping to change at page 3, line 45 skipping to change at page 3, line 48
The "ssh-ed448" key format has the following encoding: The "ssh-ed448" key format has the following encoding:
string "ssh-ed448" string "ssh-ed448"
string signature string signature
Here 'signature' is the 114-octet signature produced in accordance Here 'signature' is the 114-octet signature produced in accordance
with [RFC8032], Section 5.2.6 [RFC8032]. with [RFC8032], Section 5.2.6 [RFC8032].
7. Verification Algorithm 7. Verification Algorithm
ED25519 signatures are verified according to the procedure in Ed25519 signatures are verified according to the procedure in
[RFC8032], Section 5.1.7 [RFC8032]. [RFC8032], Section 5.1.7 [RFC8032].
ED448 signatures are verified according to the procedure in Ed448 signatures are verified according to the procedure in
[RFC8032], Section 5.2.7 [RFC8032]. [RFC8032], Section 5.2.7 [RFC8032].
8. SSHFP DNS resource records 8. SSHFP DNS resource records
Usage and generation of SSHFP DNS resource record is described in Usage and generation of SSHFP DNS resource record is described in
[RFC4255]. The generation of SSHFP resource records for "ssh- [RFC4255]. The generation of SSHFP resource records for "ssh-
ed25519" keys is described in [RFC7479]. This section illustrates ed25519" keys is described in [RFC7479]. This section illustrates
the generation of SSHFP resource records for "ssh-ed448" keys and the the generation of SSHFP resource records for "ssh-ed448" keys and the
document specifies the corresponding Ed448 code point to the "SSHFP document specifies the corresponding Ed448 code point to the "SSHFP
RR Types for public key algorithms" IANA registry. RR Types for public key algorithms" IANA registry.
skipping to change at page 4, line 25 skipping to change at page 4, line 25
described in [RFC7479]. described in [RFC7479].
The generation of SSHFP resource records for "ssh-ed448" keys is The generation of SSHFP resource records for "ssh-ed448" keys is
described as follows. described as follows.
The encoding of ed448 public keys is described in [ED448]. In brief, The encoding of ed448 public keys is described in [ED448]. In brief,
an ed448 public key is a 57-octet value representing a 455-bit an ed448 public key is a 57-octet value representing a 455-bit
y-coordinate of an elliptic curve point, and a sign bit indicating y-coordinate of an elliptic curve point, and a sign bit indicating
the the corresponding x-coordinate. the the corresponding x-coordinate.
the SSHFP Resource Record for the Ed448 public key with SHA-256 The SSHFP Resource Record for the Ed448 public key with SHA-256
fingerprint would be example be: fingerprint would for example be:
example.com. IN SSHFP TBD 2 ( a87f1b687ac0e57d2a081a2f2826723 example.com. IN SSHFP TBD 2 ( a87f1b687ac0e57d2a081a2f2826723
34d90ed316d2b818ca9580ea384d924 01 ) 34d90ed316d2b818ca9580ea384d924 01 )
The 2 here indicates SHA-256 [RFC6594]. The 2 here indicates SHA-256 [RFC6594].
9. IANA Considerations 9. IANA Considerations
This document augments the Public Key Algorithm Names in [RFC4250], This document augments the Public Key Algorithm Names in [RFC4250],
Section 4.6.2 [RFC4250]. Section 4.6.2 [RFC4250].
skipping to change at page 5, line 10 skipping to change at page 5, line 10
+--------+-------------+------------+ +--------+-------------+------------+
| Value | Description | Reference | | Value | Description | Reference |
+--------+-------------+------------+ +--------+-------------+------------+
| TBD | Ed448 | [this-draft] | | TBD | Ed448 | [this-draft] |
+--------+-------------+------------+ +--------+-------------+------------+
We suggest 6 as value. We strongly suggest 6 as value.
[TO BE REMOVED: This registration should take place at the following [TO BE REMOVED: This registration should take place at the following
location: <http://www.iana.org/assignments/ssh-parameters/ssh- location: <http://www.iana.org/assignments/ssh-parameters/ssh-
parameters.xhtml#ssh-parameters-19>] parameters.xhtml#ssh-parameters-19>]
10. Security Considerations 10. Security Considerations
The security considerations in [RFC4251], Section 9 [RFC4251] apply The security considerations in [RFC4251], Section 9 [RFC4251] apply
to all SSH implementations, including those using Ed25519 and Ed448. to all SSH implementations, including those using Ed25519 and Ed448.
skipping to change at page 6, line 21 skipping to change at page 6, line 21
Signature Algorithm (DSA), and Elliptic Curve DSA (ECDSA) Signature Algorithm (DSA), and Elliptic Curve DSA (ECDSA)
in SSHFP Resource Records", RFC 6594, in SSHFP Resource Records", RFC 6594,
DOI 10.17487/RFC6594, April 2012, DOI 10.17487/RFC6594, April 2012,
<https://www.rfc-editor.org/info/rfc6594>. <https://www.rfc-editor.org/info/rfc6594>.
[RFC8032] Josefsson, S. and I. Liusvaara, "Edwards-Curve Digital [RFC8032] Josefsson, S. and I. Liusvaara, "Edwards-Curve Digital
Signature Algorithm (EdDSA)", RFC 8032, Signature Algorithm (EdDSA)", RFC 8032,
DOI 10.17487/RFC8032, January 2017, DOI 10.17487/RFC8032, January 2017,
<https://www.rfc-editor.org/info/rfc8032>. <https://www.rfc-editor.org/info/rfc8032>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
12.2. Informative References 12.2. Informative References
[ED448] Hamburg, M., "Ed448-Goldilocks, a new elliptic curve", [ED448] Hamburg, M., "Ed448-Goldilocks, a new elliptic curve",
January 2015, <https://eprint.iacr.org/2015/625.pdf>. January 2015, <https://eprint.iacr.org/2015/625.pdf>.
[IANA-PKA] [IANA-PKA]
Internet Assigned Numbers Authority (IANA), "Secure Shell Internet Assigned Numbers Authority (IANA), "Secure Shell
(SSH) Protocol Parameters: Public Key Algorithm Names", (SSH) Protocol Parameters: Public Key Algorithm Names",
May 2017, <http://www.iana.org/assignments/ssh-parameters/ May 2017, <http://www.iana.org/assignments/ssh-parameters/
ssh-parameters.xhtml#ssh-parameters-19>. ssh-parameters.xhtml#ssh-parameters-19>.
 End of changes. 10 change blocks. 
12 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/