idnits 2.17.1 draft-moonesamy-sshfp-ed25519-00.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 -- The document date (January 24, 2014) is 3743 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'TBD' is mentioned on line 110, but not defined == Missing Reference: 'RFCXXXX' is mentioned on line 110, but not defined Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT S. Moonesamy 3 Intended Status: Informational 4 Expires: July 28, 2014 January 24, 2014 6 Using ED25519 in SSHFP Resource Records 7 draft-moonesamy-sshfp-ed25519-00 9 Abstract 11 The Ed25519 signature algorithm has recently been implemented in 12 OpenSSH. This document updates the IANA "SSHFP RR Types for public 13 key algorithms" registry by adding an algorithm number for Ed25519. 15 Status of this Memo 17 This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that 22 other groups may also distribute working documents as 23 Internet-Drafts. 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 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/1id-abstracts.html 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html 36 Copyright and License Notice 38 Copyright (c) 2014 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 1. Introduction 53 The Ed25519 [Ed25519] signature algorithm has recently been 54 implemented in OpenSSH. RFC 4255 [RFC4255] defines a new DNS 55 resource record, "SSHFP", which can be used to publish a fingerprint 56 of the SSH server public key in the DNS. This document updates the 57 IANA "SSHFP RR Types for public key algorithms" registry by adding an 58 algorithm number for Ed25519 [Ed25519]. 60 2. ED25519 Public Key 62 A SSHFP-aware Secure Shell implementation of the the Ed25519 63 signature algorithm should support SHA-256 fingerprints [FIPS180- 64 4][RFC6594] for verification of the ED25519 public key. A SSHFP- 65 aware Secure Shell implementation which also supports SHA1 66 fingerprints [FIPS180-4][RFC6594] must choose a SHA-256 fingerprint 67 over a SHA1 fingerprint if both fingerprints are available. If the 68 SHA-256 fingerprint does not match the SSH public key received from 69 the SSH server, it is recommended that the public key be rejected 70 instead of testing the SHA1 fingerprint. 72 2.2. ED25519 Public Key with SHA1 Fingerprint 74 The SSHFP Resource Record for the ED25519 public key with SHA1 75 fingerprint would, for example, be: 77 ssh.example.com IN SSHFP [TBD] 1 ( 06a2de9a2d0f034701d67917e49cfc4 78 5a03c2e61 ) 80 2.2. ED25519 Public Key with SHA-256 Fingerprint 82 The SSHFP Resource Record for the ED25519 public key with SHA-256 83 fingerprint would, for example, be: 85 ssh.example.com IN SSHFP [TBD] 2 ( a87f1b687ac0e57d2a081a2f2826723 86 34d90ed316d2b818ca9580ea384d924 87 01 ) 89 RFC Editor Note: Please replace TBD with the value assigned by IANA. 91 3. Security Considerations 93 The overall security of using SSHFP for SSH host key verification is 94 dependent on the security policies of the SSH host administrator and 95 DNS zone administrator (in transferring the fingerprint), detailed 96 aspects of how verification is done in the SSH implementation, and in 97 the client's diligence in accessing the DNS in a secure manner. 99 Please refer to RFC 4255 [RFC4255] for a discussion of the security 100 considerations. 102 4. IANA Considerations 104 IANA is requested to add the following entry to the "SSHFP RR Types 105 for public key algorithms" registry: 107 +--------+-------------+------------+ 108 | Value | Description | Reference | 109 +--------+-------------+------------+ 110 | [TBD] | ED25519 | [RFCXXXX] | 111 +--------+-------------+------------+ 113 RFC Editor Note: Please replace TBD with the value assigned by IANA 114 and RFCXXXX to refer to this document. 116 5. Acknowledgements 118 Some of the text in this document is from RFC 6594 which was written 119 by Ondrej Sury. The author would like to thank Damien Miller for his 120 feedback. 122 6. References 124 6.1. Normative References 126 [RFC4255] Schlyter, J. and W. Griffin, "Using DNS to Securely 127 Publish Secure Shell (SSH) Key Fingerprints", RFC 4255, 128 January 2006. 130 [RFC6594] Sury, O., "Use of the SHA-256 Algorithm with RSA, Digital 131 Signature Algorithm (DSA), and Elliptic Curve DSA (ECDSA) 132 in SSHFP Resource Records", RFC 6594, April 2012. 134 [FIPS180-4] National Institute of Standards and Technology, "Secure 135 Hash Standard (SHS)", FIPS PUB 180-4, March 2012, 136 . 139 6.2. Informative References 141 [Ed25519] 143 Authors' Addresses 144 S. Moonesamy 145 76, Ylang Ylang Avenue 146 Quatres Bornes 147 Mauritius 149 Email: sm+ietf@elandsys.com