Old issues remaining in draft-ietf-smime-examples-06.txt

"Magnus Svensson" <[email protected]> Mon, 5 Mar 2001 15:18:33 +0100
Newsgroups gmane.ietf.smime-examples
Message-ID <[email protected]>
I checked the draft-ietf-smime-examples-06.txt to verify that the issues I
reported earlier had been fixed. Unfortunately some of them remains and I
therefore list them here again:

1. Bob's private RSA key is incorrect. It is actually identical to Carl's
private RSA key. This error is present in both the draft text (the ASN.1
text) and the binary file. As Alexei Shamov pointed out for some time ago,
the correct key can be retrieved by downloading SFL and using the path
<INSTALL_DIR>\smimeR1.8\test\CMS_MSExamples2.d\FirstSet.d\certs.d\private.d\
BobPrivRSAEncrypt.pri. This is surely not a preferred solution, so I suggest
that this issue really is fixed for the next draft. Finding this error is
most probably a frustrating and timeconsuming effort if you are not aware of
it's presence.

2. nextUpdate field is missing in all CRLs. I mentioned this problem in a
previous mail but the problem is still present. The nextUpdate field is
required to be present, see RFC 2459 section 5.1.2.5.

3. In the description of example 6.2 the draft text states: "Does not have a
OriginatorInfo, and has unprotected attributes.". Since the example does not
have unprotected attributes the draft text should state "Does not have an
OriginatorInfo or unprotected attributes.".

4. Example 6.1. Listed below the ASN.1 text are additional information
regarding the keys used in the example. This listing contains two CEKs. The
CEK with the hex-sequence beginning with "CD4F7C8373..." is the correct one.
The other one needs to be removed.

5. Alice's and Bob's RSA certificates distributed separately are different
from those present within the messages. The first has a signature algorithm
OID of sha-1WithRSAEncryption (1 3 14 3 2 29) and the latter
sha1withRSAEncryption (1 2 840 113549 1 1 5). The draft text incorrectly
declares the algorithm OID for the separate certificates to be
sha1withRSAEncryption (1 2 840 113549 1 1 5). I suppose only the PKCS#1 (and
PKIX) variant should be used. The PKCS#1 OID is sha1withRSAEncryption (1 2
840 113549 1 1 5).

Regards,
Magnus