idnits 2.17.1 draft-bjh21-ssh-ed25519-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 80 has weird spacing: '... string key...' == Line 95 has weird spacing: '... string sig...' -- The document date (August 1, 2015) is 3183 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFCXXXX' is mentioned on line 117, but not defined Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Harris 3 Internet-Draft August 1, 2015 4 Intended status: Informational 5 Expires: February 2, 2016 7 Ed25519 public key algorithm for the Secure Shell (SSH) protocol 8 draft-bjh21-ssh-ed25519-02 10 Abstract 12 This document describes the use of the Ed25519 digital signature 13 algorithm in the Secure Shell (SSH) protocol. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on February 2, 2016. 32 Copyright Notice 34 Copyright (c) 2015 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 1. Introduction 49 Secure Shell (SSH) [RFC4251] is a secure remote-login protocol. It 50 provides for an extensible variety of public key algorithms for 51 identifying servers and users to one another. Ed25519 52 [I-D.josefsson-eddsa-ed25519] is a digital signature system. 53 OpenSSH 6.5 [OpenSSH-6.5] introduced support for using Ed25519 for 54 server and user authentication. Compatible support for Ed25519 has 55 since been added to other SSH implementations. 57 This document describes the method implemented by OpenSSH and others, 58 and formalizes its use of the name "ssh-ed25519". 60 Comments on this draft are welcomed and should be sent to the author. 62 2. Conventions Used in This Document 64 The descriptions of key and signature formats use the notation 65 introduced in [RFC4251], Section 3 and the string data type from 66 [RFC4251], Section 5. 68 3. Public Key Algorithm 70 This document describes a public key algorithm for use with SSH in 71 accordance with [RFC4253], Section 6.6. The name of the algorithm is 72 "ssh-ed25519". This algorithm only supports signing and not 73 encryption. 75 4. Public Key Format 77 The "ssh-ed25519" key format has the following encoding: 79 string "ssh-ed25519" 80 string key 82 Here 'key' is the 32-octet public key described by 83 [I-D.josefsson-eddsa-ed25519], Section 5.5. 85 5. Signature Algorithm 87 Signatures are generated according to the procedure in 88 [I-D.josefsson-eddsa-ed25519], Section 5.6. 90 6. Signature format 92 The corresponding signature format is: 94 string "ssh-ed25519" 95 string signature 97 Here 'signature' is the 64-octet signature produced in accordance 98 with [I-D.josefsson-eddsa-ed25519], Section 5.6. 100 7. Verification Algorithm 102 Signatures are verified according to the procedure in 103 [I-D.josefsson-eddsa-ed25519], Section 5.7. 105 8. SSHFP DNS resource records 107 The generation of SSHFP resource records for "ssh-ed25519" keys is 108 described in [RFC7479]. 110 9. IANA Considerations 112 IANA is requested to assign the Public Key Algorithm name 113 "ssh-ed25519" in accordance with [RFC4250], Section 4.6.2: 115 Public Key Algorithm Name Reference 116 ------------------------- --------- 117 ssh-ed25519 [RFCXXXX] 119 [TO BE REMOVED: This registration should take place at the following 120 location: ] 123 10. Security Considerations 125 The security considerations in [RFC4251], Section 9 apply to all SSH 126 implementations, including those using Ed25519. 128 The security considerations in [I-D.josefsson-eddsa-ed25519], 129 Section 9 apply to all uses of Ed25519, including those in SSH. 131 11. Acknowledgements 133 The OpenSSH implementation of Ed25519 in SSH was written by Markus 134 Friedl. 136 12. References 137 12.1. Normative References 139 [RFC4250] Lehtinen, S. and C. Lonvick, Ed., "The Secure Shell (SSH) 140 Protocol Assigned Numbers", RFC 4250, 141 DOI 10.17487/RFC4250, January 2006, 142 . 144 [RFC4251] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH) 145 Protocol Architecture", RFC 4251, DOI 10.17487/RFC4251, 146 January 2006, . 148 [RFC4253] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH) 149 Transport Layer Protocol", RFC 4253, DOI 10.17487/RFC4253, 150 January 2006, . 152 [I-D.josefsson-eddsa-ed25519] 153 Josefsson, S. and N. Moller, "EdDSA and Ed25519", draft- 154 josefsson-eddsa-ed25519-03 (work in progress), May 2015. 156 12.2. Informative References 158 [RFC7479] Moonesamy, S., "Using Ed25519 in SSHFP Resource Records", 159 RFC 7479, DOI 10.17487/RFC7479, March 2015, 160 . 162 [OpenSSH-6.5] 163 Friedl, M., Provos, N., de Raadt, T., Steves, K., Miller, 164 D., Tucker, D., McIntyre, J., Rice, T., and B. Lindstrom, 165 "[OpenSSH 6.5 release notes]", January 2014, 166 . 168 Author's Address 170 Ben Harris 171 2A Eachard Road 172 CAMBRIDGE CB3 0HY 173 UNITED KINGDOM 175 Email: bjh21@bjh21.me.uk