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>Internet Engineering Task Force (IETF) S. Turner
Request for Comments: 5754 IECA
Updates: <a href="./rfc3370">3370</a> January 2010
Category: Standards Track
ISSN: 2070-1721
<span class="h1">Using SHA2 Algorithms with Cryptographic Message Syntax</span>
Abstract
This document describes the conventions for using the Secure Hash
Algorithm (SHA) message digest algorithms (SHA-224, SHA-256, SHA-384,
SHA-512) with the Cryptographic Message Syntax (CMS). It also
describes the conventions for using these algorithms with the CMS and
the Digital Signature Algorithm (DSA), Rivest Shamir Adleman (RSA),
and Elliptic Curve DSA (ECDSA) signature algorithms. Further, it
provides SMIMECapabilities attribute values for each algorithm.
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
Internet 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/rfc5754">http://www.rfc-editor.org/info/rfc5754</a>.
Copyright Notice
Copyright (c) 2010 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 Simplified BSD License.
<span class="grey">Turner Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5754">RFC 5754</a> Using SHA2 Algorithms with CMS January 2010</span>
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Conventions Used in This Document ..........................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Message Digest Algorithms .......................................<a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. SHA-224 ....................................................<a href="#page-4">4</a>
<a href="#section-2.2">2.2</a>. SHA-256 ....................................................<a href="#page-5">5</a>
<a href="#section-2.3">2.3</a>. SHA-384 ....................................................<a href="#page-5">5</a>
<a href="#section-2.4">2.4</a>. SHA-512 ....................................................<a href="#page-5">5</a>
<a href="#section-3">3</a>. Signature Algorithms ............................................<a href="#page-6">6</a>
<a href="#section-3.1">3.1</a>. DSA ........................................................<a href="#page-6">6</a>
<a href="#section-3.2">3.2</a>. RSA ........................................................<a href="#page-7">7</a>
<a href="#section-3.3">3.3</a>. ECDSA ......................................................<a href="#page-8">8</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-9">9</a>
<a href="#section-5">5</a>. References ......................................................<a href="#page-9">9</a>
<a href="#section-5.1">5.1</a>. Normative References .......................................<a href="#page-9">9</a>
<a href="#section-5.2">5.2</a>. Informative References ....................................<a href="#page-10">10</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document specifies the algorithm identifiers and specifies
parameters for the message digest algorithms SHA-224, SHA-256,
SHA-384, and SHA-512 for use with the Cryptographic Message Syntax
(CMS) [<a href="./rfc5652" title=""Cryptographic Message Syntax (CMS)"">RFC5652</a>]. The message digest algorithms are defined in [<a href="#ref-SHS" title=" FIPS Publication 180-3: Secure Hash Standard">SHS</a>]
and reference code is provided in [<a href="./rfc4634" title=""US Secure Hash Algorithms (SHA and HMAC-SHA)"">RFC4634</a>].
This document also specifies the algorithm identifiers and parameters
for use of SHA-224, SHA-256, SHA-384, and SHA-512 with DSA [<a href="#ref-DSS" title=" FIPS Publication 186-3: Digital Signature Standard">DSS</a>], RSA
(RSASSA-PKCS1-v1_5) [<a href="./rfc3447" title=""Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1"">RFC3447</a>], and ECDSA [<a href="#ref-DSS" title=" FIPS Publication 186-3: Digital Signature Standard">DSS</a>].
This document does not define new identifiers; they are taken from
[<a href="./rfc3874" title=""A 224-bit One-way Hash Function: SHA-224"">RFC3874</a>], [<a href="./rfc4055" title=""Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC4055</a>], and [<a href="./rfc5758" title=""Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSA"">RFC5758</a>]. Additionally, the parameters
follow the conventions specified therein. Therefore, there is no
Abstract Syntax Notation One (ASN.1) module included in this
document.
<span class="grey">Turner Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5754">RFC 5754</a> Using SHA2 Algorithms with CMS January 2010</span>
Note that [<a href="./rfc4231" title=""Identifiers and Test Vectors for HMAC- SHA-224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512"">RFC4231</a>] specifies the conventions for the message
authentication code (MAC) algorithms: Hashed MAC (HMAC) with SHA-224,
HMAC with SHA-256, HMAC with SHA-384, and HMAC with SHA-512.
In the CMS, the various algorithm identifiers use the
AlgorithmIdentifier syntax, which is included here for convenience:
AlgorithmIdentifier ::= SEQUENCE {
algorithm OBJECT IDENTIFIER,
parameters ANY DEFINED BY algorithm OPTIONAL }
This document also specifies the SMIMECapabilities attribute values
[<a href="./rfc5751" title=""Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification"">RFC5751</a>] for each algorithm. The values provided are for the
SMIMECapability field, which is included here for convenience:
SMIMECapability ::= SEQUENCE {
capabilityID OBJECT IDENTIFIER,
parameters ANY DEFINED BY capabilityID OPTIONAL }
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Conventions Used in This Document</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" 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>. Message Digest Algorithms</span>
Digest algorithm identifiers are located in the SignedData
digestAlgorithms field, the SignerInfo digestAlgorithm field, the
DigestedData digestAlgorithm field, and the AuthenticatedData
digestAlgorithm field. The object identifiers are taken from
[<a href="./rfc4055" title=""Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC4055</a>].
Digest values are located in the DigestedData digest field and the
Message Digest authenticated attribute. In addition, digest values
are input to signature algorithms.
The digest algorithm identifiers use the AlgorithmIdentifier syntax
elaborated upon in <a href="#section-1">Section 1</a>.
The algorithm field and SMIMECapabilities attribute are discussed in
Sections <a href="#section-2.1">2.1</a>-<a href="#section-2.4">2.4</a> for each message digest algorithm. <a href="#section-3">Section 3</a>
provides some signatures that use SHA2 algorithms. Consult the
signature algorithm definitions for the procedures to compute the
digest values (i.e., DigestInfo).
<span class="grey">Turner Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5754">RFC 5754</a> Using SHA2 Algorithms with CMS January 2010</span>
The AlgorithmIdentifier parameters field is OPTIONAL.
Implementations MUST accept SHA2 AlgorithmIdentifiers with absent
parameters. Implementations MUST accept SHA2 AlgorithmIdentifiers
with NULL parameters. Implementations MUST generate SHA2
AlgorithmIdentifiers with absent parameters.
NOTE: There are two possible encodings for the AlgorithmIdentifier
parameters field associated with these object identifiers. The two
alternatives arise from the loss of the OPTIONAL associated with the
algorithm identifier parameters when the 1988 syntax for
AlgorithmIdentifier was translated into the 1997 syntax. Later, the
OPTIONAL was recovered via a defect report, but by then many people
thought that algorithm parameters were mandatory. Because of this
history, some implementations encode parameters as a NULL element
while others omit them entirely. The correct encoding is to omit the
parameters field; however, when some uses of these algorithms were
defined, it was done using the NULL parameters rather than absent
parameters. For example, PKCS#1 [<a href="./rfc3447" title=""Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1"">RFC3447</a>] requires that the padding
used for RSA signatures (EMSA-PKCS1-v1_5) MUST use SHA2
AlgorithmIdentifiers with NULL parameters (to clarify, the
requirement "MUST generate SHA2 AlgorithmIdentifiers with absent
parameters" in the previous paragraph does not apply to this
padding).
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. SHA-224</span>
The SHA-224 message digest algorithm is defined in [<a href="#ref-SHS" title=" FIPS Publication 180-3: Secure Hash Standard">SHS</a>]. The
algorithm identifier for SHA-224 is:
id-sha224 OBJECT IDENTIFIER ::= {
joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101)
csor(3) nistalgorithm(4) hashalgs(2) 4 }
The parameters are as specified in the beginning of <a href="#section-2">Section 2</a>.
The SMIMECapabilities attribute value indicates support for SHA-224
in a SEQUENCE with the capabilityID field containing the object
identifier id-sha224 with absent parameters. The DER encoding for
this SMIMECapability is:
id-sha224: 30 0b 06 09 60 86 48 01 65 03 04 02 04
<span class="grey">Turner Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5754">RFC 5754</a> Using SHA2 Algorithms with CMS January 2010</span>
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. SHA-256</span>
The SHA-256 message digest algorithm is defined in [<a href="#ref-SHS" title=" FIPS Publication 180-3: Secure Hash Standard">SHS</a>]. The
algorithm identifier for SHA-256 is:
id-sha256 OBJECT IDENTIFIER ::= {
joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101)
csor(3) nistalgorithm(4) hashalgs(2) 1 }
The parameters are as specified in the beginning of <a href="#section-2">Section 2</a>.
The SMIMECapabilities attribute value indicates support for SHA-256
in a SEQUENCE with the capabilityID field containing the object
identifier id-sha256 with absent parameters. The DER encoding for
this SMIMECapability value is:
id-sha256: 30 0b 06 09 60 86 48 01 65 03 04 02 01
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. SHA-384</span>
The SHA-384 message digest algorithm is defined in [<a href="#ref-SHS" title=" FIPS Publication 180-3: Secure Hash Standard">SHS</a>]. The
algorithm identifier for SHA-384 is:
id-sha384 OBJECT IDENTIFIER ::= {
joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101)
csor(3) nistalgorithm(4) hashalgs(2) 2 }
The parameters are as specified in the beginning of <a href="#section-2">Section 2</a>.
The SMIMECapabilities attribute value indicates support for SHA-384
in a SEQUENCE with the capabilityID field containing the object
identifier id-sha384 with absent parameters. The DER encoding for
this SMIMECapability value is:
id-sha384: 30 0b 06 09 60 86 48 01 65 03 04 02 02
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. SHA-512</span>
The SHA-512 message digest algorithm is defined in [<a href="#ref-SHS" title=" FIPS Publication 180-3: Secure Hash Standard">SHS</a>]. The
algorithm identifier for SHA-512 is:
id-sha512 OBJECT IDENTIFIER ::= {
joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101)
csor(3) nistalgorithm(4) hashalgs(2) 3 }
The parameters are as specified in the beginning of <a href="#section-2">Section 2</a>.
<span class="grey">Turner Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5754">RFC 5754</a> Using SHA2 Algorithms with CMS January 2010</span>
The SMIMECapabilities attribute value indicates support for SHA-384
in a SEQUENCE with the capabilityID field containing the object
identifier id-sha384 with absent parameters. The DER encoding for
this SMIMECapability value is:
id-sha512: 30 0b 06 09 60 86 48 01 65 03 04 02 03
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Signature Algorithms</span>
This section specifies the conventions employed by CMS
implementations that support DSA, RSA, and ECDSA with SHA2
algorithms.
Signature algorithm identifiers are located in the SignerInfo
signatureAlgorithm field of SignedData. Also, signature algorithm
identifiers are located in the SignerInfo signatureAlgorithm field of
countersignature attributes.
Signature values are located in the SignerInfo signature field of
SignedData. Also, signature values are located in the SignerInfo
signature field of countersignature attributes.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. DSA</span>
<a href="./rfc3370#section-3.1">[RFC3370], Section 3.1</a>, specifies the conventions for DSA with SHA-1
public key algorithm identifiers, parameters, public keys, and
signature values. DSA with SHA2 algorithms uses the same conventions
for these public key algorithm identifiers, parameters, public keys,
and signature values. DSA MAY be used with SHA-224 and SHA-256. The
object identifiers are taken from [<a href="./rfc5758" title=""Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSA"">RFC5758</a>].
DSA has not been specified with SHA-384 and SHA-512. SHA-384 and
SHA-512 are not supported because the maximum bit length of p
(specified as L) is 3072 for DSA. For consistent cryptographic
strength, SHA-384 would be used with DSA where L is 7680, and SHA-512
would be used with DSA where L is 15360.
The algorithm identifier for DSA with SHA-224 signature values is:
id-dsa-with-sha224 OBJECT IDENTIFIER ::= {
joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)
csor(3) algorithms(4) id-dsa-with-sha2(3) 1 }
The algorithm identifier for DSA with SHA-256 signature values is:
id-dsa-with-sha256 OBJECT IDENTIFIER ::= {
joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)
csor(3) algorithms(4) id-dsa-with-sha2(3) 2 }
<span class="grey">Turner Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5754">RFC 5754</a> Using SHA2 Algorithms with CMS January 2010</span>
When either of these algorithm identifiers is used, the
AlgorithmIdentifier parameters field MUST be absent.
The SMIMECapabilities attribute value indicates support for one of
the DSA signature algorithms in a SEQUENCE with the capabilityID
field containing the object identifier id-dsa-with-sha* (where * is
224 or 256) with absent parameters. The DER encodings for these
SMIMECapability values are:
id-dsa-with-sha224: 30 0b 06 09 60 86 48 01 65 03 04 03 01
id-dsa-with-sha256: 30 0b 06 09 60 86 48 01 65 03 04 03 02
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. RSA</span>
<a href="./rfc3370#section-3.2">[RFC3370], Section 3.2</a>, specifies the conventions for RSA with SHA-1
(RSASSA-PKCS1-v1_5) public key algorithm identifiers, parameters,
public keys, and signature values. RSA with SHA2 algorithms uses the
same conventions for these public key algorithm identifiers,
parameters, public keys, and signature values. RSA
(RSASSA-PKCS1-v1_5) [<a href="./rfc3447" title=""Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1"">RFC3447</a>] MAY be used with SHA-224, SHA-256,
SHA-384, or SHA-512. The object identifiers are taken from
[<a href="./rfc4055" title=""Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC4055</a>].
The object identifier for RSA with SHA-224 signature values is:
sha224WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 14 }
The object identifier for RSA with SHA-256 signature values is:
sha256WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 11 }
The object identifier for RSA with SHA-384 signature values is:
sha384WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 12 }
The object identifier for RSA with SHA-512 signature values is:
sha512WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 13 }
<span class="grey">Turner Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc5754">RFC 5754</a> Using SHA2 Algorithms with CMS January 2010</span>
When any of these four object identifiers appears within an
AlgorithmIdentifier, the parameters MUST be NULL. Implementations
MUST accept the parameters being absent as well as present.
The SMIMECapabilities attribute value indicates support for one of
the DSA signature algorithms in a SEQUENCE with the capabilityID
field containing the object identifier sha*WithRSAEncryption (where *
is 224, 256, 384, or 512) with NULL parameters. The DER encodings
for these SMIMECapability values are:
sha224WithRSAEncryption: 30 0d 06 09 2a 86 48 86 f7 0d 01 01 0e
05 00
sha256WithRSAEncryption: 30 0d 06 09 2a 86 48 86 f7 0d 01 01 0b
05 00
sha384WithRSAEncryption: 30 0d 06 09 2a 86 48 86 f7 0d 01 01 Oc
05 00
sha512WithRSAEncryption: 30 0d 06 09 2a 86 48 86 f7 0d 01 01 0d
05 00
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. ECDSA</span>
<a href="./rfc5753#section-2.1">[RFC5753], Section 2.1</a>, specifies the conventions for ECDSA with
SHA-* (where * is 1, 224, 256, 384, or 512) public key algorithm
identifiers, parameters, public keys, and signature values. The
object identifiers, which are included below for convenience, are
taken from [<a href="./rfc5758" title=""Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSA"">RFC5758</a>].
The algorithm identifier for ECDSA with SHA-224 signature values is:
ecdsa-with-SHA224 OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) ansi-X9-62(10045) signatures(4) ecdsa-with-SHA2(3) 1 }
The algorithm identifier for ECDSA with SHA-256 signature values is:
ecdsa-with-SHA256 OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840)ansi-X9-62(10045) signatures(4) ecdsa-with-SHA2(3) 2 }
The algorithm identifier for ECDSA with SHA-384 signature values is:
ecdsa-with-SHA384 OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) ansi-X9-62(10045) signatures(4) ecdsa-with-SHA2(3) 3 }
<span class="grey">Turner Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc5754">RFC 5754</a> Using SHA2 Algorithms with CMS January 2010</span>
The algorithm identifier for ECDSA with SHA-512 signature values is:
ecdsa-with-SHA512 OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) ansi-X9-62(10045) signatures(4) ecdsa-with-SHA2(3) 4 }
When any of these four object identifiers appears within an
AlgorithmIdentifier, the parameters field MUST be absent. That is,
the AlgorithmIdentifier SHALL be a SEQUENCE of one component: the OID
ecdsa-with-SHA224, ecdsa-with-SHA256, ecdsa-with-SHA384, or ecdsa-
with-SHA512.
The SMIMECapabilities attribute value indicates support for one of
the ECDSA signature algorithms in a SEQUENCE with the capabilityID
field containing the object identifier ecdsa-with-SHA1* (where * is
224, 256, 384, or 512) with absent parameters. The DER encodings for
these SMIMECapability values are:
ecdsa-with-SHA224: 30 0a 06 08 2a 86 48 ce 3d 04 03 01
ecdsa-with-SHA256: 30 0a 06 08 2a 86 48 ce 3d 04 03 02
ecdsa-with-SHA384: 30 0a 06 08 2a 86 48 ce 3d 04 03 03
ecdsa-with-SHA512: 30 0a 06 08 2a 86 48 ce 3d 04 03 04
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
The security considerations in [<a href="./rfc3370" title=""Cryptographic Message Syntax (CMS) Algorithms"">RFC3370</a>], [<a href="./rfc3874" title=""A 224-bit One-way Hash Function: SHA-224"">RFC3874</a>], [<a href="./rfc4055" title=""Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC4055</a>],
[<a href="./rfc5753" title=""Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)"">RFC5753</a>], and [<a href="./rfc5758" title=""Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSA"">RFC5758</a>] apply. No new security considerations are
introduced as a result of this specification.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Normative References</span>
[<a id="ref-DSS">DSS</a>] National Institute of Standards and Technology (NIST),
FIPS Publication 186-3: Digital Signature Standard, June
2009.
[<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-RFC3370">RFC3370</a>] Housley, R., "Cryptographic Message Syntax (CMS)
Algorithms", <a href="./rfc3370">RFC 3370</a>, August 2002.
[<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">Turner Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc5754">RFC 5754</a> Using SHA2 Algorithms with CMS January 2010</span>
[<a id="ref-RFC3874">RFC3874</a>] Housley, R., "A 224-bit One-way Hash Function: SHA-224",
<a href="./rfc3874">RFC 3874</a>, September 2004.
[<a id="ref-RFC4055">RFC4055</a>] Schaad, J., Kaliski, B., and R. Housley, "Additional
Algorithms and Identifiers for RSA Cryptography for use
in the Internet X.509 Public Key Infrastructure
Certificate and Certificate Revocation List (CRL)
Profile", <a href="./rfc4055">RFC 4055</a>, June 2005.
[<a id="ref-RFC5652">RFC5652</a>] Housley, R., "Cryptographic Message Syntax (CMS)", <a href="./rfc5652">RFC</a>
<a href="./rfc5652">5652</a>, September 2009.
[<a id="ref-RFC5751">RFC5751</a>] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet
Mail Extensions (S/MIME) Version 3.2 Message
Specification", <a href="./rfc5751">RFC 5751</a>, January 2010.
[<a id="ref-RFC5753">RFC5753</a>] Turner, S. and D. Brown, "Use of Elliptic Curve
Cryptography (ECC) Algorithms in Cryptographic Message
Syntax (CMS)", <a href="./rfc5753">RFC 5753</a>, January 2010.
[<a id="ref-RFC5758">RFC5758</a>] Dang, Q., Santesson, S., Moriarty, K., Brown, D., and T.
Polk, "Internet X.509 Public Key Infrastructure:
Additional Algorithms and Identifiers for DSA and ECDSA",
<a href="./rfc5758">RFC 5758</a>, January 2010.
[<a id="ref-SHS">SHS</a>] National Institute of Standards and Technology (NIST),
FIPS Publication 180-3: Secure Hash Standard, October
2008.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Informative References</span>
[<a id="ref-RFC4231">RFC4231</a>] Nystrom, M., "Identifiers and Test Vectors for HMAC-
SHA-224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512",
<a href="./rfc4231">RFC 4231</a>, December 2005.
[<a id="ref-RFC4634">RFC4634</a>] Eastlake 3rd, D. and T. Hansen, "US Secure Hash
Algorithms (SHA and HMAC-SHA)", <a href="./rfc4634">RFC 4634</a>, July 2006.
Author's Address
Sean Turner
IECA, Inc.
3057 Nutley Street, Suite 106
Fairfax, VA 22031
USA
EMail: turners@ieca.com
Turner Standards Track [Page 10]
</pre>
|
