CARVIEW |
Select Language
HTTP/2 200
date: Fri, 01 Aug 2025 11:03:30 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=c0ne92fd9q6mf3in0ff71cqcff; path=/
set-cookie: __cf_bm=Wk8oBImjP9MYhBb8FFPSMiSP45lRwJKcZH6hnmNJfbs-1754046210-1.0.1.1-5hFjIWE_Qbc8sJqpSyD_TYY9awv81T3IShxjexPl13Ku2cdnfgKvwomV8JdZLT_hmUhy7rMPbwpwC47s6ldX4FclWkUvUe91qUfQTe3rtxM; path=/; expires=Fri, 01-Aug-25 11:33:30 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 9684d967de4d6cd6-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
RFC 5652, "Cryptographic Message Syntax (CMS)", September 2009
Note: This RFC has been updated by RFC 8933, RFC 9629
Source of RFC: smime (sec)
Errata ID: 5331
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Thomas Stimm
Date Reported: 2018-04-23
Rejected by: Eric Rescorla
Date Rejected: 2018-04-27
Section 6.1 and 8 says:
EncryptedData ::= SEQUENCE { version CMSVersion, encryptedContentInfo EncryptedContentInfo, unprotectedAttrs [1] IMPLICIT UnprotectedAttributes OPTIONAL } EncryptedContentInfo ::= SEQUENCE { contentType ContentType, contentEncryptionAlgorithm ContentEncryptionAlgorithmIdentifier, encryptedContent [0] IMPLICIT EncryptedContent OPTIONAL }
It should say:
EncryptedData ::= SEQUENCE { version CMSVersion, encryptedContentInfo EncryptedContentInfo, encryptedContent [0] IMPLICIT EncryptedContent OPTIONAL, unprotectedAttrs [1] IMPLICIT UnprotectedAttributes OPTIONAL } EncryptedContentInfo ::= SEQUENCE { contentType ContentType, contentEncryptionAlgorithm ContentEncryptionAlgorithmIdentifier }
Notes:
- Wrong enumeration of UnprotectedAttributes OPTIONAL [1] instead of [0].
- ‘UnprotectedAttributes OPTIONAL’ makes only sense, if ‘EncryptedContent OPTIONAL’ is available.
- It seems that OpenSSL and wolfSSL are using the suggested wrapping and are not following the RFC, here.
--VERIFIER NOTES--
Misunderstanding of the specification
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us