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
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
|
<pre>Network Working Group J. Jansen
Request for Comments: 5702 NLnet Labs
Category: Standards Track October 2009
<span class="h1">Use of SHA-2 Algorithms with RSA in</span>
<span class="h1">DNSKEY and RRSIG Resource Records for DNSSEC</span>
Abstract
This document describes how to produce RSA/SHA-256 and RSA/SHA-512
DNSKEY and RRSIG resource records for use in the Domain Name System
Security Extensions (<a href="./rfc4033">RFC 4033</a>, <a href="./rfc4034">RFC 4034</a>, and <a href="./rfc4035">RFC 4035</a>).
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (c) 2009 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
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 BSD License.
<span class="grey">Jansen Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5702">RFC 5702</a> DNSSEC RSA/SHA-2 October 2009</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. DNSKEY Resource Records .........................................<a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. RSA/SHA-256 DNSKEY Resource Records ........................<a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. RSA/SHA-512 DNSKEY Resource Records ........................<a href="#page-3">3</a>
<a href="#section-3">3</a>. RRSIG Resource Records ..........................................<a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. RSA/SHA-256 RRSIG Resource Records .........................<a href="#page-4">4</a>
<a href="#section-3.2">3.2</a>. RSA/SHA-512 RRSIG Resource Records .........................<a href="#page-4">4</a>
<a href="#section-4">4</a>. Deployment Considerations .......................................<a href="#page-5">5</a>
<a href="#section-4.1">4.1</a>. Key Sizes ..................................................<a href="#page-5">5</a>
<a href="#section-4.2">4.2</a>. Signature Sizes ............................................<a href="#page-5">5</a>
<a href="#section-5">5</a>. Implementation Considerations ...................................<a href="#page-5">5</a>
<a href="#section-5.1">5.1</a>. Support for SHA-2 Signatures ...............................<a href="#page-5">5</a>
<a href="#section-5.2">5.2</a>. Support for NSEC3 Denial of Existence ......................<a href="#page-5">5</a>
<a href="#section-6">6</a>. Examples ........................................................<a href="#page-6">6</a>
<a href="#section-6.1">6.1</a>. RSA/SHA-256 Key and Signature ..............................<a href="#page-6">6</a>
<a href="#section-6.2">6.2</a>. RSA/SHA-512 Key and Signature ..............................<a href="#page-7">7</a>
<a href="#section-7">7</a>. IANA Considerations .............................................<a href="#page-8">8</a>
<a href="#section-8">8</a>. Security Considerations .........................................<a href="#page-8">8</a>
8.1. SHA-1 versus SHA-2 Considerations for RRSIG
Resource Records ...........................................<a href="#page-8">8</a>
<a href="#section-8.2">8.2</a>. Signature Type Downgrade Attacks ...........................<a href="#page-8">8</a>
<a href="#section-9">9</a>. Acknowledgments .................................................<a href="#page-9">9</a>
<a href="#section-10">10</a>. References .....................................................<a href="#page-9">9</a>
<a href="#section-10.1">10.1</a>. Normative References ......................................<a href="#page-9">9</a>
<a href="#section-10.2">10.2</a>. Informative References ....................................<a href="#page-9">9</a>
<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 DNS has been extended to use
cryptographic keys and digital signatures for the verification of the
authenticity and integrity of its data. [<a href="./rfc4033" title=""DNS Security Introduction and Requirements"">RFC4033</a>], [<a href="./rfc4034" title=""Resource Records for the DNS Security Extensions"">RFC4034</a>], and
[<a href="./rfc4035" title=""Protocol Modifications for the DNS Security Extensions"">RFC4035</a>] describe these DNS Security Extensions, called DNSSEC.
<a href="./rfc4034">RFC 4034</a> describes how to store DNSKEY and RRSIG resource records,
and specifies a list of cryptographic algorithms to use. This
document extends that list with the algorithms RSA/SHA-256 and RSA/
SHA-512, and specifies how to store DNSKEY data and how to produce
RRSIG resource records with these hash algorithms.
Familiarity with DNSSEC, RSA, 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">Jansen Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5702">RFC 5702</a> DNSSEC RSA/SHA-2 October 2009</span>
To refer to both SHA-256 and SHA-512, this document will use the name
SHA-2. This is done to improve readability. When a part of text is
specific for either SHA-256 or SHA-512, their specific names are
used. The same goes for RSA/SHA-256 and RSA/SHA-512, which will be
grouped using the name RSA/SHA-2.
The term "SHA-2" is not officially defined but is usually used to
refer to the collection of the algorithms SHA-224, SHA-256, SHA-384,
and SHA-512. Since SHA-224 and SHA-384 are not used in DNSSEC, SHA-2
will only refer to SHA-256 and SHA-512 in this document.
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" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. DNSKEY Resource Records</span>
The format of the DNSKEY RR can be found in [<a href="./rfc4034" title=""Resource Records for the DNS Security Extensions"">RFC4034</a>]. [<a href="./rfc3110" title=""RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)"">RFC3110</a>]
describes the use of RSA/SHA-1 for DNSSEC signatures.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. RSA/SHA-256 DNSKEY Resource Records</span>
RSA public keys for use with RSA/SHA-256 are stored in DNSKEY
resource records (RRs) with the algorithm number 8.
For interoperability, as in [<a href="./rfc3110" title=""RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)"">RFC3110</a>], the key size of RSA/SHA-256
keys MUST NOT be less than 512 bits and MUST NOT be more than 4096
bits.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. RSA/SHA-512 DNSKEY Resource Records</span>
RSA public keys for use with RSA/SHA-512 are stored in DNSKEY
resource records (RRs) with the algorithm number 10.
The key size of RSA/SHA-512 keys MUST NOT be less than 1024 bits and
MUST NOT be more than 4096 bits.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. RRSIG Resource Records</span>
The value of the signature field in the RRSIG RR follows the RSASSA-
PKCS1-v1_5 signature scheme and is calculated as follows. The values
for the RDATA fields that precede the signature data are specified in
[<a href="./rfc4034" title=""Resource Records for the DNS Security Extensions"">RFC4034</a>].
<span class="grey">Jansen Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5702">RFC 5702</a> DNSSEC RSA/SHA-2 October 2009</span>
hash = SHA-XXX(data)
Here XXX is either 256 or 512, depending on the algorithm used, as
specified in FIPS PUB 180-3; "data" is the wire format data of the
resource record set that is signed, as specified in [<a href="./rfc4034" title=""Resource Records for the DNS Security Extensions"">RFC4034</a>].
signature = ( 00 | 01 | FF* | 00 | prefix | hash ) ** e (mod n)
Here "|" is concatenation; "00", "01", "FF", and "00" are fixed
octets of corresponding hexadecimal value; "e" is the private
exponent of the signing RSA key; and "n" is the public modulus of the
signing key. The FF octet MUST be repeated the exact number of times
so that the total length of the concatenated term in parentheses
equals the length of the modulus of the signer's public key ("n").
The "prefix" is intended to make the use of standard cryptographic
libraries easier. These specifications are taken directly from the
specifications of RSASSA-PKCS1-v1_5 in PKCS #1 v2.1 (<a href="./rfc3447#section-8.2">Section 8.2 of
[RFC3447]</a>), and EMSA-PKCS1-v1_5 encoding in PKCS #1 v2.1 (<a href="./rfc3447#section-9.2">Section 9.2
of [RFC3447]</a>). The prefixes for the different algorithms are
specified below.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. RSA/SHA-256 RRSIG Resource Records</span>
RSA/SHA-256 signatures are stored in the DNS using RRSIG resource
records (RRs) with algorithm number 8.
The prefix is the ASN.1 DER SHA-256 algorithm designator prefix, as
specified in PKCS #1 v2.1 [<a href="./rfc3447" title=""Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1"">RFC3447</a>]:
hex 30 31 30 0d 06 09 60 86 48 01 65 03 04 02 01 05 00 04 20
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. RSA/SHA-512 RRSIG Resource Records</span>
RSA/SHA-512 signatures are stored in the DNS using RRSIG resource
records (RRs) with algorithm number 10.
The prefix is the ASN.1 DER SHA-512 algorithm designator prefix, as
specified in PKCS #1 v2.1 [<a href="./rfc3447" title=""Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1"">RFC3447</a>]:
hex 30 51 30 0d 06 09 60 86 48 01 65 03 04 02 03 05 00 04 40
<span class="grey">Jansen Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5702">RFC 5702</a> DNSSEC RSA/SHA-2 October 2009</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Deployment Considerations</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Key Sizes</span>
Apart from the restrictions in <a href="#section-2">Section 2</a>, this document will not
specify what size of keys to use. That is an operational issue and
depends largely on the environment and intended use. A good starting
point for more information would be NIST SP 800-57 [<a href="#ref-NIST800-57">NIST800-57</a>].
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Signature Sizes</span>
In this family of signing algorithms, the size of signatures is
related to the size of the key and not to the hashing algorithm used
in the signing process. Therefore, RRSIG resource records produced
with RSA/SHA-256 or RSA/SHA-512 will have the same size as those
produced with RSA/SHA-1, if the keys have the same length.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Implementation Considerations</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Support for SHA-2 Signatures</span>
DNSSEC-aware implementations SHOULD be able to support RRSIG and
DNSKEY resource records created with the RSA/SHA-2 algorithms as
defined in this document.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Support for NSEC3 Denial of Existence</span>
[<a id="ref-RFC5155">RFC5155</a>] defines new algorithm identifiers for existing signing
algorithms, to indicate that zones signed with these algorithm
identifiers can use NSEC3 as well as NSEC records to provide denial
of existence. That mechanism was chosen to protect implementations
predating <a href="./rfc5155">RFC 5155</a> from encountering resource records about which
they could not know. This document does not define such algorithm
aliases.
A DNSSEC validator that implements RSA/SHA-2 MUST be able to validate
negative answers in the form of both NSEC and NSEC3 with hash
algorithm 1, as defined in [<a href="./rfc5155" title=""DNS Security (DNSSEC) Hashed Authenticated Denial of Existence"">RFC5155</a>]. An authoritative server that
does not implement NSEC3 MAY still serve zones that use RSA/SHA-2
with NSEC denial of existence.
<span class="grey">Jansen Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5702">RFC 5702</a> DNSSEC RSA/SHA-2 October 2009</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Examples</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. RSA/SHA-256 Key and Signature</span>
Given a private key with the following values (in Base64):
Private-key-format: v1.2
Algorithm: 8 (RSASHA256)
Modulus: wVwaxrHF2CK64aYKRUibLiH30KpPuPBjel7E8ZydQW1HYWHfoGm
idzC2RnhwCC293hCzw+TFR2nqn8OVSY5t2Q==
PublicExponent: AQAB
PrivateExponent: UR44xX6zB3eaeyvTRzmskHADrPCmPWnr8dxsNwiDGHzrMKLN+i/
HAam+97HxIKVWNDH2ba9Mf1SA8xu9dcHZAQ==
Prime1: 4c8IvFu1AVXGWeFLLFh5vs7fbdzdC6U82fduE6KkSWk=
Prime2: 2zZpBE8ZXVnL74QjG4zINlDfH+EOEtjJJ3RtaYDugvE=
Exponent1: G2xAPFfK0KGxGANDVNxd1K1c9wOmmJ51mGbzKFFNMFk=
Exponent2: GYxP1Pa7CAwtHm8SAGX594qZVofOMhgd6YFCNyeVpKE=
Coefficient: icQdNRjlZGPmuJm2TIadubcO8X7V4y07aVhX464tx8Q=
The DNSKEY record for this key would be:
example.net. 3600 IN DNSKEY (256 3 8 AwEAAcFcGsaxxdgiuuGmCkVI
my4h99CqT7jwY3pexPGcnUFtR2Fh36BponcwtkZ4cAgtvd4Qs8P
kxUdp6p/DlUmObdk= );{id = 9033 (zsk), size = 512b}
With this key, sign the following RRSet, consisting of 1 A record:
www.example.net. 3600 IN A 192.0.2.91
If the inception date is set at 00:00 hours on January 1st, 2000, and
the expiration date at 00:00 hours on January 1st, 2030, the
following signature should be created:
www.example.net. 3600 IN RRSIG (A 8 3 3600 20300101000000
20000101000000 9033 example.net. kRCOH6u7l0QGy9qpC9
l1sLncJcOKFLJ7GhiUOibu4teYp5VE9RncriShZNz85mwlMgNEa
cFYK/lPtPiVYP4bwg==);{id = 9033}
<span class="grey">Jansen Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5702">RFC 5702</a> DNSSEC RSA/SHA-2 October 2009</span>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. RSA/SHA-512 Key and Signature</span>
Given a private key with the following values (in Base64):
Private-key-format: v1.2
Algorithm: 10 (RSASHA512)
Modulus: 0eg1M5b563zoq4k5ZEOnWmd2/BvpjzedJVdfIsDcMuuhE5SQ3pf
Q7qmdaeMlC6Nf8DKGoUPGPXe06cP27/WRODtxXquSUytkO0kJDk
8KX8PtA0+yBWwy7UnZDyCkynO00Uuk8HPVtZeMO1pHtlAGVnc8V
jXZlNKdyit99waaE4s=
PublicExponent: AQAB
PrivateExponent: rFS1IPbJllFFgFc33B5DDlC1egO8e81P4fFadODbp56V7sphKa6
AZQCx8NYAew6VXFFPAKTw41QdHnK5kIYOwxvfFDjDcUGza88qbj
yrDPSJenkeZbISMUSSqy7AMFzEolkk6WSn6k3thUVRgSlqDoOV3
SEIAsrB043XzGrKIVE=
Prime1: 8mbtsu9Tl9v7tKSHdCIeprLIQXQLzxlSZun5T1n/OjvXSUtvD7x
nZJ+LHqaBj1dIgMbCq2U8O04QVcK3TS9GiQ==
Prime2: 3a6gkfs74d0Jb7yL4j4adAif4fcp7ZrGt7G5NRVDDY/Mv4TERAK
Ma0TKN3okKE0A7X+Rv2K84mhT4QLDlllEcw==
Exponent1: v3D5A9uuCn5rgVR7wgV8ba0/KSpsdSiLgsoA42GxiB1gvvs7gJM
MmVTDu/ZG1p1ZnpLbhh/S/Qd/MSwyNlxC+Q==
Exponent2: m+ezf9dsDvYQK+gzjOLWYeKq5xWYBEYFGa3BLocMiF4oxkzOZ3J
PZSWU/h1Fjp5RV7aPP0Vmx+hNjYMPIQ8Y5w==
Coefficient: Je5YhYpUron/WdOXjxNAxDubAp3i5X7UOUfhJcyIggqwY86IE0Q
/Bk0Dw4SC9zxnsimmdBXW2Izd8Lwuk8FQcQ==
The DNSKEY record for this key would be:
example.net. 3600 IN DNSKEY (256 3 10 AwEAAdHoNTOW+et86KuJOWRD
p1pndvwb6Y83nSVXXyLA3DLroROUkN6X0O6pnWnjJQujX/AyhqFD
xj13tOnD9u/1kTg7cV6rklMrZDtJCQ5PCl/D7QNPsgVsMu1J2Q8g
pMpztNFLpPBz1bWXjDtaR7ZQBlZ3PFY12ZTSncorffcGmhOL
);{id = 3740 (zsk), size = 1024b}
With this key, sign the following RRSet, consisting of 1 A record:
www.example.net. 3600 IN A 192.0.2.91
If the inception date is set at 00:00 hours on January 1st, 2000, and
the expiration date at 00:00 hours on January 1st, 2030, the
following signature should be created:
www.example.net. 3600 IN RRSIG (A 10 3 3600 20300101000000
20000101000000 3740 example.net. tsb4wnjRUDnB1BUi+t
6TMTXThjVnG+eCkWqjvvjhzQL1d0YRoOe0CbxrVDYd0xDtsuJRa
eUw1ep94PzEWzr0iGYgZBWm/zpq+9fOuagYJRfDqfReKBzMweOL
DiNa8iP5g9vMhpuv6OPlvpXwm9Sa9ZXIbNl1MBGk0fthPgxdDLw
=);{id = 3740}
<span class="grey">Jansen Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc5702">RFC 5702</a> DNSSEC RSA/SHA-2 October 2009</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
This document updates the IANA registry "DNS SECURITY ALGORITHM
NUMBERS -- per [<a href="./rfc4035" title=""Protocol Modifications for the DNS Security Extensions"">RFC4035</a>]" (<a href="http://www.iana.org/protocols">http://www.iana.org/protocols</a>). The
following entries are added to the registry:
Zone Trans.
Value Description Mnemonic Signing Sec. References
8 RSA/SHA-256 RSASHA256 Y * <a href="./rfc5702">RFC 5702</a>
10 RSA/SHA-512 RSASHA512 Y * <a href="./rfc5702">RFC 5702</a>
* There has been no determination of standardization of the use of
this algorithm with Transaction Security.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. SHA-1 versus SHA-2 Considerations for RRSIG Resource Records</span>
Users of DNSSEC are encouraged to deploy SHA-2 as soon as software
implementations allow for it. SHA-2 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. Regardless of whether or
not the attacks on SHA-1 will affect DNSSEC, it is believed (at the
time of this writing) that SHA-2 is the better choice for use in
DNSSEC records.
SHA-2 is considered sufficiently strong for the immediate future, but
predictions about future development in cryptography and
cryptanalysis are beyond the scope of this document.
The signature scheme RSASSA-PKCS1-v1_5 is chosen to match the one
used for RSA/SHA-1 signatures. This should ease implementation of
the new hashing algorithms in DNSSEC software.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Signature Type Downgrade Attacks</span>
Since each RRSet MUST be signed with each algorithm present in the
DNSKEY RRSet at the zone apex (see <a href="./rfc4035#section-2.2">Section 2.2 of [RFC4035]</a>), a
malicious party cannot filter out the RSA/SHA-2 RRSIG and force the
validator to use the RSA/SHA-1 signature if both are present in the
zone. This should provide resilience against algorithm downgrade
attacks, if the validator supports RSA/SHA-2.
<span class="grey">Jansen Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc5702">RFC 5702</a> DNSSEC RSA/SHA-2 October 2009</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgments</span>
This document is a minor extension to [<a href="./rfc4034" title=""Resource Records for the DNS Security Extensions"">RFC4034</a>]. Also, we try to
follow the documents [<a href="./rfc3110" title=""RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)"">RFC3110</a>] and [<a href="./rfc4509" title=""Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)"">RFC4509</a>] for consistency. The
authors of and contributors to these documents are gratefully
acknowledged for their hard work.
The following people provided additional feedback and text: Jaap
Akkerhuis, Mark Andrews, Roy Arends, Rob Austein, Francis Dupont,
Miek Gieben, Alfred Hoenes, Paul Hoffman, Peter Koch, Scott Rose,
Michael St. Johns, and Wouter Wijngaards.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.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", FIPS PUB 180-3, October 2008.
[<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-RFC3110">RFC3110</a>] Eastlake, D., "RSA/SHA-1 SIGs and RSA KEYs in the Domain
Name System (DNS)", <a href="./rfc3110">RFC 3110</a>, May 2001.
[<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.
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-NIST800-57">NIST800-57</a>]
Barker, E., Barker, W., Burr, W., Polk, W., and M. Smid,
"Recommendations for Key Management", NIST SP 800-57,
March 2007.
[<a id="ref-RFC3447">RFC3447</a>] Jonsson, J. and B. Kaliski, "Public-Key Cryptography
Standards (PKCS) #1: RSA Cryptography Specifications
Version 2.1", <a href="./rfc3447">RFC 3447</a>, February 2003.
<span class="grey">Jansen Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc5702">RFC 5702</a> DNSSEC RSA/SHA-2 October 2009</span>
[<a id="ref-RFC4509">RFC4509</a>] Hardaker, W., "Use of SHA-256 in DNSSEC Delegation Signer
(DS) Resource Records (RRs)", <a href="./rfc4509">RFC 4509</a>, May 2006.
[<a id="ref-RFC5155">RFC5155</a>] Laurie, B., Sisson, G., Arends, R., and D. Blacka, "DNS
Security (DNSSEC) Hashed Authenticated Denial of
Existence", <a href="./rfc5155">RFC 5155</a>, March 2008.
Author's Address
Jelte Jansen
NLnet Labs
Science Park 140
1098 XG Amsterdam
NL
EMail: jelte@NLnetLabs.nl
URI: <a href="http://www.nlnetlabs.nl/">http://www.nlnetlabs.nl/</a>
Jansen Standards Track [Page 10]
</pre>
|
