1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
|
<pre>Internet Engineering Task Force (IETF) O. Sury
Request for Comments: 6594 CZ.NIC
Category: Standards Track April 2012
ISSN: 2070-1721
<span class="h1">Use of the SHA-256 Algorithm with RSA,</span>
<span class="h1">Digital Signature Algorithm (DSA),</span>
<span class="h1">and Elliptic Curve DSA (ECDSA) in SSHFP Resource Records</span>
Abstract
This document updates the IANA registries in <a href="./rfc4255">RFC 4255</a>, which defines
SSHFP, a DNS Resource Record (RR) that contains a standard Secure
Shell (SSH) key fingerprint used to verify SSH host keys using DNS
Security Extensions (DNSSEC). This document defines additional
options supporting SSH public keys applying the Elliptic Curve
Digital Signature Algorithm (ECDSA) and the implementation of
fingerprints computed using the SHA-256 message digest algorithm in
SSHFP Resource Records.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
fInternet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6594">http://www.rfc-editor.org/info/rfc6594</a>.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
<span class="grey">Sury Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6594">RFC 6594</a> ECDSA and SHA-256 Algorithms for SSHFP April 2012</span>
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Requirements Language ...........................................<a href="#page-4">4</a>
<a href="#section-3">3</a>. SSHFP Resource Records ..........................................<a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. SSHFP Fingerprint Type Specification .......................<a href="#page-4">4</a>
<a href="#section-3.1.1">3.1.1</a>. SHA-256 SSHFP Fingerprint Type Specification ........<a href="#page-4">4</a>
<a href="#section-3.2">3.2</a>. SSHFP Algorithm Number Specification .......................<a href="#page-4">4</a>
<a href="#section-3.2.1">3.2.1</a>. ECDSA SSHFP Algorithm Number Specification ..........<a href="#page-4">4</a>
<a href="#section-4">4</a>. Implementation Considerations ...................................<a href="#page-4">4</a>
<a href="#section-4.1">4.1</a>. Support for SHA-256 Fingerprints ...........................<a href="#page-4">4</a>
<a href="#section-4.2">4.2</a>. Support for ECDSA ..........................................<a href="#page-4">4</a>
<a href="#section-5">5</a>. Examples ........................................................<a href="#page-5">5</a>
<a href="#section-5.1">5.1</a>. RSA Public Key .............................................<a href="#page-5">5</a>
<a href="#section-5.1.1">5.1.1</a>. RSA Public Key with SHA1 Fingerprint ................<a href="#page-5">5</a>
<a href="#section-5.1.2">5.1.2</a>. RSA Public Key with SHA-256 Fingerprint .............<a href="#page-5">5</a>
<a href="#section-5.2">5.2</a>. DSA Public Key .............................................<a href="#page-6">6</a>
<a href="#section-5.2.1">5.2.1</a>. DSA Public Key with SHA1 Fingerprint ................<a href="#page-6">6</a>
<a href="#section-5.2.2">5.2.2</a>. DSA Public Key with SHA-256 Fingerprint .............<a href="#page-6">6</a>
<a href="#section-5.3">5.3</a>. ECDSA Public Key ...........................................<a href="#page-6">6</a>
<a href="#section-5.3.1">5.3.1</a>. ECDSA Public Key with SHA1 Fingerprint ..............<a href="#page-7">7</a>
<a href="#section-5.3.2">5.3.2</a>. ECDSA Public Key with SHA-256 Fingerprint ...........<a href="#page-7">7</a>
<a href="#section-6">6</a>. IANA Considerations .............................................<a href="#page-7">7</a>
<a href="#section-6.1">6.1</a>. SSHFP RR Types for Public Key Algorithms ...................<a href="#page-7">7</a>
<a href="#section-6.2">6.2</a>. SSHFP RR Types for Fingerprint Types .......................<a href="#page-7">7</a>
<a href="#section-7">7</a>. Security Considerations .........................................<a href="#page-8">8</a>
<a href="#section-8">8</a>. References ......................................................<a href="#page-8">8</a>
<a href="#section-8.1">8.1</a>. Normative References .......................................<a href="#page-8">8</a>
<a href="#section-8.2">8.2</a>. Informative References .....................................<a href="#page-9">9</a>
<span class="grey">Sury Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6594">RFC 6594</a> ECDSA and SHA-256 Algorithms for SSHFP April 2012</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Domain Name System (DNS) is the global, hierarchical distributed
database for Internet naming. The Secure Shell (SSH) is a protocol
for secure remote login and other secure network services over an
insecure network. <a href="./rfc4253">RFC 4253</a> [<a href="./rfc4253" title=""The Secure Shell (SSH) Transport Layer Protocol"">RFC4253</a>] defines Public Key Algorithms
for the Secure Shell server public keys.
The DNS has been extended to store fingerprints in a DNS Resource
Record named SSHFP [<a href="./rfc4255" title=""Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints"">RFC4255</a>], which provides out-of-band verification
by looking up a fingerprint of the server public key in the DNS
[<a href="./rfc1034" title=""Domain names - concepts and facilities"">RFC1034</a>][RFC1035] and using Domain Name System Security Extensions
(DNSSEC) [<a href="./rfc4033" title=""DNS Security Introduction and Requirements"">RFC4033</a>][RFC4034][<a href="./rfc4035" title=""Protocol Modifications for the DNS Security Extensions"">RFC4035</a>] to verify the lookup.
<a href="./rfc4255">RFC 4255</a> [<a href="./rfc4255" title=""Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints"">RFC4255</a>] describes how to store the cryptographic
fingerprint of SSH public keys in SSHFP Resource Records. SSHFP
Resource Records contain the fingerprint and two index numbers
identifying the cryptographic algorithms used:
1. to link the fingerprinted public key with the corresponding
private key, and
2. to derive the message digest stored as the fingerprint in the
record.
<a href="./rfc4255">RFC 4255</a> [<a href="./rfc4255" title=""Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints"">RFC4255</a>] then specifies lists of cryptographic algorithms
and the corresponding index numbers used to identify them in SSHFP
Resource Records.
This document updates the IANA registry "SSHFP RR Types for public
key algorithms" and "SSHFP RR types for fingerprint types"
[<a href="#ref-SSHFPVALS" title=""DNS SSHFP Resource Records Parameters"">SSHFPVALS</a>] by adding a new option in each list:
o the Elliptic Curve Digital Signature Algorithm (ECDSA) [<a href="./rfc6090" title=""Fundamental Elliptic Curve Cryptography Algorithms"">RFC6090</a>],
which has been added to the Secure Shell Public Key list by <a href="./rfc5656">RFC</a>
<a href="./rfc5656">5656</a> [<a href="./rfc5656" title=""Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"">RFC5656</a>] in the public key algorithms list, and
o the SHA-256 algorithm [<a href="#ref-FIPS.180-3.2008">FIPS.180-3.2008</a>] in the SSHFP fingerprint
type list.
Familiarity with DNSSEC, SSH Protocol [<a href="./rfc4251" title=""The Secure Shell (SSH) Protocol Architecture"">RFC4251</a>][RFC4253][<a href="./rfc4250" title=""The Secure Shell (SSH) Protocol Assigned Numbers"">RFC4250</a>],
SSHFP [<a href="./rfc4255" title=""Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints"">RFC4255</a>], and the SHA-2 [<a href="#ref-FIPS.180-3.2008">FIPS.180-3.2008</a>] family of algorithms
is assumed in this document.
<span class="grey">Sury Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6594">RFC 6594</a> ECDSA and SHA-256 Algorithms for SSHFP April 2012</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Language</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. SSHFP Resource Records</span>
The format of the SSHFP RR can be found in <a href="./rfc4255">RFC 4255</a> [<a href="./rfc4255" title=""Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints"">RFC4255</a>].
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. SSHFP Fingerprint Type Specification</span>
The fingerprint type octet identifies the message digest algorithm
used to calculate the fingerprint of the public key.
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. SHA-256 SSHFP Fingerprint Type Specification</span>
SHA-256 fingerprints of the public keys are stored in SSHFP Resource
Records with the fingerprint type 2.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. SSHFP Algorithm Number Specification</span>
The SSHFP Resource Record algorithm number octet describes the
algorithm of the public key.
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. ECDSA SSHFP Algorithm Number Specification</span>
ECDSA public keys are stored in SSHFP Resource Records with the
algorithm number 3.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Implementation Considerations</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Support for SHA-256 Fingerprints</span>
SSHFP-aware Secure Shell implementations SHOULD support the SHA-256
fingerprints for verification of the public key. Secure Shell
implementations that support SHA-256 fingerprints MUST prefer a SHA-
256 fingerprint over SHA-1 if both are available for a server. If
the SHA-256 fingerprint is tested and does not match the SSH public
key received from the SSH server, then the key MUST be rejected
rather than testing the alternative SHA-1 fingerprint.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Support for ECDSA</span>
SSHFP-aware Secure Shell implementations that also implement the
ECDSA for the public key SHOULD support SSHFP fingerprints for ECDSA
public keys.
<span class="grey">Sury Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6594">RFC 6594</a> ECDSA and SHA-256 Algorithms for SSHFP April 2012</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Examples</span>
The following examples provide reference for both the newly defined
value for ECDSA and the use of the SHA-256 fingerprint combined with
both the new and the existing algorithm numbers.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. RSA Public Key</span>
A public key with the following value in OpenSSH format [<a href="./rfc4716" title=""The Secure Shell (SSH) Public Key File Format"">RFC4716</a>]
would appear as follows:
---- BEGIN SSH2 PUBLIC KEY ----
AAAAB3NzaC1yc2EAAAADAQABAAABAQDCUR4JOhxTinzq7QO3bQXW4jmPCCulFsnh
8Yi7MKwpMnd96+T7uV7nEwy+6+GWYu98IxFJByIjFXX/a6BXDp3878wezH1DZ2tN
D/tu/eudz6ErpTFYmnVLyEDARYSzVBNQuIK1UDqvvB6KffJcyt78FpwW27euGkqE
kam7GaurPRAgwXehDB/gMwRtXVRZ+13zYWkAmAY+5OAWVmdXuQVm5kjlvcNzto2H
3m3nqJtD4J9L1lKPuSVVqwJr4/6hibXJkQEvWpUvdOAUw3frKpNwa932fXFk3ke4
rsDjQ/W8GyleMtK3Tx8tE4z1wuowXtYe6Ba8q3LAPs/m2S4pUscx
---- END SSH2 PUBLIC KEY ----
<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>. RSA Public Key with SHA1 Fingerprint</span>
The SSHFP Resource Record for this key would be:
server.example.net IN SSHFP 1 1 ( dd465c09cfa51fb45020cc83316fff
21b9ec74ac )
<span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a>. RSA Public Key with SHA-256 Fingerprint</span>
The SSHFP Resource Record for this key would be:
server.example.net IN SSHFP 1 2 ( b049f950d1397b8fee6a61e4d14a9a
cdc4721e084eff5460bbed80cfaa2c
e2cb )
<span class="grey">Sury Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6594">RFC 6594</a> ECDSA and SHA-256 Algorithms for SSHFP April 2012</span>
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. DSA Public Key</span>
A public key with the following value in OpenSSH format would appear
as follows:
---- BEGIN SSH2 PUBLIC KEY ----
AAAAB3NzaC1kc3MAAACBAPVFrc0U36gWaywbfJzjcv8ef13qAX4EJl8Na6xqvXh1
t+aCJEdS7soRjtvK4KsNhk78DjdtnfhEhyFKHHNz3i6/c/s9lP0UjV7mRAo6nA7A
3Gs6iQElb6O9Fqm6iVSC6bYWilTSB0tYencEEJUoaAua8YQF/uxRzPrReXxGqHnj
AAAAFQDC9M/pli8VIVmEGOO0wC1TeUTN4wAAAIEAgA2Fbkbbeo0+u/qw8mQFOFWZ
pTaqNo7d7jov3majbh5LqEVD7yT3MS1GSGhjgvvhus/ehMTqzYbjTc0szUM9JnwT
7xq15P2ZYDK98IVxrw31jMtsUUEmBqB4DUjTurtcaWmJ9LNaP1/k4bMo0/hotnOc
OVnIPsTLBFWVvdNRxUAAAACAOZcDcK01NTM1qIIYbBqCffrwjQ+9PmsuSKI6nUzf
S4NysXHkdbW5u5VxeXLcwWj5PGbRfoS2P3vwYAmakqgq502wigam18u9nAczUYl+
2kOeOiIRrtSmLfpV7thLOAb8k1ESjIlkbn35jKmTcoMFRXbFmkKRTK8OEnWQ8AVg
6w8=
---- END SSH2 PUBLIC KEY ----
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. DSA Public Key with SHA1 Fingerprint</span>
The SSHFP Resource Record for this key would be:
server.example.net IN SSHFP 2 1 ( 3b6ba6110f5ffcd29469fc1ec2ee25
d61718badd )
<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. DSA Public Key with SHA-256 Fingerprint</span>
The SSHFP Resource Record for this key would be:
server.example.net IN SSHFP 2 2 ( f9b8a6a460639306f1b38910456a6a
e1018a253c47ecec12db77d7a0878b
4d83 )
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. ECDSA Public Key</span>
A public key with the following value in OpenSSH format would appear
as follows:
---- BEGIN SSH2 PUBLIC KEY ----
AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBAD+9COUiX7W
YgcvIOdI8+djdoFDVUTxNrcog8sSYdbIzeG+bYdsssvcyy/nRfVhXC5QBCk8IThq
s7D4/lFxX5g=
---- END SSH2 PUBLIC KEY ----
<span class="grey">Sury Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6594">RFC 6594</a> ECDSA and SHA-256 Algorithms for SSHFP April 2012</span>
<span class="h4"><a class="selflink" id="section-5.3.1" href="#section-5.3.1">5.3.1</a>. ECDSA Public Key with SHA1 Fingerprint</span>
The SSHFP Resource Record for this key would be:
server.example.net IN SSHFP 3 1 ( c64607a28c5300fec1180b6e417b92
2943cffcdd )
<span class="h4"><a class="selflink" id="section-5.3.2" href="#section-5.3.2">5.3.2</a>. ECDSA Public Key with SHA-256 Fingerprint</span>
The SSHFP Resource Record for this key would be:
server.example.net IN SSHFP 3 2 ( 821eb6c1c98d9cc827ab7f456304c0
f14785b7008d9e8646a8519de80849
afc7 )
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
This document updates the IANA registry "SSHFP RR Types for public
key algorithms" and "SSHFP RR types for fingerprint types"
[<a href="#ref-SSHFPVALS" title=""DNS SSHFP Resource Records Parameters"">SSHFPVALS</a>].
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. SSHFP RR Types for Public Key Algorithms</span>
The following entries have been added to the "SSHFP RR Types for
public key algorithms" registry:
+-------+-------------+------------+
| Value | Description | Reference |
+-------+-------------+------------+
| 3 | ECDSA | [This doc] |
+-------+-------------+------------+
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. SSHFP RR Types for Fingerprint Types</span>
The following entries have been added to the "SSHFP RR types for
fingerprint types" registry:
+-------+-------------+------------+
| Value | Description | Reference |
+-------+-------------+------------+
| 2 | SHA-256 | [This doc] |
+-------+-------------+------------+
<span class="grey">Sury Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6594">RFC 6594</a> ECDSA and SHA-256 Algorithms for SSHFP April 2012</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
Please see the security considerations in [<a href="./rfc4255" title=""Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints"">RFC4255</a>] for SSHFP
Resource Records and [<a href="./rfc5656" title=""Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer"">RFC5656</a>] for the ECDSA.
Users of SSHFP are encouraged to deploy SHA-256 as soon as
implementations allow for it. The SHA-2 family of algorithms is
widely believed to be more resilient to attack than SHA-1, and
confidence in SHA-1's strength is being eroded by recently announced
attacks [IACR2007/474]. Regardless of whether or not the attacks on
SHA-1 will affect SSHFP, it is believed (at the time of this writing)
that SHA-256 is the better choice for use in SSHFP records.
SHA-256 is considered sufficiently strong for the immediate future,
but predictions about future development in cryptography and
cryptanalysis are beyond the scope of this document.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-FIPS.180-3.2008">FIPS.180-3.2008</a>]
National Institute of Standards and Technology, "Secure
Hash Standard (SHS)", FIPS PUB 180-3, October 2008,
<<a href="http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf">http://csrc.nist.gov/publications/fips/fips180-3/</a>
<a href="http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf">fips180-3_final.pdf</a>>.
[<a id="ref-RFC1034">RFC1034</a>] Mockapetris, P., "Domain names - concepts and
facilities", STD 13, <a href="./rfc1034">RFC 1034</a>, November 1987.
[<a id="ref-RFC1035">RFC1035</a>] Mockapetris, P., "Domain names - implementation and
specification", STD 13, <a href="./rfc1035">RFC 1035</a>, November 1987.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC4250">RFC4250</a>] Lehtinen, S. and C. Lonvick, "The Secure Shell (SSH)
Protocol Assigned Numbers", <a href="./rfc4250">RFC 4250</a>, January 2006.
[<a id="ref-RFC4251">RFC4251</a>] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)
Protocol Architecture", <a href="./rfc4251">RFC 4251</a>, January 2006.
[<a id="ref-RFC4253">RFC4253</a>] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)
Transport Layer Protocol", <a href="./rfc4253">RFC 4253</a>, January 2006.
[<a id="ref-RFC4255">RFC4255</a>] Schlyter, J. and W. Griffin, "Using DNS to Securely
Publish Secure Shell (SSH) Key Fingerprints", <a href="./rfc4255">RFC 4255</a>,
January 2006.
<span class="grey">Sury Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6594">RFC 6594</a> ECDSA and SHA-256 Algorithms for SSHFP April 2012</span>
[<a id="ref-RFC5656">RFC5656</a>] Stebila, D. and J. Green, "Elliptic Curve Algorithm
Integration in the Secure Shell Transport Layer",
<a href="./rfc5656">RFC 5656</a>, December 2009.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[IACR2007/474]
Cochran, M., "Notes on the Wang et al. 2^63 SHA-1
Differential Path", IACR 2007/474,
<<a href="http://eprint.iacr.org/2007/474.pdf">http://eprint.iacr.org/2007/474.pdf</a>>.
[<a id="ref-RFC4033">RFC4033</a>] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "DNS Security Introduction and Requirements",
<a href="./rfc4033">RFC 4033</a>, March 2005.
[<a id="ref-RFC4034">RFC4034</a>] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Resource Records for the DNS Security Extensions",
<a href="./rfc4034">RFC 4034</a>, March 2005.
[<a id="ref-RFC4035">RFC4035</a>] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Protocol Modifications for the DNS Security
Extensions", <a href="./rfc4035">RFC 4035</a>, March 2005.
[<a id="ref-RFC4716">RFC4716</a>] Galbraith, J. and R. Thayer, "The Secure Shell (SSH)
Public Key File Format", <a href="./rfc4716">RFC 4716</a>, November 2006.
[<a id="ref-RFC6090">RFC6090</a>] McGrew, D., Igoe, K., and M. Salter, "Fundamental
Elliptic Curve Cryptography Algorithms", <a href="./rfc6090">RFC 6090</a>,
February 2011.
[<a id="ref-SSHFPVALS">SSHFPVALS</a>] IANA, "DNS SSHFP Resource Records Parameters",
<<a href="http://www.iana.org/assignments/dns-sshfp-rr-parameters">http://www.iana.org/assignments/</a>
<a href="http://www.iana.org/assignments/dns-sshfp-rr-parameters">dns-sshfp-rr-parameters</a>>.
Author's Address
Ondrej Sury
CZ.NIC
Americka 23
120 00 Praha 2
Czech Republic
Phone: +420 222 745 110
EMail: ondrej.sury@nic.cz
Sury Standards Track [Page 9]
</pre>
|
