RFC Errata
Found 2 records.
Status: Verified (1)
RFC 4134, "Examples of S/MIME Messages", July 2005
Source of RFC: smime (sec)
Errata ID: 1716
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Maxim Masiutin
Date Reported: 2009-03-15
Verifier Name: Sean Turner
Date Verified: 2010-07-20
Section 4.8 & 4.9 says:
In 4.8, From: aliceDss@examples.com Subject: Example 4.8 Message-Id: <020906002550300.249@examples.com> In 4.9, From: aliceDss@examples.com Subject: Example 4.9 Message-Id: <021031164540300.304@examples.com>
It should say:
In 4.8, From: AliceDSS@example.com Subject: Example 4.8 Message-Id: <020906002550300.249@example.com> In 4.9, From: AliceDSS@example.com Subject: Example 4.9 Message-Id: <021031164540300.304@example.com>
Notes:
"From" line of the RFC-822 message is aliceDss@examples.com, while the certificate’s SubjectAlternativeName contains Rfc822Name = AliceDSS@example.com
So the two emails are different in the host part:
aliceDss@examples.com
AliceDSS@example.com
The wrong email (aliceDss@examples.com) is given in both cleartext examples and encoded examples.
Additionally, the Message-Id should also be from example.com not from examples.com.
Status: Reported (1)
RFC 4134, "Examples of S/MIME Messages", July 2005
Source of RFC: smime (sec)
Errata ID: 7125
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Dmitry Baryshkov
Date Reported: 2022-09-11
Section B says:
***5.2.bin*** |* Example 5.2.bin |>5.2.bin |MIIBZQYJKoZIhvcNAQcDoIIBVjCCAVICAQIxggEAMIG9AgEAMCYwEjEQMA4GA1UEAxMHQ2 |FybFJTQQIQRjRrx4AAVrwR024uzV1x0DANBgkqhkiG9w0BAQEFAASBgJQmQojGi7Z4IP+C |VypBmNFoCDoEp87khtgyff2N4SmqD3RxPx+8hbLQt9i3YcMwcap+aiOkyqjMalT03VUC0X |BOGv+HYI3HBZm/aFzxoq+YOXAWs5xlGerZwTOc9j6AYlK4qXvnztR5SQ8TBjlzytm4V7zg |+TGrnGVNQBNw47Ewoj4CAQQwDQQLTWFpbExpc3RSQzIwEAYLKoZIhvcNAQkQAwcCAToEGH |cUr5MSJ/g9HnJVHsQ6X56VcwYb+OfojTBJBgkqhkiG9w0BBwEwGgYIKoZIhvcNAwIwDgIC |AKAECJwE0hkuKlWhgCBeKNXhojuej3org9Lt7n+wWxOhnky5V50vSpoYRfRRyw== |<5.2.bin
It should say:
***5.2.bin*** |* Example 5.2.bin |>5.2.bin |MIIBIwYJKoZIhvcNAQcDoIIBFDCCARACAQAxgcAwgb0CAQAwJjASMRAwDgYDVQQDEwdDYX |JsUlNBAhBGNGvHgABWvBHTbi7NXXHQMA0GCSqGSIb3DQEBAQUABIGAhUK+4wsu5Q8JqiTK |3trB0wm4Jysly9Vx+8mc2/CybqCKXxydSu2YnRU5JgEaLmvwRDmJNzxvx0phCwsnd6r51J |ek0iE/wj8g1NwQ6dY/ANucgkfWfpb/Em6HhKC67YEPVm2mHeurw7ehufhfi8wbSuUUNgZh |0MdkX2lnkalQ7tgwSAYJKoZIhvcNAQcBMBkGCCqGSIb3DQMCMA0CAToECOhwgeLvxRVXgC |AGUwp7jVwWDczVdtaLWdZFjBoaDOYe895DVgCbQIw4XQ== |<5.2.bin
Notes:
The base64 encoding in the Appending B doesn't correspond to the data in the section 5.2. Provided base64 was generated using data in the section 5.2 instead.