|
| |
| | [No title] |
 | | For each signer, a message digest, or hash value, is computed on the content with a signer-specific message-digest algorithm. | | | For signed-data, the message digest is computed using the signer's message digest algorithm. | | | For authenticated-data, the message digest is computed using the originator's message digest algorithm. |
|
http://www.ietf.org/rfc/rfc2630.txt
(12011 words)
|
|
| |
| | Griffin Consulting X9.96 |
| | The syntax is optimized for the common case where the same key management algorithm and parameters are used for all of the recipients; 3) Data integrity and origin authentication of data, using any approved X9 digital signature or message authentication algorithm. | | | This syntax specifies enhancements of the cryptographic message syntax defined in the IETF SMIME CMS in RFC 2630, Reference [19]. | | | An optimized syntax allows for the common case where only a single entity signs or authenticates a message. |
|
http://asn-1.com/x996.htm
(1070 words)
|
|
| |
| | RFC 3370 - Cryptographic Message Syntax (CMS) Algorithms. R. Housley. |
| | RFC 2437 specifies the use of the RSA signature algorithm with the SHA-1 and MD5 message digest algorithms. | | | Abstract This document describes the conventions for using several cryptographic algorithms with the Cryptographic Message Syntax (CMS). | | | RFC 3370 CMS Algorithms August 2002 The rsaEncryption algorithm identifier is used to identify RSA (PKCS #1 v1.5) signature values regardless of the message digest algorithm employed. |
|
http://rfc.sunsite.dk/rfc/rfc3370.html
(4783 words)
|
|
| |
| | The Internet Report |
| | Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS) (RFC 4010) (0 bytes) | | | use of additional cryptographic algorithms will be developed. | | | Use of the RSASSA-PSS Signature Algorithm in Cryptographic Message Syntax (CMS) (RFC 4056) (0 bytes) |
|
http://ietfreport.isoc.org/ids-wg-smime.html
(1003 words)
|
|
| |
| | RSA Security - PKCS #7: Cryptographic Message Syntax Standard |
| | This standard describes general syntax for data that may have cryptography applied to it, such as digital signatures and digital envelopes. | | | In support of the SET protocol for secure electronic transactions, RSA Laboratories has produced a bulletin detailing changes to be made to PKCS #7 version 1.5 to update it to version 1.6 (which has not yet been published). | | | PKCS #7 Cryptographic Message Syntax Standard: ASCII, MS-Word, PostScript and Gzip PostScript |
|
http://www.rsasecurity.com/rsalabs/node.asp?id=2129
(132 words)
|
|
| |
| | [xcbf] XCBF Cryptographic Message Syntax (CMS) |
| | I also hope to initiate discussion on which cryptographic algorithms we will support. | | | -- any X9-approved MAC or HMAC algorithm -- } MessageAuthenticationCode ::= OCTET STRING -- Cryptographic algorithm identification -- ALGORITHM ::= CLASS { andid OBJECT IDENTIFIER UNIQUE, andType OPTIONAL } WITH SYNTAX { OID andid [PARMS andType] } AlgorithmIdentifier { ALGORITHM:IOSet } ::= SEQUENCE { algorithm ALGORITHM.andid({IOSet}), parameters ALGORITHM.andType({IOSet}{@algorithm}) OPTIONAL } END -- XCBF-CMS -- | | | I've more to do still, and it has not even been syntax checked yet, but it will give you a better idea of how the biometrics are enhanced using CMS security types in XCBF. |
|
http://www.oasis-open.org/archives/xcbf/200205/msg00017.html
(410 words)
|
|
|
