[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Corrected Signed Receipt Sample for Examples-07 I-D



All,

On 6 April 2001, we provided a new 11.1 sample message requesting a signed
receipt, but we neglected to provide the corresponding 11.2 sample signed
receipt.  A new 11.2 sample signed receipt is attached that we generated
based on the 6 April 11.1 sample message.

Thanks to Ronald 'Life is hard, and then you die' for catching our omission.

===========================================
John Pawling, John.Pawling@xxxxxxxxxxxxxxxx
Getronics Government Solutions, LLC
===========================================

 <<11.2.signedReceipt.bin>> 
 
>  -----Original Message-----
> From: 	Pawling, John  
> Sent:	Friday, April 06, 2001 3:19 PM
> To:	SMIME Examples List (E-mail)
> Cc:	Colestock, Robert
> Subject:	Corrected Samples for Examples-07 I-D
> 
> All,
> 
> In reply to several e-mail messages, Getronics Government Solutions has
> used the S/MIME Freeware Library (SFL) to generate new corrected versions
> (see below) of the following sample messages (attached).  We propose that
> these messages should be included in the next release (-07) of the
> "Examples of S/MIME Messages" Internet-Draft.  We still need to generate
> corrected samples for sections 5.8, 5.9 and 6.8.  We need to enhance our
> MIME capabilities before generating those samples.  Thanks to all who
> provided feedback!!  We look forward to further feedback.
> 
> 1) We corrected the SFL to use the id-dsa-with-sha1 OID for DSA signatures
> as specified in RFC 2630, Section 12.2.1.  New samples including the
> corrected OID are provided for sections 5.1, 5.3, 5.4, 5.6, 5.7, 5.10,
> 11.1, 11.3, 11.4, 11.5, 11.6.  Note: We generated new samples for all
> DSA-signed messages including those submitted by Jim Schaad, because we
> (and others) could not verify the signature of Jim's DSA-signed messages.
> 
> 2) We corrected the SFL to properly implement the following requirement as
> specified in RFC 2630, Section 12.3.1: "For key agreement of RC2
> key-encryption keys, 128 bits must be generated as input to the key
> expansion process used to compute the RC2 effective key [RC2]."  New
> corrected samples are provided for sections 6.3, 6.7, 6.9, 6.10.  The
> sample for section 6.7 also included the correct KEKRecipientInfo version
> value (4).  
> 
> 3) We were unable to use the BobPrivRSAEncrypt private key included in the
> Examples-06 document.  We are providing a new BobPrivRSAEncrypt private
> key that can be used to decrypt the sample 6.2 message included in the
> Examples-06 document.  We are also providing a new BobRSASignByCarl
> certificate.  
> 
> Paul: Recommend changing all occurrences of "DH-DSS" to "DSA" to be
> consistent with RFC 2630.
> 
> Thank you again for the feedback!!
> 
> ===========================================
> John Pawling, John.Pawling@xxxxxxxxxxxxxxxx
> Getronics Government Solutions, LLC
> ===========================================
> 
> 

Attachment: 11.2.signedReceipt.bin
Description: Binary data