SHA1-WITH-DSA SignedData

"Pawling, John" <[email protected]> Thu, 26 Aug 1999 17:37:31 -0400
Newsgroups gmane.ietf.smime-examples
Message-ID <33BD629222C0D211B6DB0060085ACF31360AE8@WFHQEX03>
All,

Attached is a signedData object (MIME wrapped (.eml) and just ASN.1 encoded
(.out)) produced using the S/MIME Freeware Library.  The signedData was
hashed using SHA-1 and signed using DSA. It includes a variety of signed
attributes.  It includes the complete cert path for the signer.  The cert
path includes the self-signed root (i.e. PAA) certificate which contains the
DSA parameters.  As stated in RFC 2459, if the DSA parameters are absent
from a subject's cert, then the DSA parameters of the issuer's cert are used
in conjunction with the subject's public DSA key to verify signatures signed
using the subject's private DSA key (i.e. the subject inherits the
parameters of the issuer).  You can use the signer's DSA public key from the
signer's certificate in conjunction with the DSA parameters from the PAA
cert to verify the signature of the attached signedData object.  We don't
normally include the self-signed root in signedData objects that we produce,
but it is included here for convenience of the testing.  An extra cert (Key
Exchange Algorithm) is also included in the signedData.  More test messages
will follow.

============================================
John Pawling, Director - Systems Engineering
J.G. Van Dyke & Associates, Inc.,
a Wang Government Services Company
[email protected]
============================================
SignedData1.eml (application/octet-stream, 7.8 KB) - not displayed
SignedData1.out (application/octet-stream, 5.4 KB) - not displayed