draft-ietf-smime-gost-07.txt   rfc4490.txt 
S/MIME Working Group Serguei Leontiev, CRYPTO-PRO Network Working Group S. Leontiev, Ed.
Internet Draft Gregory Chudov, CRYPTO-PRO Request for Comments: 4490 G. Chudov, Ed.
Expires July 18, 2006 January 18, 2006 Category: Standards Track CRYPTO-PRO
Intended Category: Standards Track May 2006
Using the GOST 28147-89, GOST R 34.11-94, Using the GOST 28147-89, GOST R 34.11-94,
GOST R 34.10-94 and GOST R 34.10-2001 algorithms with the GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with
Cryptographic Message Syntax (CMS) Cryptographic Message Syntax (CMS)
<draft-ietf-smime-gost-07.txt> Status of This Memo
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 18, 2006. This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document describes the conventions for using cryptographic This document describes the conventions for using the cryptographic
algorithms GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, GOST R algorithms GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and
34.11-94, along with Cryptographic Message Syntax (CMS). The CMS is GOST R 34.11-94 with the Cryptographic Message Syntax (CMS). The CMS
used for digital signature, digest, authentication and encryption of is used for digital signature, digest, authentication, and encryption
arbitrary message contents. of arbitrary message contents.
Table of Contents Table of Contents
1. Introduction..................................................2 1. Introduction ....................................................3
1.2. Terminology..............................................3 1.1. Terminology ................................................3
2. Message Digest Algorithms.....................................3 2. Message Digest Algorithms .......................................3
2.1. Message Digest Algorithm GOST R 34.11-94.................3 2.1. Message Digest Algorithm GOST R 34.11-94 ...................3
3. Signature Algorithms..........................................4 3. Signature Algorithms ............................................4
3.1. Signature Algorithm GOST R 34.10-94......................4 3.1. Signature Algorithm GOST R 34.10-94 ........................4
3.2. Signature Algorithm GOST R 34.10-2001....................4 3.2. Signature Algorithm GOST R 34.10-2001 ......................5
4. Key Management Algorithms.....................................5 4. Key Management Algorithms .......................................5
4.1. Key Agreement Algorithms.................................5 4.1. Key Agreement Algorithms ...................................6
4.1.1. Key Agreement Algorithms Based on 4.1.1. Key Agreement Algorithms Based on GOST R
GOST R 34.10-94/2001 Public Keys........................5 34.10-94/2001 Public ................................6
4.2. Key Transport Algorithms.................................7 4.2. Key Transport Algorithms ...................................8
4.2.1. Key Transport Algorithm Based on 4.2.1. Key Transport Algorithm Based on GOST R
GOST R 34.10-94/2001 Public Keys........................8 34.10-94/2001 Public ................................8
5. Content Encryption Algorithms.................................9 5. Content Encryption Algorithms ...................................9
5.1. Key-Encryption Key Algorithm GOST 28147-89...............9 5.1. Content Encryption Algorithm GOST 28147-89 ................10
6. MAC Algorithms................................................9 6. MAC Algorithms .................................................10
6.1. HMAC with GOST R 34.11-94...............................10 6.1. HMAC with GOST R 34.11-94 .................................10
7. Using with S/MIME............................................10 7. Use with S/MIME ................................................11
7.1. Parameter micalg........................................10 7.1. Parameter micalg ..........................................11
7.2. Atribute SMIMECapabilities..............................10 7.2. Attribute SMIMECapabilities ...............................11
8. Security Considerations......................................11 8. Security Considerations ........................................12
9. Appendix Examples............................................11 9. Examples .......................................................12
9.1. Signed message..........................................12 9.1. Signed Message ............................................12
9.2. Enveloped message using Key Agreement...................13 9.2. Enveloped Message Using Key Agreement .....................14
9.3. Enveloped message using Key Transport...................16 9.3. Enveloped Message Using Key Transport .....................17
10. Appendix ASN.1 Modules......................................18 10. ASN.1 Modules .................................................19
10.1. GostR3410-EncryptionSyntax.............................18 10.1. GostR3410-EncryptionSyntax ...............................19
10.2. GostR3410-94-SignatureSyntax...........................20 10.2. GostR3410-94-SignatureSyntax .............................21
10.3. GostR3410-2001-SignatureSyntax.........................21 10.3. GostR3410-2001-SignatureSyntax ...........................22
11. Acknowledgments.............................................22 11. Acknowledgements ..............................................23
12. References..................................................22 12. References ....................................................24
12.1. Normative References...................................23 12.1. Normative References .....................................24
12.2. Informative References.................................24 12.2. Informative References ...................................25
Contact Information.............................................24
Full Copyright Statement........................................26
1. Introduction 1. Introduction
The Cryptographic Message Syntax [CMS] is used for digital signature, The Cryptographic Message Syntax [CMS] is used for digital signature,
digest, authentication and encryption of arbitrary message contents. digest, authentication, and encryption of arbitrary message contents.
This companion specification describes the use of cryptographic This companion specification describes the use of cryptographic
algorithms GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001 and GOST algorithms GOST 28147-89 [GOST28147], GOST R 34.10-94 [GOST3431095,
R 34.11-94 in CMS, as proposed by the CRYPTO-PRO Company for "Russian GOSTR341094], GOST R 34.10-2001 [GOST3431004, GOSTR341001], and GOST
Cryptographic Software Compatibility Agreement" community. This R 34.11-94 [GOST3431195, GOSTR341194] in CMS, as proposed by the
document does not describe these cryptographic algorithms; they are CRYPTO-PRO Company for the "Russian Cryptographic Software
defined in corresponding national standards. Compatibility Agreement" community. This document does not describe
these cryptographic algorithms; they are defined in corresponding
national standards.
The CMS values are generated using ASN.1 [X.208-88], using BER- The CMS values are generated using ASN.1 [X.208-88], using BER
encoding [X.209-88]. This document specifies the algorithm encoding [X.209-88]. This document specifies the algorithm
identifiers for each algorithm, including ASN.1 for object identifiers for each algorithm, including ASN.1 for object
identifiers and any associated parameters. identifiers and any associated parameters.
The fields in the CMS employed by each algorithm are identified. The fields in the CMS employed by each algorithm are identified.
1.2. Terminology 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Message Digest Algorithms 2. Message Digest Algorithms
This section specifies the conventions for using the digest algorithm This section specifies the conventions for using the digest algorithm
GOST R 34.11-94 employed by CMS. GOST R 34.11-94 employed by CMS.
Digest values are located in the DigestedData digest field and the Digest values are located in the DigestedData digest field and the
Message Digest authenticated attribute. In addition, digest values Message Digest authenticated attribute. In addition, digest values
are input to signature algorithms. are input to signature algorithms.
2.1. Message Digest Algorithm GOST R 34.11-94 2.1. Message Digest Algorithm GOST R 34.11-94
Hash function GOST R 34.11-94 has been developed by "GUBS of Federal The hash function GOST R 34.11-94 has been developed by "GUBS of
Agency Government Communication and Information" and "All-Russian Federal Agency Government Communication and Information" and "All-
Scientific and Research Institute of Standardization". The algorithm Russian Scientific and Research Institute of Standardization". The
GOST R 34.11-94 produces a 256-bit hash value of the arbitrary finite algorithm GOST R 34.11-94 produces a 256-bit hash value of the
bit length input. This document does not contain the full GOST R arbitrary finite bit-length input. This document does not contain
34.11-94 specification, which can be found in [GOSTR3411] in Russian. the full GOST R 34.11-94 specification, which can be found in
[Schneier95] ch. 18.11, p. 454. contains a brief technical [GOSTR341194] in Russian. [Schneier95], ch. 18.11, p. 454, contains
description in English. a brief technical description in English.
The hash algorithm GOST R 34.11-94 has the following identifier: The hash algorithm GOST R 34.11-94 has the following identifier:
id-GostR3411-94 OBJECT IDENTIFIER ::= id-GostR3411-94 OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) ru(643) rans(2) cryptopro(2) { iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
gostr3411(9) } gostr3411(9) }
The AlgorithmIdentifier parameters field MUST be present, and the The AlgorithmIdentifier parameters field MUST be present, and the
parameters field MUST contain NULL. Implementations MAY accept the parameters field MUST contain NULL. Implementations MAY accept the
GOST R 34.11-94 AlgorithmIdentifiers with absent parameters as well GOST R 34.11-94 AlgorithmIdentifiers with absent parameters as well
as NULL parameters. as NULL parameters.
This function is always used with default parameters id- This function is always used with default parameters id-GostR3411-
GostR3411-94-CryptoProParamSet (see section 8.2 of [CPALGS]). 94-CryptoProParamSet (see Section 8.2 of [CPALGS]).
When Message Digest authenticated attribute is present, DigestedData When the Message Digest authenticated attribute is present, the
digest contains a 32-byte digest in little-endian representation: DigestedData digest contains a 32-byte digest in little-endian
representation:
GostR3411-94-Digest ::= OCTET STRING (SIZE (32)) GostR3411-94-Digest ::= OCTET STRING (SIZE (32))
3. Signature Algorithms 3. Signature Algorithms
This section specifies the CMS procedures for GOST R 34.10-94 and This section specifies the CMS procedures for the GOST R 34.10-94 and
GOST R 34.10-2001 signature algorithms. GOST R 34.10-2001 signature algorithms.
Signature algorithm identifiers are located in the SignerInfo Signature algorithm identifiers are located in the SignerInfo
signatureAlgorithm field of SignedData. Also, signature algorithm signatureAlgorithm field of SignedData. Also, signature algorithm
identifiers are located in the SignerInfo signatureAlgorithm field of identifiers are located in the SignerInfo signatureAlgorithm field of
countersignature attributes. countersignature attributes.
Signature values are located in the SignerInfo signature field of Signature values are located in the SignerInfo signature field of
SignedData. Also, signature values are located in the SignerInfo SignedData. Also, signature values are located in the SignerInfo
signature field of countersignature attributes. signature field of countersignature attributes.
3.1. Signature Algorithm GOST R 34.10-94 3.1. Signature Algorithm GOST R 34.10-94
GOST R 34.10-94 has been developed by "GUBS of Federal Agency GOST R 34.10-94 has been developed by "GUBS of Federal Agency
Government Communication and Information" and "All-Russian Scientific Government Communication and Information" and "All-Russian Scientific
and Research Institute of Standardization". This signature algorithm and Research Institute of Standardization". This signature algorithm
MUST be used conjointly with GOST R 34.11-94 message digest MUST be used conjointly with the GOST R 34.11-94 message digest
algorithm. This document does not contain the full GOST R 34.10-94 algorithm. This document does not contain the full GOST R 34.10-94
specification, which is fully described in [GOSTR341094] in Russian, specification, which is fully described in [GOSTR341094] in Russian;
and a brief description in English can be found in [Schneier95] ch. and a brief description in English can be found in [Schneier95], ch.
20.3, p. 495. 20.3, p. 495.
The GOST R 34.10-94 signature algorithm has the following public key The GOST R 34.10-94 signature algorithm has the following public key
algorithm identifier: algorithm identifier:
id-GostR3410-94-signature OBJECT IDENTIFIER ::= id-GostR3410-94 id-GostR3410-94-signature OBJECT IDENTIFIER ::= id-GostR3410-94
id-GostR3410-94 is defined in Section 2.3.1 of [CPPK]. id-GostR3410-94 is defined in Section 2.3.1 of [CPPK].
Signature algorithm GOST R 34.10-94 generates a digital signature in The signature algorithm GOST R 34.10-94 generates a digital signature
the form of a binary 512-bit vector (<r'>256||<s>256). in the form of two 256-bit numbers, r' and s. Its octet string
signatureValue contains its little endian representation. representation consists of 64 octets, where the first 32 octets
contain the big-endian representation of s and the second 32 octets
contain the big-endian representation of r'.
GostR3410-94-Signature ::= OCTET STRING (SIZE (64)) GostR3410-94-Signature ::= OCTET STRING (SIZE (64))
3.2. Signature Algorithm GOST R 34.10-2001 3.2. Signature Algorithm GOST R 34.10-2001
GOST R 34.10-2001 has been developed by "GUBS of Federal Agency GOST R 34.10-2001 has been developed by "GUBS of Federal Agency
Government Communication and Information" and "All-Russian Scientific Government Communication and Information" and "All-Russian Scientific
and Research Institute of Standardization". This signature algorithm and Research Institute of Standardization". This signature algorithm
MUST be used conjointly with GOST R 34.11-94. This document does not MUST be used conjointly with GOST R 34.11-94. This document does not
contain the full GOST R 34.10-2001 specification, which is fully contain the full GOST R 34.10-2001 specification, which is fully
described in [GOSTR341001]. described in [GOSTR341001].
The signature algorithm GOST R 34.10-2001 has the following public The signature algorithm GOST R 34.10-2001 has the following public
key algorithm identifier: key algorithm identifier:
id-GostR3410-2001-signature OBJECT IDENTIFIER ::= id-GostR3410-2001 id-GostR3410-2001-signature OBJECT IDENTIFIER ::= id-GostR3410-2001
id-GostR3410-2001 is defined in Section 2.3.2 of [CPPK]. id-GostR3410-2001 is defined in Section 2.3.2 of [CPPK].
Signature algorithm GOST R 34.10-2001 generates a digital signature The signature algorithm GOST R 34.10-2001 generates a digital
in the form of a binary 512-bit vector (<r'>256||<s>256). signature in the form of two 256-bit numbers, r and s. Its octet
signatureValue contains its little endian representation. string representation consists of 64 octets, where the first 32
octets contain the big-endian representation of s and the second 32
octets contain the big-endian representation of r.
GostR3410-2001-Signature ::= OCTET STRING (SIZE (64)) GostR3410-2001-Signature ::= OCTET STRING (SIZE (64))
4. Key Management Algorithms 4. Key Management Algorithms
This chapter describes the key agreement and key transport This chapter describes the key agreement and key transport
algorithms, based on VKO GOST R 34.10-94 and VKO GOST R 34.10-2001 algorithms, based on the VKO GOST R 34.10-94 and VKO GOST R 34.10-
key derivation algorithms, and the CryptoPro and GOST 28147-89 key 2001 key derivation algorithms, and the CryptoPro and GOST 28147-89
wrap algorithms, described in [CPALGS]. They MUST be used only with key wrap algorithms, described in [CPALGS]. They MUST be used only
content encryption algorithm GOST 28147-89, defined in section 5 of with the content encryption algorithm GOST 28147-89, defined in
this document. Section 5 of this document.
4.1. Key Agreement Algorithms 4.1. Key Agreement Algorithms
This section specifies the conventions employed by CMS This section specifies the conventions employed by CMS
implementations that support key agreement using both VKO GOST R implementations that support key agreement using both the VKO GOST R
34.10-94 and VKO GOST R 34.10-2001 algorithms, described in [CPALGS]. 34.10-94 and VKO GOST R 34.10-2001 algorithms, described in [CPALGS].
Key agreement algorithm identifiers are located in the EnvelopedData Key agreement algorithm identifiers are located in the EnvelopedData
RecipientInfos KeyAgreeRecipientInfo keyEncryptionAlgorithm and RecipientInfos KeyAgreeRecipientInfo keyEncryptionAlgorithm and
AuthenticatedData RecipientInfos KeyAgreeRecipientInfo AuthenticatedData RecipientInfos KeyAgreeRecipientInfo
keyEncryptionAlgorithm fields. keyEncryptionAlgorithm fields.
Wrapped content-encryption keys are located in the EnvelopedData Wrapped content-encryption keys are located in the EnvelopedData
RecipientInfos KeyAgreeRecipientInfo RecipientEncryptedKeys RecipientInfos KeyAgreeRecipientInfo RecipientEncryptedKeys
encryptedKey field. Wrapped message-authentication keys are located encryptedKey field. Wrapped message-authentication keys are located
in the AuthenticatedData RecipientInfos KeyAgreeRecipientInfo in the AuthenticatedData RecipientInfos KeyAgreeRecipientInfo
RecipientEncryptedKeys encryptedKey field. RecipientEncryptedKeys encryptedKey field.
4.1.1. Key Agreement Algorithms Based on GOST R 34.10-94/2001 Public 4.1.1. Key Agreement Algorithms Based on GOST R 34.10-94/2001 Public
Keys Keys
The EnvelopedData RecipientInfos KeyAgreeRecipientInfo field is used The EnvelopedData RecipientInfos KeyAgreeRecipientInfo field is used
as follows: as follows:
version MUST be 3. The version MUST be 3.
originator MUST be the originatorKey alternative. The The originator MUST be the originatorKey alternative. The
originatorKey algorithm field MUST contain the object identifier originatorKey algorithm field MUST contain the object identifier
id-GostR3410-94 or id-GostR3410-2001 and corresponding parameters id-GostR3410-94 or id-GostR3410-2001 and corresponding parameters
(defined in sections 2.3.1, 2.3.2 of [CPPK]). (defined in Sections 2.3.1, 2.3.2 of [CPPK]).
The originatorKey publicKey field MUST contain the sender's public The originatorKey publicKey field MUST contain the sender's public
key. key.
keyEncryptionAlgorithm MUST be the id-GostR3410-94-CryptoPro-ESDH keyEncryptionAlgorithm MUST be the id-GostR3410-94-CryptoPro-ESDH
or the id-GostR3410-2001-CryptoPro-ESDH algorithm identifier, or the id-GostR3410-2001-CryptoPro-ESDH algorithm identifier,
depending on the recipient public key algorithm. The algorithm depending on the recipient public key algorithm. The algorithm
identifier parameter field for these algorithms is identifier parameter field for these algorithms is
KeyWrapAlgorithm, and this parameter MUST be present. The KeyWrapAlgorithm, and this parameter MUST be present. The
KeyWrapAlgorithm denotes the algorithm and parameters used to KeyWrapAlgorithm denotes the algorithm and parameters used to
skipping to change at page 6, line 45 skipping to change at page 7, line 18
KeyWrapAlgorithm ::= AlgorithmIdentifier KeyWrapAlgorithm ::= AlgorithmIdentifier
When keyEncryptionAlgorithm is id-GostR3410-94-CryptoPro-ESDH, When keyEncryptionAlgorithm is id-GostR3410-94-CryptoPro-ESDH,
KeyWrapAlgorithm algorithm MUST be the id-Gost28147-89-CryptoPro- KeyWrapAlgorithm algorithm MUST be the id-Gost28147-89-CryptoPro-
KeyWrap algorithm identifier. KeyWrap algorithm identifier.
id-Gost28147-89-CryptoPro-KeyWrap OBJECT IDENTIFIER ::= id-Gost28147-89-CryptoPro-KeyWrap OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) ru(643) rans(2) cryptopro(2) { iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
keyWrap(13) cryptoPro(1) } keyWrap(13) cryptoPro(1) }
The CryptoPro Key Wrap algorithm is described in sections 6.3 and The CryptoPro Key Wrap algorithm is described in Sections 6.3 and
6.4 of [CPALGS]. 6.4 of [CPALGS].
When keyEncryptionAlgorithm is id-GostR3410-2001-CryptoPro-ESDH, When keyEncryptionAlgorithm is id-GostR3410-2001-CryptoPro-ESDH,
KeyWrapAlgorithm algorithm MUST be either the id- KeyWrapAlgorithm algorithm MUST be either the id-Gost28147-89-
Gost28147-89-CryptoPro-KeyWrap or id-Gost28147-89-None-KeyWrap CryptoPro-KeyWrap or id-Gost28147-89-None-KeyWrap algorithm
algorithm identifier. identifier.
id-Gost28147-89-None-KeyWrap OBJECT IDENTIFIER ::= id-Gost28147-89-None-KeyWrap OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) ru(643) rans(2) cryptopro(2) { iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
keyWrap(13) none(0) } keyWrap(13) none(0) }
The GOST 28147-89 Key Wrap algorithm is described in sections 6.1 The GOST 28147-89 Key Wrap algorithm is described in Sections 6.1
and 6.2 of [CPALGS]. and 6.2 of [CPALGS].
KeyWrapAlgorithm algorithm parameters MUST be present. The syntax KeyWrapAlgorithm algorithm parameters MUST be present. The syntax
for KeyWrapAlgorithm algorithm parameters is for KeyWrapAlgorithm algorithm parameters is
Gost28147-89-KeyWrapParameters ::= Gost28147-89-KeyWrapParameters ::=
SEQUENCE { SEQUENCE {
encryptionParamSet Gost28147-89-ParamSet, encryptionParamSet Gost28147-89-ParamSet,
ukm OCTET STRING (SIZE (8)) OPTIONAL ukm OCTET STRING (SIZE (8)) OPTIONAL
} }
Gost28147-89-ParamSet ::= OBJECT IDENTIFIER Gost28147-89-ParamSet ::= OBJECT IDENTIFIER
Gost28147-89-KeyWrapParameters ukm MUST be absent. Gost28147-89-KeyWrapParameters ukm MUST be absent.
KeyAgreeRecipientInfo ukm MUST be present, and contain eight KeyAgreeRecipientInfo ukm MUST be present and contain eight
octets. octets.
encryptedKey MUST encapsulate Gost28147-89-EncryptedKey, where encryptedKey MUST encapsulate Gost28147-89-EncryptedKey, where
maskKey MUST be absent. maskKey MUST be absent.
Gost28147-89-EncryptedKey ::= SEQUENCE { Gost28147-89-EncryptedKey ::= SEQUENCE {
encryptedKey Gost28147-89-Key, encryptedKey Gost28147-89-Key,
maskKey [0] IMPLICIT Gost28147-89-Key maskKey [0] IMPLICIT Gost28147-89-Key
OPTIONAL, OPTIONAL,
macKey Gost28147-89-MAC macKey Gost28147-89-MAC
} }
Using the secret key, corresponding to the originatorKey publicKey, Using the secret key corresponding to the originatorKey publicKey and
and the recipient's public key, the algorithm VKO GOST R 34.10-94 or the recipient's public key, the algorithm VKO GOST R 34.10-94 or VKO
VKO GOST R 34.10-2001 (described in [CPALGS]) is applied to produce GOST R 34.10-2001 (described in [CPALGS]) is applied to produce the
the KEK. KEK.
Then the key wrap algorithm, specified by KeyWrapAlgorithm, is Then the key wrap algorithm, specified by KeyWrapAlgorithm, is
applied to produce CEK_ENC, CEK_MAC, and UKM. applied to produce CEK_ENC, CEK_MAC, and UKM. Gost28147-89-
Gost28147-89-KeyWrapParameters encryptionParamSet is used for all KeyWrapParameters encryptionParamSet is used for all encryption
encryption operations. operations.
The resulting encrypted key (CEK_ENC) is placed in The resulting encrypted key (CEK_ENC) is placed in the Gost28147-89-
Gost28147-89-EncryptedKey encryptedKey field, its mac (CEK_MAC) is EncryptedKey encryptedKey field, its mac (CEK_MAC) is placed in the
placed in Gost28147-89-EncryptedKey macKey field, and UKM is placed Gost28147-89-EncryptedKey macKey field, and UKM is placed in the
in KeyAgreeRecipientInfo ukm field. KeyAgreeRecipientInfo ukm field.
4.2. Key Transport Algorithms 4.2. Key Transport Algorithms
This section specifies the conventions employed by CMS This section specifies the conventions employed by CMS
implementations that support key transport using both VKO GOST R implementations that support key transport using both the VKO GOST R
34.10-94 and VKO GOST R 34.10-2001 algorithms, described in [CPALGS]. 34.10-94 and VKO GOST R 34.10-2001 algorithms, described in [CPALGS].
Key transport algorithm identifiers are located in the EnvelopedData Key transport algorithm identifiers are located in the EnvelopedData
RecipientInfos KeyTransRecipientInfo keyEncryptionAlgorithm field. RecipientInfos KeyTransRecipientInfo keyEncryptionAlgorithm field.
Key transport encrypted content-encryption keys are located in the Key transport encrypted content-encryption keys are located in the
EnvelopedData RecipientInfos KeyTransRecipientInfo encryptedKey EnvelopedData RecipientInfos KeyTransRecipientInfo encryptedKey
field. field.
4.2.1. Key Transport Algorithm Based on GOST R 34.10-94/2001 Public 4.2.1. Key Transport Algorithm Based on GOST R 34.10-94/2001 Public
Keys Keys
The EnvelopedData RecipientInfos KeyTransRecipientInfo field is used The EnvelopedData RecipientInfos KeyTransRecipientInfo field is used
as follows: as follows:
version MUST be 0 or 3. The version MUST be 0 or 3.
keyEncryptionAlgorithm and parameters MUST be identical to the keyEncryptionAlgorithm and parameters MUST be identical to the
recipient public key algorithm and parameters. recipient public key algorithm and parameters.
encryptedKey encapsulates GostR3410-KeyTransport, which consists encryptedKey encapsulates GostR3410-KeyTransport, which consists
of encrypted content-encryption key, it's MAC, GOST 28147-89 of encrypted content-encryption key, its MAC, GOST 28147-89
algorithm parameters used for key encryption, sender's ephemeral algorithm parameters used for key encryption, the sender's
public key, and UKM (UserKeyingMaterial, see [CMS], 10.2.6). ephemeral public key, and UKM (UserKeyingMaterial; see [CMS],
Section 10.2.6).
transportParameters MUST be present. transportParameters MUST be present.
ephemeralPublicKey MUST be present, and its parameters, if ephemeralPublicKey MUST be present and its parameters, if present,
present, MUST be equal to the recipient public key parameters; MUST be equal to the recipient public key parameters;
GostR3410-KeyTransport ::= SEQUENCE { GostR3410-KeyTransport ::= SEQUENCE {
sessionEncryptedKey Gost28147-89-EncryptedKey, sessionEncryptedKey Gost28147-89-EncryptedKey,
transportParameters transportParameters
[0] IMPLICIT GostR3410-TransportParameters OPTIONAL [0] IMPLICIT GostR3410-TransportParameters OPTIONAL
} }
GostR3410-TransportParameters ::= SEQUENCE { GostR3410-TransportParameters ::= SEQUENCE {
encryptionParamSet OBJECT IDENTIFIER, encryptionParamSet OBJECT IDENTIFIER,
ephemeralPublicKey [0] IMPLICIT SubjectPublicKeyInfo OPTIONAL, ephemeralPublicKey [0] IMPLICIT SubjectPublicKeyInfo OPTIONAL,
ukm OCTET STRING ukm OCTET STRING
} }
Using the secret key, corresponding to the Using the secret key corresponding to the GostR3410-
GostR3410-TransportParameters ephemeralPublicKey, and the recipient's TransportParameters ephemeralPublicKey and the recipient's public
public key, the algorithm VKO GOST R 34.10-94 or VKO GOST R key, the algorithm VKO GOST R 34.10-94 or VKO GOST R 34.10-2001
34.10-2001 (described in [CPALGS]) is applied to produce the KEK. (described in [CPALGS]) is applied to produce the KEK.
Then the CryptoPro key wrap algorithm is applied to produce CEK_ENC, Then the CryptoPro key wrap algorithm is applied to produce CEK_ENC,
CEK_MAC, and UKM. GostR3410-TransportParameters encryptionParamSet is CEK_MAC, and UKM. GostR3410-TransportParameters encryptionParamSet
used for all encryption operations. is used for all encryption operations.
The resulting encrypted key (CEK_ENC) is placed in The resulting encrypted key (CEK_ENC) is placed in the Gost28147-89-
Gost28147-89-EncryptedKey encryptedKey field, its mac (CEK_MAC) is EncryptedKey encryptedKey field, its mac (CEK_MAC) is placed in the
placed in Gost28147-89-EncryptedKey macKey field, and UKM is placed Gost28147-89-EncryptedKey macKey field, and UKM is placed in the
in GostR3410-TransportParameters ukm field. GostR3410-TransportParameters ukm field.
5. Content Encryption Algorithms 5. Content Encryption Algorithms
This section specifies the conventions employed by CMS This section specifies the conventions employed by CMS
implementations that support content encryption using GOST 28147-89. implementations that support content encryption using GOST 28147-89.
Content encryption algorithm identifiers are located in the Content encryption algorithm identifiers are located in the
EnvelopedData EncryptedContentInfo contentEncryptionAlgorithm and the EnvelopedData EncryptedContentInfo contentEncryptionAlgorithm and the
EncryptedData EncryptedContentInfo contentEncryptionAlgorithm fields. EncryptedData EncryptedContentInfo contentEncryptionAlgorithm fields.
skipping to change at page 9, line 35 skipping to change at page 10, line 17
field and the EncryptedData EncryptedContentInfo encryptedContent field and the EncryptedData EncryptedContentInfo encryptedContent
field. field.
5.1. Content Encryption Algorithm GOST 28147-89 5.1. Content Encryption Algorithm GOST 28147-89
This section specifies the use of GOST 28147-89 algorithm for data This section specifies the use of GOST 28147-89 algorithm for data
encipherment. encipherment.
GOST 28147-89 is fully described in [GOST28147] (in Russian). GOST 28147-89 is fully described in [GOST28147] (in Russian).
This document specifies the following OID for this algorithm: This document specifies the following object identifier (OID) for
this algorithm:
id-Gost28147-89 OBJECT IDENTIFIER ::= id-Gost28147-89 OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) ru(643) rans(2) cryptopro(2) { iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
gost28147-89(21) } gost28147-89(21) }
Algorithm parameters MUST be present and have the following Algorithm parameters MUST be present and have the following
structure: structure:
Gost28147-89-Parameters ::= Gost28147-89-Parameters ::=
SEQUENCE { SEQUENCE {
iv Gost28147-89-IV, iv Gost28147-89-IV,
encryptionParamSet OBJECT IDENTIFIER encryptionParamSet OBJECT IDENTIFIER
} }
Gost28147-89-IV ::= OCTET STRING (SIZE (8)) Gost28147-89-IV ::= OCTET STRING (SIZE (8))
encryptionParamSet specifies the set of corresponding encryptionParamSet specifies the set of corresponding Gost28147-89-
Gost28147-89-ParamSetParameters (see section 8.1 of [CPALGS]) ParamSetParameters (see Section 8.1 of [CPALGS])
6. MAC Algorithms 6. MAC Algorithms
This section specifies the conventions employed by CMS This section specifies the conventions employed by CMS
implementations that support the message authentication code (MAC) implementations that support the message authentication code (MAC)
based on GOST R 34.11-94. based on GOST R 34.11-94.
MAC algorithm identifiers are located in the AuthenticatedData MAC algorithm identifiers are located in the AuthenticatedData
macAlgorithm field. macAlgorithm field.
MAC values are located in the AuthenticatedData mac field. MAC values are located in the AuthenticatedData mac field.
6.1. HMAC with GOST R 34.11-94 6.1. HMAC with GOST R 34.11-94
HMAC_GOSTR3411 (K,text) function is based on hash function GOST R HMAC_GOSTR3411 (K,text) function is based on hash function GOST R
34.11-94, as defined in section 3 of [CPALGS]. 34.11-94, as defined in Section 3 of [CPALGS].
This document specifies the following OID for this algorithm: This document specifies the following OID for this algorithm:
id-HMACGostR3411-94 OBJECT IDENTIFIER ::= id-HMACGostR3411-94 OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) ru(643) rans(2) cryptopro(2) { iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
hmacgostr3411(10) } hmacgostr3411(10) }
This algorithm has the same parameters, as GOST R 34.11-94 digest This algorithm has the same parameters as the GOST R 34.11-94 digest
algorithm, and uses the same OIDs for their identification (see algorithm and uses the same OIDs for their identification (see
[CPPK]). [CPPK]).
7. Using with S/MIME 7. Use with S/MIME
This section defines use of the algorithms defined in this document This section defines the use of the algorithms defined in this
together with S/MIME [RFC 3851]. document with S/MIME [RFC3851].
7.1. Parameter micalg 7.1. Parameter micalg
When using the algorithms defined in this document, micalg parameter When using the algorithms defined in this document, micalg parameter
SHOULD be set to "gostr3411-94", otherwise it MUST be set to SHOULD be set to "gostr3411-94"; otherwise, it MUST be set to
"unknown". "unknown".
7.2. Attribute SMIMECapabilities 7.2. Attribute SMIMECapabilities
The SMIMECapability value which indicates support for the GOST R The SMIMECapability value that indicates support for the GOST R
34.11-94 digest algorithm is the SEQUENCE with the capabilityID field 34.11-94 digest algorithm is the SEQUENCE with the capabilityID field
containing the object identifier id-GostR3411-94 and no parameters. containing the object identifier id-GostR3411-94 and no parameters.
The DER encoding is: The DER encoding is:
30 08 06 06 2A 85 03 02 02 09 30 08 06 06 2A 85 03 02 02 09
The SMIMECapability value which indicates support for the GOST
The SMIMECapability value that indicates support for the GOST
28147-89 encryption algorithm is the SEQUENCE with the capabilityID 28147-89 encryption algorithm is the SEQUENCE with the capabilityID
field containing the object identifier id-Gost28147-89 and no field containing the object identifier id-Gost28147-89 and no
parameters. The DER encoding is: parameters. The DER encoding is:
30 08 06 06 2A 85 03 02 02 15 30 08 06 06 2A 85 03 02 02 15
If the sender wishes to indicate support for a specific parameter If the sender wishes to indicate support for a specific parameter
set, SMIMECapability parameters MUST contain the set, SMIMECapability parameters MUST contain the Gost28147-89-
Gost28147-89-Parameters structure. Recipients MUST ignore the Parameters structure. Recipients MUST ignore the Gost28147-89-
Gost28147-89-Parameters iv field, and assume that the sender supports Parameters iv field and assume that the sender supports the
parameters, specified in Gost28147-89-Parameters encryptionParamSet parameters specified in the Gost28147-89-Parameters
field. encryptionParamSet field.
The DER encoding for the SMIMECapability, indicating support for GOST The DER encoding for the SMIMECapability, indicating support for GOST
28147-89 with id-Gost28147-89-CryptoPro-A-ParamSet (see [CPALGS]) is: 28147-89 with id-Gost28147-89-CryptoPro-A-ParamSet (see [CPALGS]),
is:
30 1D 06 06 2A 85 03 02 02 15 30 13 04 08 00 00 30 1D 06 06 2A 85 03 02 02 15 30 13 04 08 00 00
00 00 00 00 00 00 06 07 2A 85 03 02 02 1F 01 00 00 00 00 00 00 06 07 2A 85 03 02 02 1F 01
8. Security Considerations 8. Security Considerations
Conforming applications MUST use unique values for ukm and iv. Conforming applications MUST use unique values for ukm and iv.
Recipients MAY verify that ukm and iv, specified by the sender, are Recipients MAY verify that ukm and iv, specified by the sender, are
unique. unique.
It is RECOMMENDED that software applications verify signature values, It is RECOMMENDED that software applications verify that signature
subject public keys and algorithm parameters to conform to values, subject public keys, and algorithm parameters conform to
[GOSTR341001] [GOSTR341094] standards prior to their use. [GOSTR341001] and [GOSTR341094] standards prior to their use.
Cryptographic algorithm parameters affect algorithm strength. The Cryptographic algorithm parameters affect algorithm strength. The
use of parameters not listed in [CPALGS] is NOT RECOMMENDED (see use of parameters not listed in [CPALGS] is NOT RECOMMENDED (see the
Security Considerations section of [CPALGS]). Security Considerations section of [CPALGS]).
Use of the same key for signature and key derivation is NOT Use of the same key for signature and key derivation is NOT
RECOMMENDED. When signed CMS documents are used as an analogue to a RECOMMENDED. When signed CMS documents are used as an analogue to a
manual signing, in the context of Russian Federal Digital Signature manual signing, in the context of Russian Federal Electronic Digital
Law [RFDSL], signer certificate MUST contain the keyUsage extension, Signature Law [RFEDSL], signer certificate MUST contain the keyUsage
it MUST be critical, and keyUsage MUST NOT include keyEncipherment or extension, it MUST be critical, and keyUsage MUST NOT include
keyAgreement (see [PROFILE], section 4.2.1.3). Application SHOULD be keyEncipherment or keyAgreement (see [PROFILE], Section 4.2.1.3).
submited for examination by an authorized agency in appropriate Application SHOULD be submitted for examination by an authorized
levels of target_of_evaluation (TOE), according to [RFDSL], [RFLLIC] agency in appropriate levels of target_of_evaluation (TOE), according
and [CRYPTOLIC]. to [RFEDSL], [RFLLIC], and [CRYPTOLIC].
9. Appendix Examples 9. Examples
Examples here are stored in the same format as the examples in [RFC Examples here are stored in the same format as the examples in
4134], and can be extracted using the same program. [RFC4134] and can be extracted using the same program.
If you want to extract without the program, copy all the lines If you want to extract without the program, copy all the lines
between the "|>" and "|<" markers, remove any page breaks, and remove between the "|>" and "|<" markers, remove any page breaks, and remove
the "|" in the first column of each line. The result is a valid the "|" in the first column of each line. The result is a valid
Base64 blob that can be processed by any Base64 decoder. Base64 blob that can be processed by any Base64 decoder.
9.1. Signed message 9.1. Signed Message
This message is signed using the sample certificate from section 4.2 This message is signed using the sample certificate from Section 4.2
of [CPPK]. The public key (x,y) from the same section can be used to of [CPPK]. The public key (x,y) from the same section can be used to
verify the message signature. verify the message signature.
0 296: SEQUENCE { 0 296: SEQUENCE {
4 9: OBJECT IDENTIFIER signedData 4 9: OBJECT IDENTIFIER signedData
15 281: [0] { 15 281: [0] {
19 277: SEQUENCE { 19 277: SEQUENCE {
23 1: INTEGER 1 23 1: INTEGER 1
26 12: SET { 26 12: SET {
28 10: SEQUENCE { 28 10: SEQUENCE {
skipping to change at page 13, line 46 skipping to change at page 14, line 30
|>GostR3410-2001-signed.bin |>GostR3410-2001-signed.bin
|MIIBKAYJKoZIhvcNAQcCoIIBGTCCARUCAQExDDAKBgYqhQMCAgkFADAbBgkqhkiG |MIIBKAYJKoZIhvcNAQcCoIIBGTCCARUCAQExDDAKBgYqhQMCAgkFADAbBgkqhkiG
|9w0BBwGgDgQMc2FtcGxlIHRleHQKMYHkMIHhAgEBMIGBMG0xHzAdBgNVBAMMFkdv |9w0BBwGgDgQMc2FtcGxlIHRleHQKMYHkMIHhAgEBMIGBMG0xHzAdBgNVBAMMFkdv
|c3RSMzQxMC0yMDAxIGV4YW1wbGUxEjAQBgNVBAoMCUNyeXB0b1BybzELMAkGA1UE |c3RSMzQxMC0yMDAxIGV4YW1wbGUxEjAQBgNVBAoMCUNyeXB0b1BybzELMAkGA1UE
|BhMCUlUxKTAnBgkqhkiG9w0BCQEWGkdvc3RSMzQxMC0yMDAxQGV4YW1wbGUuY29t |BhMCUlUxKTAnBgkqhkiG9w0BCQEWGkdvc3RSMzQxMC0yMDAxQGV4YW1wbGUuY29t
|AhAr9cYewhG9F8fc1GJmtC4hMAoGBiqFAwICCQUAMAoGBiqFAwICEwUABEDAw0LZ |AhAr9cYewhG9F8fc1GJmtC4hMAoGBiqFAwICCQUAMAoGBiqFAwICEwUABEDAw0LZ
|P4/+JRERiHe/icPbg0IE1iD5aCqZ9v4wO+T0yPjVtNr74caRZzQfvKZ6DRJ7/RAl |P4/+JRERiHe/icPbg0IE1iD5aCqZ9v4wO+T0yPjVtNr74caRZzQfvKZ6DRJ7/RAl
|xlHbjbL0jHF+7XKp |xlHbjbL0jHF+7XKp
|<GostR3410-2001-signed.bin |<GostR3410-2001-signed.bin
9.2. Enveloped message using Key Agreement 9.2. Enveloped Message Using Key Agreement
This message is encrypted using the sample certificate from section This message is encrypted using the sample certificate from Section
4.2 of [CPPK] as a recipient certificate. The private key 'd' from 4.2 of [CPPK] as a recipient certificate. The private key 'd' from
the same section can be used to decrypt this message. the same section can be used to decrypt this message.
0 420: SEQUENCE { 0 420: SEQUENCE {
4 9: OBJECT IDENTIFIER envelopedData 4 9: OBJECT IDENTIFIER envelopedData
15 405: [0] { 15 405: [0] {
19 401: SEQUENCE { 19 401: SEQUENCE {
23 1: INTEGER 2 23 1: INTEGER 2
26 336: SET { 26 336: SET {
30 332: [1] { 30 332: [1] {
skipping to change at page 16, line 21 skipping to change at page 17, line 5
|AgITMBIGByqFAwICJAAGByqFAwICHgEDQwAEQLNVOfRngZcrpcTZhB8n+4HtCDLm |AgITMBIGByqFAwICJAAGByqFAwICHgEDQwAEQLNVOfRngZcrpcTZhB8n+4HtCDLm
|mtTyAHi4/4Nk6tIdsHg8ff4DwfQG5DvMFrnF9vYZNxwXuKCqx9GhlLOlNiChCgQI |mtTyAHi4/4Nk6tIdsHg8ff4DwfQG5DvMFrnF9vYZNxwXuKCqx9GhlLOlNiChCgQI
|L/D20YZLMoowHgYGKoUDAgJgMBQGByqFAwICDQAwCQYHKoUDAgIfATCBszCBsDCB |L/D20YZLMoowHgYGKoUDAgJgMBQGByqFAwICDQAwCQYHKoUDAgIfATCBszCBsDCB
|gTBtMR8wHQYDVQQDDBZHb3N0UjM0MTAtMjAwMSBleGFtcGxlMRIwEAYDVQQKDAlD |gTBtMR8wHQYDVQQDDBZHb3N0UjM0MTAtMjAwMSBleGFtcGxlMRIwEAYDVQQKDAlD
|cnlwdG9Qcm8xCzAJBgNVBAYTAlJVMSkwJwYJKoZIhvcNAQkBFhpHb3N0UjM0MTAt |cnlwdG9Qcm8xCzAJBgNVBAYTAlJVMSkwJwYJKoZIhvcNAQkBFhpHb3N0UjM0MTAt
|MjAwMUBleGFtcGxlLmNvbQIQK/XGHsIRvRfH3NRiZrQuIQQqMCgEIBajHOfOTukN |MjAwMUBleGFtcGxlLmNvbQIQK/XGHsIRvRfH3NRiZrQuIQQqMCgEIBajHOfOTukN
|8ex0aQRoHsefOu24Ox8dSn75pdnLGdXoBAST/YZ+MDgGCSqGSIb3DQEHATAdBgYq |8ex0aQRoHsefOu24Ox8dSn75pdnLGdXoBAST/YZ+MDgGCSqGSIb3DQEHATAdBgYq
|hQMCAhUwEwQItzXhegc1oh0GByqFAwICHwGADDmxivS/qeJlJbZVyQ== |hQMCAhUwEwQItzXhegc1oh0GByqFAwICHwGADDmxivS/qeJlJbZVyQ==
|<GostR3410-2001-keyagree.bin |<GostR3410-2001-keyagree.bin
9.3. Enveloped message using Key Transport 9.3. Enveloped Message Using Key Transport
This message is encrypted using the sample certificate from section This message is encrypted using the sample certificate from Section
4.2 of [CPPK] as a recipient certificate. The private key 'd' from 4.2 of [CPPK] as a recipient certificate. The private key 'd' from
the same section can be used to decrypt this message. the same section can be used to decrypt this message.
0 423: SEQUENCE { 0 423: SEQUENCE {
4 9: OBJECT IDENTIFIER envelopedData 4 9: OBJECT IDENTIFIER envelopedData
15 408: [0] { 15 408: [0] {
19 404: SEQUENCE { 19 404: SEQUENCE {
23 1: INTEGER 0 23 1: INTEGER 0
26 339: SET { 26 339: SET {
30 335: SEQUENCE { 30 335: SEQUENCE {
skipping to change at page 17, line 48 skipping to change at page 18, line 31
258 99: [0] { 258 99: [0] {
260 28: SEQUENCE { 260 28: SEQUENCE {
262 6: OBJECT IDENTIFIER id-GostR3410-2001 262 6: OBJECT IDENTIFIER id-GostR3410-2001
270 18: SEQUENCE { 270 18: SEQUENCE {
272 7: OBJECT IDENTIFIER 272 7: OBJECT IDENTIFIER
: id-GostR3410-2001-CryptoPro-XchA-ParamSet : id-GostR3410-2001-CryptoPro-XchA-ParamSet
281 7: OBJECT IDENTIFIER 281 7: OBJECT IDENTIFIER
: id-GostR3411-94-CryptoProParamSet : id-GostR3411-94-CryptoProParamSet
: } : }
: } : }
290 67: BIT STRING 1 unused bits, encapsulates { 290 67: BIT STRING encapsulates {
293 64: OCTET STRING 293 64: OCTET STRING
: 4D 2B 2F 33 90 E6 DC A3 DD 55 2A CD DF E0 EF FB : 4D 2B 2F 33 90 E6 DC A3 DD 55 2A CD DF E0 EF FB
: 31 F7 73 7E 4E FF BF 78 89 8A 2B C3 CD 31 94 04 : 31 F7 73 7E 4E FF BF 78 89 8A 2B C3 CD 31 94 04
: 4B 0E 60 48 96 1F DB C7 5D 12 6F DA B2 40 8A 77 : 4B 0E 60 48 96 1F DB C7 5D 12 6F DA B2 40 8A 77
: B5 BD EA F2 EC 34 CB 23 9F 9B 8B DD 9E 12 C0 F6 : B5 BD EA F2 EC 34 CB 23 9F 9B 8B DD 9E 12 C0 F6
: } : }
: } : }
359 8: OCTET STRING 359 8: OCTET STRING
: 97 95 E3 2C 2B AD 2B 0C : 97 95 E3 2C 2B AD 2B 0C
: } : }
skipping to change at page 18, line 37 skipping to change at page 19, line 20
: } : }
: } : }
|>GostR3410-2001-keytrans.bin |>GostR3410-2001-keytrans.bin
|MIIBpwYJKoZIhvcNAQcDoIIBmDCCAZQCAQAxggFTMIIBTwIBADCBgTBtMR8wHQYD |MIIBpwYJKoZIhvcNAQcDoIIBmDCCAZQCAQAxggFTMIIBTwIBADCBgTBtMR8wHQYD
|VQQDDBZHb3N0UjM0MTAtMjAwMSBleGFtcGxlMRIwEAYDVQQKDAlDcnlwdG9Qcm8x |VQQDDBZHb3N0UjM0MTAtMjAwMSBleGFtcGxlMRIwEAYDVQQKDAlDcnlwdG9Qcm8x
|CzAJBgNVBAYTAlJVMSkwJwYJKoZIhvcNAQkBFhpHb3N0UjM0MTAtMjAwMUBleGFt |CzAJBgNVBAYTAlJVMSkwJwYJKoZIhvcNAQkBFhpHb3N0UjM0MTAtMjAwMUBleGFt
|cGxlLmNvbQIQK/XGHsIRvRfH3NRiZrQuITAcBgYqhQMCAhMwEgYHKoUDAgIkAAYH |cGxlLmNvbQIQK/XGHsIRvRfH3NRiZrQuITAcBgYqhQMCAhMwEgYHKoUDAgIkAAYH
|KoUDAgIeAQSBpzCBpDAoBCBqL6ghBpVon5/kR6qey2EVK35BYLxdjfv1PSgbGJr5 |KoUDAgIeAQSBpzCBpDAoBCBqL6ghBpVon5/kR6qey2EVK35BYLxdjfv1PSgbGJr5
|dQQENm2Yt6B4BgcqhQMCAh8BoGMwHAYGKoUDAgITMBIGByqFAwICJAAGByqFAwIC |dQQENm2Yt6B4BgcqhQMCAh8BoGMwHAYGKoUDAgITMBIGByqFAwICJAAGByqFAwIC
|HgEDQwEEQE0rLzOQ5tyj3VUqzd/g7/sx93N+Tv+/eImKK8PNMZQESw5gSJYf28dd |HgEDQwAEQE0rLzOQ5tyj3VUqzd/g7/sx93N+Tv+/eImKK8PNMZQESw5gSJYf28dd
|Em/askCKd7W96vLsNMsjn5uL3Z4SwPYECJeV4ywrrSsMMDgGCSqGSIb3DQEHATAd |Em/askCKd7W96vLsNMsjn5uL3Z4SwPYECJeV4ywrrSsMMDgGCSqGSIb3DQEHATAd
|BgYqhQMCAhUwEwQIvBCLHwv/NCkGByqFAwICHwGADKqOch3uT7Mu4w+hNw== |BgYqhQMCAhUwEwQIvBCLHwv/NCkGByqFAwICHwGADKqOch3uT7Mu4w+hNw==
|<GostR3410-2001-keytrans.bin |<GostR3410-2001-keytrans.bin
10. Appendix ASN.1 Modules 10. ASN.1 Modules
Additional ASN.1 modules, referenced here, can be found in [CPALGS]. Additional ASN.1 modules, referenced here, can be found in [CPALGS].
10.1. GostR3410-EncryptionSyntax 10.1. GostR3410-EncryptionSyntax
GostR3410-EncryptionSyntax GostR3410-EncryptionSyntax
{ iso(1) member-body(2) ru(643) rans(2) cryptopro(2) { iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
other(1) modules(1) gostR3410-EncryptionSyntax(5) 2 } other(1) modules(1) gostR3410-EncryptionSyntax(5) 2 }
DEFINITIONS ::= DEFINITIONS ::=
BEGIN BEGIN
-- EXPORTS All -- -- EXPORTS All --
-- The types and values defined in this module are exported for -- The types and values defined in this module are exported for
-- use in the other ASN.1 modules contained within the Russian -- use in the other ASN.1 modules contained within the Russian
-- Cryptography "GOST" & "GOST R" Specifications, and for the use -- Cryptography "GOST" & "GOST R" Specifications, and for the use
-- of other applications which will use them to access Russian -- of other applications which will use them to access Russian
-- Cryptography services. Other applications may use them for -- Cryptography services. Other applications may use them for
-- their own purposes, but this will not constrain extensions and -- their own purposes, but this will not constrain extensions and
-- modifications needed to maintain or improve the Russian -- modifications needed to maintain or improve the Russian
-- Cryptography service. -- Cryptography service.
skipping to change at page 22, line 28 skipping to change at page 23, line 10
GostR3410-2001-Signature ::= GostR3410-2001-Signature ::=
OCTET STRING (SIZE (64)) OCTET STRING (SIZE (64))
-- GOST R 34.10-2001 signature algorithms and parameters -- GOST R 34.10-2001 signature algorithms and parameters
GostR3410-2001-CMSSignatureAlgorithms GostR3410-2001-CMSSignatureAlgorithms
ALGORITHM-IDENTIFIER ::= { ALGORITHM-IDENTIFIER ::= {
{ GostR3410-2001-PublicKeyParameters IDENTIFIED BY { GostR3410-2001-PublicKeyParameters IDENTIFIED BY
id-GostR3410-2001 } id-GostR3410-2001 }
} }
END -- GostR3410-2001-SignatureSyntax END -- GostR3410-2001-SignatureSyntax
11. Acknowledgments 11. Acknowledgements
This document was created in accordance with "Russian Cryptographic This document was created in accordance with "Russian Cryptographic
Software Compatibility Agreement", signed by FGUE STC "Atlas", Software Compatibility Agreement", signed by FGUE STC "Atlas",
CRYPTO-PRO, Factor-TS, MD PREI, Infotecs GmbH, SPRCIS (SPbRCZI), CRYPTO-PRO, Factor-TS, MD PREI, Infotecs GmbH, SPRCIS (SPbRCZI),
Cryptocom, R-Alpha. The aim of this agreement is to achieve mutual Cryptocom, R-Alpha. The aim of this agreement is to achieve mutual
compatibility of the products and solutions. compatibility of the products and solutions.
The authors wish to thank: The authors wish to thank:
Microsoft Corporation Russia for providing information about Microsoft Corporation Russia for providing information about
company products and solutions, and also for technical consulting company products and solutions, and also for technical consulting
in PKI. in PKI.
RSA Security Russia and Demos Co Ltd for active collaboration and RSA Security Russia and Demos Co Ltd for active collaboration and
critical help in creation of this document. critical help in creation of this document.
Russ Hously (Vigil Security, LLC, housley@vigilsec.com) and Russ Housley (Vigil Security, LLC, housley@vigilsec.com) and
Vasilij Sakharov (DEMOS Co Ltd, svp@dol.ru) for encouraging the Vasilij Sakharov (DEMOS Co Ltd, svp@dol.ru) for encouraging the
authors to create this document. authors to create this document.
Prikhodko Dmitriy (VSTU, PrikhodkoDV@volgablob.ru) for invaluable
assistance in proofreading this document and verifying the form
and the contents of the ASN.1 structures mentioned or used in this
document.
12. References 12. References
12.1. Normative references: 12.1. Normative References
[CPALGS] V. Popov, I. Kurepkin, S. Leontiev, "Additional Crypto- [CMS] Housley, R., "Cryptographic Message Syntax (CMS)", RFC
graphic Algorithms for Use with GOST 28147-89, GOST R 3852, July 2004.
34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algo-
rithms.", RFC 4357, January 2006.
[CPPK] S. Leontiev, D. Shefanovskij, "Algorithms and Identi- [CPALGS] Popov, V., Kurepkin, I., and S. Leontiev, "Additional
fiers for the Internet X.509 Public Key Infrastructure Cryptographic Algorithms for Use with GOST 28147-89,
Certificates and Certificate Revocation List (CRL), GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94
corresponding to the algorithms GOST R 34.10-94, GOST R Algorithms", RFC 4357, January 2006.
34.10-2001, GOST R 34.11-94", January 2006, draft-ietf-
pkix-gost-cppk-05.txt [CPPK] Leontiev, S., Ed. and D. Shefanovskij, Ed., "Using the
GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94
Algorithms with the Internet X.509 Public Key
Infrastructure Certificate and CRL Profile", RFC 4491,
May 2006.
[GOST28147] "Cryptographic Protection for Data Processing System", [GOST28147] "Cryptographic Protection for Data Processing System",
GOST 28147-89, Gosudarstvennyi Standard of USSR, Gov- GOST 28147-89, Gosudarstvennyi Standard of USSR,
ernment Committee of the USSR for Standards, 1989. (In Government Committee of the USSR for Standards, 1989.
Russian) (In Russian)
[GOST3431195] "Information technology. Cryptographic Data Security.
Cashing function.", GOST 34.311-95, Council for
Standardization, Metrology and Certification of the
Commonwealth of Independence States (EASC), Minsk,
1995. (In Russian)
[GOST3431095] "Information technology. Cryptographic Data Security.
Produce and check procedures of Electronic Digital
Signature based on Asymmetric Cryptographic
Algorithm.", GOST 34.310-95, Council for
Standardization, Metrology and Certification of the
Commonwealth of Independence States (EASC), Minsk,
1995. (In Russian)
[GOST3431004] "Information technology. Cryptographic Data Security.
Formation and verification processes of (electronic)
digital signature based on Asymmetric Cryptographic
Algorithm.", GOST 34.310-2004, Council for
Standardization, Metrology and Certification of the
Commonwealth of Independence States (EASC), Minsk,
2004. (In Russian)
[GOSTR341094] "Information technology. Cryptographic Data Security. [GOSTR341094] "Information technology. Cryptographic Data Security.
Produce and check procedures of Electronic Digital Sig- Produce and check procedures of Electronic Digital
natures based on Asymmetric Cryptographic Algorithm.", Signatures based on Asymmetric Cryptographic
GOST R 34.10-94, Gosudarstvennyi Standard of Russian Algorithm.", GOST R 34.10-94, Gosudarstvennyi Standard
Federation, Government Committee of the Russia for of Russian Federation, Government Committee of the
Standards, 1994. (In Russian) Russia for Standards, 1994. (In Russian)
[GOSTR341001] "Information technology. Cryptographic data security. [GOSTR341001] "Information technology. Cryptographic data security.
Signature and verification processes of [electronic] Signature and verification processes of [electronic]
digital signature.", GOST R 34.10-2001, Gosudarstvennyi digital signature.", GOST R 34.10-2001, Gosudarstvennyi
Standard of Russian Federation, Government Committee of Standard of Russian Federation, Government Committee of
the Russia for Standards, 2001. (In Russian) the Russia for Standards, 2001. (In Russian)
[GOSTR341194] "Information technology. Cryptographic Data Security. [GOSTR341194] "Information technology. Cryptographic Data Security.
Hashing function.", GOST R 34.10-94, Gosudarstvennyi Hashing function.", GOST R 34.10-94, Gosudarstvennyi
Standard of Russian Federation, Government Committee of Standard of Russian Federation, Government Committee of
the Russia for Standards, 1994. (In Russian) the Russia for Standards, 1994. (In Russian)
[CMS] R. Housley, "Cryptographic Message Syntax", RFC 3369, [PROFILE] Housley, R., Polk, W., Ford, W., and D. Solo, "Internet
August 2002. X.509 Public Key Infrastructure Certificate and
Certificate Revocation List (CRL) Profile", RFC 3280,
April 2002.
[PROFILE] Housley, R., Polk, W., Ford, W. and D. Solo, "Internet [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
X.509 Public Key Infrastructure: Certificate and CRL Requirement Levels", BCP 14, RFC 2119, March 1997.
Profile", RFC 3280, April 2002.
[RFC 3851] B. Ramsdell, "Secure/Multipurpose Internet Mail Exten- [RFC3851] Ramsdell, B., "Secure/Multipurpose Internet Mail
sions (S/MIME) Version 3.1 Message Specification", RFC Extensions (S/MIME) Version 3.1 Message Specification",
3851. July 2004. RFC 3851, July 2004.
[X.208-88] CCITT. Recommendation X.208: Specification of Abstract [X.208-88] CCITT. Recommendation X.208: Specification of Abstract
Syntax Notation One (ASN.1). 1988. Syntax Notation One (ASN.1). 1988.
[X.209-88] CCITT. Recommendation X.209: Specification of Basic [X.209-88] CCITT. Recommendation X.209: Specification of Basic
Encoding Rules for Abstract Syntax Notation One Encoding Rules for Abstract Syntax Notation One
(ASN.1). 1988. (ASN.1). 1988.
12.2. Informative references: 12.2. Informative References
[RFC 2119] Bradner, S., "Key Words for Use in RFCs to Indi- [CRYPTOLIC] "Russian Federal Government Regulation on Licensing of
cateRequirement Levels", BCP 14, RFC 2119, March 1997. Selected Activity Categories in Cryptography Area", 23
Sep 2002 N 691.
[Schneier95] B. Schneier, Applied cryptography, second edition, [RFC4134] Hoffman, P., "Examples of S/MIME Messages", RFC 4134,
John Wiley & Sons, Inc., 1995. July 2005.
[RFDSL] "Russian Federal Digital Signature Law", 10 Jan 2002 N [RFEDSL] "Russian Federal Electronic Digital Signature Law", 10
1-FZ. Jan 2002 N 1-FZ.
[RFLLIC] "Russian Federal Law on Licensing of Selected Activity [RFLLIC] "Russian Federal Law on Licensing of Selected Activity
Categories", 08 Aug 2001 N 128-FZ. Categories", 08 Aug 2001 N 128-FZ.
[CRYPTOLIC] "Russian Federal Goverment Regulation on Licensing of [Schneier95] B. Schneier, Applied Cryptography, Second Edition, John
Selected Activity Categories in Cryptography Area", 23 Wiley & Sons, Inc., 1995.
Sep 2002 N 691.
Contact Information Authors' Addresses
Serguei Leontiev Serguei Leontiev, Ed.
CRYPTO-PRO CRYPTO-PRO
38, Obraztsova, 38, Obraztsova,
Moscow, 127018, Russian Federation Moscow, 127018, Russian Federation
EMail: lse@cryptopro.ru EMail: lse@cryptopro.ru
Gregory Chudov Grigorij Chudov, Ed.
CRYPTO-PRO CRYPTO-PRO
38, Obraztsova, 38, Obraztsova,
Moscow, 127018, Russian Federation Moscow, 127018, Russian Federation
EMail: chudov@cryptopro.ru EMail: chudov@cryptopro.ru
Vladimir Popov Vladimir Popov
CRYPTO-PRO CRYPTO-PRO
38, Obraztsova, 38, Obraztsova,
Moscow, 127018, Russian Federation Moscow, 127018, Russian Federation
skipping to change at page 26, line 18 skipping to change at page 29, line 5
EMail: igus@cryptocom.ru EMail: igus@cryptocom.ru
Anatolij Erkin Anatolij Erkin
SPRCIS (SPbRCZI) SPRCIS (SPbRCZI)
1, Obrucheva, 1, Obrucheva,
St.Petersburg, 195220, Russian Federation St.Petersburg, 195220, Russian Federation
EMail: erkin@nevsky.net EMail: erkin@nevsky.net
Disclaimer of Validity Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Full Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the ISOC's procedures with respect to rights in ISOC Documents can on the procedures with respect to rights in RFC documents can be
be found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment Acknowledgement
Funding for the RFC Editor function is provided by the IETF Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA). Administrative Support Activity (IASA).
 End of changes. 89 change blocks. 
240 lines changed or deleted 259 lines changed or added

This html diff was produced by rfcdiff 1.31. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/