RE: Comments on new files

["Jim Schaad" <jimsch@xxxxxxxxxx>]

You are correct, I had assumed that the two .pri files where different
and the problem was with the certificate.  This is incorrect.

However I am surprised that 6.2.ber does not decrypt.  It appears to
decrypt correctly in my system.

jim

> -----Original Message-----
> From: owner-ietf-smime-examples@xxxxxxxxxxxx 
> [mailto:owner-ietf-smime-examples@xxxxxxxxxxxx] On Behalf Of 
> Blake Ramsdell
> Sent: Thursday, March 07, 2002 6:19 PM
> To: jimsch@xxxxxxxxxx
> Cc: John.Pawling@xxxxxxxxxxxxxxxx; IETF-SMIME-Examples; Paul Hoffman
> Subject: Comments on new files
> 
> 
> 
> Jim,
> 
> I have some comments on your last post.
> 
> 1. I noticed that the public key in BobRSASignByCarl.cer 
> changed to be what
> appears to be Carl's public key.  I don't mind this, it's just that I
> thought that each one would have their own keypair.
> 
> 2. From what I can tell, 6.2.ber is still DER, not BER.  Well, I guess
> technically it's BER, but using definite lengths for everything ;).  I
> presume that the intent was to use indefinite lengths for constructed
> elements, which this example does not appear to do.
> 
> 3. 6.2.ber still does not decrypt in my environment with
> BobPrivRSAEncrypt.pri (the unwrapped key does not appear to 
> have the correct
> block format, leading me to believe that it is the wrong 
> private key.  I am
> in the process of pulling all of this stuff apart to 
> determine if it's a bug
> in my code or in the data.
> 
> Blake
> --
> Blake Ramsdell
> Brute Squad Labs http://www.brutesquadlabs.com
>