RE: Status of the examples draft

["Jacoby, Jeffrey" <jjacoby@xxxxxxxxxxxxxxx>]

FYI,

Our current status...

We have had success with the following messages
from draft-ietf-smime-examples-11.txt.  There is
one additional success, and one failure, since -09 
(or was -10 the last time I responded?):

        4.1.bin
        4.2.bin
        5.1.bin    <- new success since -09
        5.2.bin
        5.3.bin
        5.4.bin
        5.5.bin
        5.10.bin
        5.11.bin
        6.2.bin
        6.3.bin
        7.0.bin
        8.1.bin
                   <-- new failure w/ 11.1.bin (we now don't 
                       support dsa (1 2 840 10040 4 1) as a 
                       signature OID)
        11.3.bin
        11.4.bin
        11.5.bin
        11.6.bin


A few points:

 - Paul, looking back at my previous status note, we had
   never claimed success with 11.2.bin (sorry, I should 
   known that when we spoke)

 - Don't take too much comfort in our success with the other
   examples 11.*.bin.  While the code can parse and verify the 
   signatures, it doesn't do anything else in terms of enhanced 
   security semantics.

 - The same comments Blake made (below) for his results, where we 
   both had successes in common, apply to ours as well.


Jeff
-- 
Jeff Jacoby, Principal Development Engineer  
RSA Security Inc., Developer Solutions
2955 Campus Drive, Suite 400
San Mateo, CA 94403

phone: (650) 295-7569
fax:   (650) 358-2530
email: jjacoby@xxxxxxxxxxxxxxx        






>  > -----Original Message-----
>  > From: owner-ietf-smime@xxxxxxxxxxxx
>  > [mailto:owner-ietf-smime@xxxxxxxxxxxx] On Behalf Of Paul 
>  Hoffman / IMC
>  > Sent: Wednesday, July 02, 2003 8:44 AM
>  > To: ietf-smime-examples@xxxxxxx; ietf-smime@xxxxxxx
>  > Subject: Status of the examples draft
>  > 
>  > Hi again. The -11 draft has the following changes:
>  
>  The comments that I posted regarding the -10 draft stand for 
>  the -11 draft, and I have included them below for completeness.
>  
>  The only thing that I've had trouble with so far is 5.6.bin 
>  appears to have changed the order of the SignerInfos.  I 
>  don't believe that this change is relevant, so I don't think 
>  there needs to be any modification of the draft.
>  
>  The files I have worked with:
>  
>  5.1.bin -- Identified as a CMS SignedData with signatures 
>  and content, checked certificates were present, matched 
>  content to ExContent.bin, verified one signer
>  
>  5.2.bin -- Checked certificates were present, matched 
>  content to ExContent.bin, verified one signer
>  
>  5.3.bin -- Identified as a CMS SignedData with signatures 
>  and no content, checked certificates were present, verified 
>  one signer against external content in ExContent.bin
>  
>  5.4.bin -- Extracted signing time attribute, checked 
>  certificates were present, checked CRLs were present, 
>  matched content to ExContent.bin, verified one signer
>  
>  5.5.bin -- Checked certificates were present, matched 
>  content to ExContent.bin, verified one signer
>  
>  5.6.bin -- Checked certificates were present, matched 
>  content to ExContent.bin, verified two signers
>  
>  5.7.bin -- Checked certificates were present, matched 
>  content to ExContent.bin, verified one signer
>  
>  5.8.eml -- Parsed content with MIME parser, matched 
>  extracted text content from text part to ExContent.bin, 
>  checked certificates were present, verified one signer 
>  against first part of message, identified as a CMS 
>  SignedData with signatures and no content
>  
>  5.9.eml -- Parsed content with MIME parser, matched 
>  extracted text content from text part to ExContent.bin, 
>  checked certificates were present, verified one signer, 
>  identified as a CMS SignedData with signatures and content
>  
>  5.10.bin -- Matched content to ExContent.bin, verified one signer
>  
>  5.11.bin -- Identified as a CMS SignedData with no 
>  signatures and no content, checked certificates were present
>  
>  6.2.bin -- Decrypted message, matched content to 
>  ExContent.bin, identified as a CMS EnvelopedData
>  
>  6.3.bin -- Decrypted message, matched content to ExContent.bin
>  
>  7.0.bin -- Verified hash, matched content to ExContent.bin
>  
>  8.1.bin -- Decrypted data with given key, matched content to 
>  ExContent.bin
>  
>  
>  I also worked with the following certificates and private keys:
>  
>  AliceDSSSignByCarlNoInherit.cer
>  AlicePrivRSASign.pri
>  AliceRSASignByCarl.cer
>  BobPrivRSAEncrypt.pri
>  BobRSASignByCarl.cer
>  CarlDSSCRLForAll.crl
>  CarlDSSSelf.cer
>  CarlPrivDSSSign.pri
>  CarlPrivRSASign.pri
>  CarlRSASelf.cer
>  DianeDHEncryptByCarl.cer
>  DianeDSSSignByCarlInherit.cer
>  DianePrivRSASignEncrypt.pri
>  DianeRSASignByCarl.cer
>  EricaDHEncryptByCarl.cer
>  
>  Blake
>