< draft-ietf-pkix-gost-cppk-02.txt   draft-ietf-pkix-gost-cppk-03.txt >
PKIX Working Group Serguei Leontiev, CRYPTO-PRO PKIX Working Group Serguei Leontiev, CRYPTO-PRO
Internet Draft Dennis Shefanovskij, DEMOS Co Ltd Internet Draft Dennis Shefanovski, DEMOS Co Ltd
Expires August 5, 2005 February 5, 2005 Expires March 8, 2006 September 8, 2005
Intended Category: Informational Intended Category: Informational
Using the GOST R 34.10-94, GOST R 34.10-2001 and Using the GOST R 34.10-94, GOST R 34.10-2001 and
GOST R 34.11-94 algorithms with the GOST R 34.11-94 algorithms with the
Internet X.509 Public Key Infrastructure Internet X.509 Public Key Infrastructure
Certificate and CRL Profile. Certificate and CRL Profile.
<draft-ietf-pkix-gost-cppk-02.txt> <draft-ietf-pkix-gost-cppk-03.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
and any of which I become aware will be disclosed, in accordance with have been or will be disclosed, and any of which he or she becomes
RFC 3668. aware will be disclosed, in accordance with Section 6 of BCP 79.
This document is an Internet Draft and is subject to all provisions Internet-Drafts are working documents of the Internet Engineering
of Section 10 of RFC2026. Internet Drafts are working documents of Task Force (IETF), its areas, and its working groups. Note that
the Internet Engineering Task Force (IETF), its areas, and its other groups may also distribute working documents as Internet-
working groups. Note that other groups may also distribute working Drafts.
documents as Internet Drafts. Internet Drafts are draft documents
valid for a maximum of 6 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 a
"work in progress".
The list of current Internet Drafts can be accessed at Internet-Drafts are draft documents valid for a maximum of six months
http://www.ietf.org/1id-abstracts.html 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 a "work in progress."
The list of Internet Draft Shadow Directories can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/1id-abstracts.html.
Copyright (C) The Internet Society (2005). All Rights Reserved. The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 8, 2006.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract Abstract
This document describes identifiers and appropriate parameters for This document supplements RFC 3279. It describes encoding formats,
the algorithms GOST R 34.10-94, GOST R 34.10-2001, GOST R 34.11-94, identifiers and parameter formats for the algorithms GOST R 34.10-94,
and also ASN.1 encoding scheme for digital signatures and public GOST R 34.10-2001 and GOST R 34.11-94 for use in Internet X.509
keys, used in Internet X.509 Public Key Infrastructure (PKI). This Public Key Infrastructure (PKI).
specification extends [RFC3279], "Algorithms and Identifiers for the
Internet X.509 Public Key Infrastructure Certificate and Certificate
Revocation List (CRL) Profile" and, correspondingly, [RFC3280],
"Internet X.509 Public Key Infrastructure: Certificate and
Certificate Revocation List (CRL) Profile". All implementations of
this specification MUST also satisfy the requirements of [RFC3280].
Table of Contents Table of Contents
1 Introduction. . . . . . . . . . . . . . . . . . . . . . 2 1 Introduction. . . . . . . . . . . . . . . . . . . . . . 2
2 Algorithm Support . . . . . . . . . . . . . . . . . . . 3 2 Algorithm Support . . . . . . . . . . . . . . . . . . . 3
2.1 One-way Hash Function . . . . . . . . . . . . . . . . . 3 2.1 One-way Hash Function . . . . . . . . . . . . . . . . . 3
2.1.1 One-way Hash Function GOST R 34.11-94 . . . . . . . . . 3 2.1.1 One-way Hash Function GOST R 34.11-94 . . . . . . . . . 3
2.2 Signature Algorithms. . . . . . . . . . . . . . . . . . 4 2.2 Signature Algorithms. . . . . . . . . . . . . . . . . . 3
2.2.1 Signature Algorithm GOST R 34.10-94 . . . . . . . . . . 4 2.2.1 Signature Algorithm GOST R 34.10-94 . . . . . . . . . . 4
2.2.2 Signature Algorithm GOST R 34.10-2001 . . . . . . . . . 5 2.2.2 Signature Algorithm GOST R 34.10-2001 . . . . . . . . . 5
2.3 Subject Public Key Algorithms . . . . . . . . . . . . . 6 2.3 Subject Public Key Algorithms . . . . . . . . . . . . . 5
2.3.1 GOST R 34.10-94 Keys. . . . . . . . . . . . . . . . . . 6 2.3.1 GOST R 34.10-94 Keys. . . . . . . . . . . . . . . . . . 6
2.3.2 GOST R 34.10-2001 Keys. . . . . . . . . . . . . . . . . 8 2.3.2 GOST R 34.10-2001 Keys. . . . . . . . . . . . . . . . . 7
3 Security Considerations . . . . . . . . . . . . . . . . 10 3 Security Considerations . . . . . . . . . . . . . . . . 9
4 Appendix Examples . . . . . . . . . . . . . . . . . . . 11 4 Appendix Examples . . . . . . . . . . . . . . . . . . . 10
4.1 GOST R 34.10-94 Certificate . . . . . . . . . . . . . . 11 4.1 GOST R 34.10-94 Certificate . . . . . . . . . . . . . . 10
4.2 GOST R 34.10-2001 Certificate . . . . . . . . . . . . . 13 4.2 GOST R 34.10-2001 Certificate . . . . . . . . . . . . . 12
5 References. . . . . . . . . . . . . . . . . . . . . . . 16 5 References. . . . . . . . . . . . . . . . . . . . . . . 15
Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 17 Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 16
Author's Addresses . . . . . . . . . . . . . . . . . . . . . . 18 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . 17
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 19 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 18
1 Introduction 1 Introduction
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].
This document defines identifiers and corresponding algorithm This document supplements RFC 3279 [PKALGS]. It describes the
parameters and attributes proposed by CRYPTO-PRO Company within conventions for using the GOST R 34.10-94 and GOST R 34.10-2001
"Russian Cryptographic Software Compatibility Agreement" community signature algorithms, VKO GOST R 34.10-94 and VKO GOST R 34.10-2001
for the algorithms GOST R 34.10-94, GOST R 34.10-2001, GOST R key derivation algorithms, and GOST R 34.11-94 one-way hash function
34.11-94, key derivation algorithms based on GOST R 34.10-94 public in the Internet X.509 Public Key Infrastructure (PKI) [PROFILE].
keys, key derivation algorithms based on GOST R 34.10-2001 public
keys, and also ASN.1 encoding [X.660] for digital signatures and
public keys, used in Internet X.509 Public Key Infrastructure (PKI).
This specification extends [RFC3279], "Algorithms and Identifiers for
the Internet X.509 Public Key Infrastructure Certificate and
Certificate Revocation List (CRL) Profile" and, correspondingly,
[RFC3280], "Internet X.509 Public Key Infrastructure: Certificate and
Certificate Revocation List (CRL) Profile". All implementations of
this specification MUST also satisfy the requirements of [RFC3280].
This specification defines the content of the signatureAlgorithm,
signatureValue, signature, and subjectPublicKeyInfo fields within
Internet X.509 certificates and CRLs.
This document defines the use of one-way hash-function GOST R
34.11-94 [GOST3411] with digital signatures. This algorithm is used
in conjunction with digital signature algorithms.
This specification describes the encoding of digital signatures,
generated with the following cryptographic algorithms:
* GOST R 34.10-94; This document is a proposal put forward by the CRYPT-PRO Company to
* GOST R 34.10-2001. provide supplemental information and specifications needed by the
"Russian Cryptographic Software Compatibility Agreement" community.
This document also defines the contents of the subjectPublicKeyInfo The algorithm identifiers and associated parameters for subject
field for Internet X.509 certificates. For each algorithm, the public keys that employ the GOST R 34.10-94 [GOSTR341094] / VKO GOST
appropriate alternatives for the keyUsage extension are provided. R 34.10-94 [CPALGS] or the GOST R 34.10-2001 [GOSTR341001] / VKO GOST
This specification describes encoding formats for public keys used R 34.10-2001 [CPALGS] algorithms, and the encoding format for the
with the following cryptographic algorithms: signatures produced by these algorithms are specified. Also, the
algorithm identifiers for using the GOST R 34.11-94 one-way hash
function with the GOST R 34.10-94 and GOST R 34.10-2001 signature
algorithms are specified.
* GOST R 34.10-94 [GOST341094]; This specification defines the contents of the signatureAlgorithm,
* GOST R 34.10-2001 [GOST34102001]; signatureValue, signature, and subjectPublicKeyInfo fields within
* Key derivation algorithm VKO GOST R 34.10-94 [CPALGS]; Internet X.509 Certificates and CRLs. For each algorithm, the
* Key derivation algorithm VKO GOST R 34.10-2001 [CPALGS]; appropriate alternatives for the keyUsage certificate extension are
provided.
ASN.1 modules, including all the definitions used in this document ASN.1 modules, including all the definitions used in this document
can be found in [CPALGS]. can be found in [CPALGS].
2 Algorithm Support 2 Algorithm Support
This section is an overview of cryptographic algorithms, that may be This section is an overview of cryptographic algorithms, that may be
used within the Internet X.509 certificates and CRL profile used within the Internet X.509 certificates and CRL profile
[RFC3280]. It describes one-way hash functions and digital signature [PROFILE]. It describes one-way hash functions and digital signature
algorithms, that may be used to sign certificates and CRLs, and algorithms, that may be used to sign certificates and CRLs, and
identifies OIDs and ASN.1 encoding for public keys contained in a identifies OIDs and ASN.1 encoding for public keys contained in a
certificate. certificate.
The conforming CAs and/or applications MUST fully support digital The conforming CAs and/or applications MUST fully support digital
signatures and public keys for at least one of the specified signatures and public keys for at least one of the specified
algorithms. algorithms.
2.1 One-way Hash Function 2.1 One-way Hash Function
This section identifies the use of one-way, collision free hash This section identifies the use of one-way, collision free hash
function GOST R 34.11-94 - the only one that can be used in digital function GOST R 34.11-94 - the only one that can be used in digital
signature algorithms GOST R 34.10-94/2001. The data that is hashed signature algorithms GOST R 34.10-94/2001. The data that is hashed
for certificates and CRL signing is fully described in [RFC3280]. for certificates and CRL signing is fully described in RFC 3280
[PROFILE].
2.1.1 One-way Hash Function GOST R 34.11-94 2.1.1 One-way Hash Function GOST R 34.11-94
GOST R 34.11-94 has been developed by "GUBS of Federal Agency GOST R 34.11-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". The algorithm GOST R and Research Institute of Standardization". The algorithm GOST R
34.11-94 produces a 256-bit hash value of the arbitrary finite bit 34.11-94 produces a 256-bit hash value of the arbitrary finite bit
length input. This document does not contain GOST R 34.11-94 full length input. This document does not contain the full GOST R 34.11-94
specification, which can be found in [GOSTR3411] in Russian. It's specification, which can be found in [GOSTR3411] in Russian.
brief technical description in english can be found in [Schneier95], [Schneier95] ch. 18.11, p. 454. contains a brief technical
ch. 18.11, p. 454. description in English.
This function is always used with default parameter set This function MUST always be used with parameter set identified by
gostR3411CryptoProParamSetAI (see section 8.2 of [CPALGS]). id-GostR3411-94-CryptoProParamSet (see section 8.2 of [CPALGS]).
2.2 Signature Algorithms 2.2 Signature Algorithms
Conforming CAs may use GOST R 34.10-94 or GOST R 34.10-2001 signature Conforming CAs may use GOST R 34.10-94 or GOST R 34.10-2001 signature
algorithms to sign certificates and CRLs. The signatureAlgorithm algorithms to sign certificates and CRLs.
field of Certificate or CertificateList indicates the signature
algorithm ID, and associated parameters. This section also defines
algorithm identifiers and parameters that MUST be used in the
signatureAlgorithm field in a Certificate or CertificateList.
Signature algorithms are always used conjointly with a one-way hash These signature algorithms MUST always be used with a one-way hash
function GOST R 34.11-94 as indicated in [GOSTR341094] and function GOST R 34.11-94 as indicated in [GOSTR341094] and
[GOSTR34102001]. [GOSTR341001].
This section identifies OIDs for GOST R 34.10-94 and GOST R This section defines algorithm identifiers and parameters to be used
34.10-2001 algorithms. The contents of the parameters component for in the signatureAlgorithm field in a Certificate or CertificateList.
each algorithm may vary and details are provided below for each
algorithm separately.
2.2.1 Signature Algorithm GOST R 34.10-94 2.2.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 document does not
MUST be used conjointly with one-way, collision free hash function contain the full GOST R 34.10-94 specification, which can be found in
GOST R 34.11-94. This document does not contain GOST R 34.10-94 [GOSTR341094] in Russian. [Schneier95] ch. 20.3, p. 495 contains a
standard description, which is fully described in [GOSTR341094] in brief technical description in English.
Russian, and brief description in English could be found in
[Schneier95] ch. 20.3, p. 495.
The ASN.1 OID used to identify GOST R 34.10-94 signature algorithm in
fields signatureAlgorithm in Certificate and CertificateList is:
id-CryptoPro-algorithms OBJECT IDENTIFIER ::= The ASN.1 object identifier used to identify this signature algorithm
{ iso(1) member-body(2) ru(643) rans(2) cryptopro(2) } is:
id-GostR3411-94-with-GostR3410-94 OBJECT IDENTIFIER ::= id-GostR3411-94-with-GostR3410-94 OBJECT IDENTIFIER ::=
{ id-CryptoPro-algorithms gostR3411-94-with-gostR3410-94(4)} { iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
gostR3411-94-with-gostR3410-94(4) }
GostR3410-94-CertificateSignatureAlgorithms
ALGORITHM-IDENTIFIER ::= {
{ NULL IDENTIFIED BY
id-GostR3411-94-with-GostR3410-94 } |
{ GostR3410-94-PublicKeyParameters IDENTIFIED BY
id-GostR3411-94-with-GostR3410-94 } }
GostR3410-94-PublicKeyParameters are defined in section 2.3.1.
When the id-GostR3411-94-with-GostR3410-94 algorithm identifier When the id-GostR3411-94-with-GostR3410-94 algorithm identifier
appears in an AlgorithmIdentifier and parameters are omitted, the appears as the algorithm field in an AlgorithmIdentifier, the
parameters from the public key of the signer's certificate MUST be encoding SHALL omit the parameters field. That is, the
used. If the parameters from the public key of the signer's AlgorithmIdentifier SHALL be a SEQUENCE of one component: the OBJECT
certificate are also omited, and it's issuer's certificate has the IDENTIFIER id-GostR3411-94-with-GostR3410-94.
same public key algorithm, parameters from the public key of the
issuer's certificate MUST be used, and so on. The parameters in the subjectPublicKeyInfo field of the certificate
of the issuer SHALL apply to the verification of the signature.
Signature algorithm GOST R 34.10-94 generates digital signature in Signature algorithm GOST R 34.10-94 generates digital signature in
the form of a binary 512-bit vector (<r'>256||<s>256). That is, the the form of two 256-bit numbers r' and s. Its octet string
least-significant (1-st) bit of signatureValue BIT STRING contains representation consists of 64 octets, where first 32 octets contain
the least-significant (1-st) bit of <s>, and the most-significant big endian representation of s and second 32 octets contain big
(512th) bit of signatureValue contains the most-significant (256th) endian representation of r'.
bit of <r'>.
Signature values in CMS [CMS] are represented as octet strings, and
the output is used directly. However, signature values in
certificates and CRLs [PROFILE] are represented as bit strings, and
conversion is needed.
To convert a signature value to a bit string, the most significant
bit of the first octet of the signature value SHALL become the first
bit of the bit string, and so on through the least significant bit of
the last octet of the signature value, which SHALL become the last
bit of the bit string.
2.2.2 Signature Algorithm GOST R 34.10-2001 2.2.2 Signature Algorithm GOST R 34.10-2001
GOST R 34.10-2001 was developed by "GUBS of Federal Agency Government GOST R 34.10-2001 was developed by "GUBS of Federal Agency Government
Communication and Information" and "All-Russian Scientific and Communication and Information" and "All-Russian Scientific and
Research Institute of Standardization". This signature algorithm Research Institute of Standardization". This document does not
MUST be used conjointly with one-way, collision free hash function contain the full GOST R 34.10-2001 specification, which can be found
GOST R 34.11-94. This document does not contain GOST R 34.10-2001 in [GOSTR341001] in Russian.
standard description, which is fully described in [GOSTR34102001].
The ASN.1 OID used to identify GOST R 34.10-2001 signature algorithm The ASN.1 object identifier used to identify this signature algorithm
in fields signatureAlgorithm of Certificate and CertificateList is: is:
id-GostR3411-94-with-GostR3410-2001 OBJECT IDENTIFIER ::= id-GostR3411-94-with-GostR3410-2001 OBJECT IDENTIFIER ::=
{ id-CryptoPro-algorithms gostR3411-94-with-gostR3410-2001(3) } { iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
gostR3411-94-with-gostR3410-2001(3) }
GostR3410-2001-CertificateSignatureAlgorithms
ALGORITHM-IDENTIFIER ::= {
{ NULL IDENTIFIED BY
id-GostR3411-94-with-GostR3410-2001 } |
{ GostR3410-2001-PublicKeyParameters IDENTIFIED BY
id-GostR3411-94-with-GostR3410-2001 } }
GostR3410-2001-PublicKeyParameters are defined in section 2.3.2.
When the id-GostR3411-94-with-GostR3410-2001 algorithm identifier When the id-GostR3411-94-with-GostR3410-2001 algorithm identifier
appears in an AlgorithmIdentifier and parameters are omitted, the appears as the algorithm field in an AlgorithmIdentifier, the
parameters from the public key of the signer's certificate MUST be encoding SHALL omit the parameters field. That is, the
used. If the parameters from the public key of the signer's AlgorithmIdentifier SHALL be a SEQUENCE of one component: the OBJECT
certificate are also omited, and it's issuer's certificate has the IDENTIFIER id-GostR3411-94-with-GostR3410-2001.
same public key algorithm, parameters from the public key of the
issuer's certificate MUST be used, and so on. The parameters in the subjectPublicKeyInfo field of the certificate
of the issuer SHALL apply to the verification of the signature.
Signature algorithm GOST R 34.10-2001 generates digital signature in Signature algorithm GOST R 34.10-2001 generates digital signature in
the form of a binary 512-bit vector (<r'>256||<s>256). That is, the the form of two 256-bit numbers r' and s. Its octet string
least-significant (1-st) bit of signatureValue BIT STRING contains representation consists of 64 octets, where first 32 octets contain
the least-significant (1-st) bit of <s>, and the most-significant big endian representation of s and second 32 octets contain big
(512th) bit of signatureValue contains the most-significant (256th) endian representation of r'.
bit of <r'>.
Signature values in CMS [CMS] are represented as octet strings, and
the output is used directly. However, signature values in
certificates and CRLs [PROFILE] are represented as bit strings, and
conversion is needed.
To convert a signature value to a bit string, the most significant
bit of the first octet of the signature value SHALL become the first
bit of the bit string, and so on through the least significant bit of
the last octet of the signature value, which SHALL become the last
bit of the bit string.
2.3 Subject Public Key Algorithms 2.3 Subject Public Key Algorithms
In according to [RFC3280] the certificates may contain a public key This section defines OIDs and public key parameters for public keys
for any algorithm. Within the framework of this specification the that employ the GOST R 34.10-94 [GOSTR341094] / VKO GOST R 34.10-94
only GOST R 34.10-94 and GOST R 34.10-2001 public key algorithms [CPALGS] or the GOST R 34.10-2001 [GOSTR341001] / VKO GOST R
defined. The algorithm and associated parameters are definable as OID 34.10-2001 [CPALGS] algorithms.
in certificate through ASN.1 structure AlgorithmIdentifier.
This section identifies defines OID and public key parameters for the Use of the same key for both signature and key derivation is NOT
GOST R 34.10-94 and GOST R 34.10-2001 algorithms. The appropriate CA RECOMMENDED. The intended application for the key MAY be indicated in
MUST use the predefined OID issuing certificates containing public the keyUsage certificate extension (see [PROFILE], Section 4.2.1.3).
keys for these algorithms. The appropriate applications supporting
any of these algorithms MUST fully recognize the OID identified in
this section
2.3.1 GOST R 34.10-94 Keys 2.3.1 GOST R 34.10-94 Keys
This section defines OID and parameter encoding for inclusion of GOST GOST R 34.10-94 public keys can be used for signature algorithm GOST
R 34.10-94 public key in certificate. Such public key can be used R 34.10-94 [GOSTR341094] and for key derivation algorithm VKO GOST R
for digital signature validation algorithm GOST R 34.10-94 34.10-94 [CPALGS].
[GOSTR341094], and for key derivation algorithm VKO GOST R 34.10-94
[CPALGS].
An assumed cryptographic key usage MAY be specified by keyUsage
extension [RFC3280]. The usage of the same key for signature and key
derivation is NOT RECOMMENDED, but possible.
Public key OID for GOST R 34.10-94 declared in this document is: GOST R 34.10-94 public keys are identified by the following OID:
id-GostR3410-94 OBJECT IDENTIFIER ::= id-GostR3410-94 OBJECT IDENTIFIER ::=
{ id-CryptoPro-algorithms gostR3410-94(20) } { iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
gostR3410-94(20) }
SubjectPublicKeyInfo.algorithm.algorithm field (see [RFC3280]) for SubjectPublicKeyInfo.algorithm.algorithm field (see RFC 3280
GOST R 34.10-94 keys MUST be id-GostR3410-94; [PROFILE]) for GOST R 34.10-94 keys MUST be id-GostR3410-94.
SubjectPublicKeyInfo.algorithm.parameters in this case MUST have the When the id-GostR3410-94 algorithm identifier appears as the
following structure: algorithm field in an AlgorithmIdentifier, the encoding MAY
completely omit the parameters field or set it to null. Otherwise
this field MUST have the following structure:
GostR3410-94-PublicKeyParameters ::= GostR3410-94-PublicKeyParameters ::=
SEQUENCE { SEQUENCE {
publicKeyParamSet publicKeyParamSet
OBJECT IDENTIFIER, OBJECT IDENTIFIER,
digestParamSet digestParamSet
OBJECT IDENTIFIER, OBJECT IDENTIFIER,
encryptionParamSet encryptionParamSet
OBJECT IDENTIFIER OPTIONAL OBJECT IDENTIFIER DEFAULT
id-Gost28147-89-CryptoPro-A-ParamSet
} }
where: where:
* publicKeyParamSet - public key parameters identifier for GOST R * publicKeyParamSet - public key parameters identifier for GOST R
34.10-94 (see section 8.3 of [CPALGS]) 34.10-94 (see section 8.3 of [CPALGS])
* digestParamSet - parameters identifier for GOST R 34.11-94 (see * digestParamSet - parameters identifier for GOST R 34.11-94 (see
section 8.2 of [CPALGS]) section 8.2 of [CPALGS])
* encryptionParamSet - optional parameters identifier for GOST * encryptionParamSet - parameters identifier for GOST 28147-89 (see
28147-89 (see section 8.1 of [CPALGS]) MAY be present in any section 8.1 of [CPALGS])
certificate and MUST be present if keyUsage includes keyAgreement or
keyEnchiperment.
If GOST R 34.10-94 algorithm parameters are omitted in
subjectPublicKeyInfo, and CA signs subject certificate using GOST R
34.10-94, then GOST R 34.10-94 parameters taken from
subjectPublicKeyInfo field of issuer certificate are applicable to
public key of GOST R 34.10-94 subject. That is, cryptographic
parameters inheritance takes place. If subjectPublicKeyInfo
AlgorithmIdentifier field contain no parameters, but CA sign
certificate using signature algorithm different from GOST R 34.10-94,
such certificate MUST be rejected by conforming applications.
Public key GOST R 34.10-94 MUST be ASN.1 encoded in following way. Absence of parameters SHALL be processed as described in RFC 3280
[PROFILE], section 6.1, that is, parameters are inherited from the
issuer certificate if possible.
In GOST R 34.10-94 public key is a number y = a^x (mod p), where a The GOST R 34.10-94 public key MUST be ASN.1 DER encoded as an OCTET
and p - parameters, and y is a bit-vector (<y>1024), at that STRING; this encoding shall be used as the contents (i.e., the value)
encoding should present <y>1024 (BIT STRING) as a vector holding of the subjectPublicKey component (a BIT STRING) of the
data in a little-endian. At first, a key is presented as an OCTET SubjectPublicKeyInfo data element.
STRING, and then, being DER-encoded, presented as a BIT STRING.
GostR3410-94-PublicKey ::= BIT STRING GostR3410-94-PublicKey ::= OCTET STRING -- public key, Y
GostR3410-94-PublicKeyOctetString ::= OCTET STRING GostR3410-94-PublicKey MUST must contain 128 octets of the little-
endian representation of the public key Y = a^x (mod p), where a and
p - parameters.
If the keyUsage extension is present in an end-entity certificate, If the keyUsage extension is present in an end-entity certificate,
which contains a GOST R 34.10-94 public key, the following values MAY which contains a GOST R 34.10-94 public key, the following values MAY
be present: be present:
digitalSignature; digitalSignature;
nonRepudiation. nonRepudiation.
keyEncipherment; keyEncipherment;
keyAgreement. keyAgreement.
skipping to change at page 8, line 23 skipping to change at page 7, line 34
certificate GOST R 34.10-94 public key, the following values MAY be certificate GOST R 34.10-94 public key, the following values MAY be
present as well: present as well:
encipherOnly; encipherOnly;
decipherOnly. decipherOnly.
The keyUsage extension MUST NOT assert both encipherOnly and The keyUsage extension MUST NOT assert both encipherOnly and
decipherOnly. decipherOnly.
If the keyUsage extension is present in an CA or CRL signer If the keyUsage extension is present in an CA or CRL signer
certificate which contain a GOST R 34.10-94 public key, the following certificate which contains a GOST R 34.10-94 public key, the
values MAY be present: following values MAY be present:
digitalSignature; digitalSignature;
nonRepudiation; nonRepudiation;
keyCertSign; keyCertSign;
cRLSign. cRLSign.
2.3.2 GOST R 34.10-2001 Keys 2.3.2 GOST R 34.10-2001 Keys
This section defines OID and parameter encoding for inclusion of GOST GOST R 34.10-2001 public keys can be used for signature algorithm
R 34.10-2001 public key in certificate. Such public key can be used GOST R 34.10-2001 [GOSTR341001] and for key derivation algorithm VKO
for digital signature validation algorithm GOST R 34.10-2001 GOST R 34.10-2001 [CPALGS].
[GOSTR34102001], and for key derivation algorithm VKO GOST R
34.10-2001 [CPALGS].
An assumed cryptographic key usage MAY be specified by keyUsage
extension [RFC3280]. The usage of the same key for signature and key
derivation is NOT RECOMMENDED, but possible.
Public key OID for GOST R 34.10-2001 declared in this document is: GOST R 34.10-2001 public keys are identified by the following OID:
id-GostR3410-2001 OBJECT IDENTIFIER ::= id-GostR3410-2001 OBJECT IDENTIFIER ::=
{ id-CryptoPro-algorithms gostR3410-2001(19) } { iso(1) member-body(2) ru(643) rans(2) cryptopro(2)
gostR3410-2001(19) }
SubjectPublicKeyInfo.algorithm.algorithm field (see [RFC3280]) for SubjectPublicKeyInfo.algorithm.algorithm field (see RFC 3280
GOST R 34.10-2001 keys MUST be id-GostR3410-2001; [PROFILE]) for GOST R 34.10-2001 keys MUST be id-GostR3410-2001.
SubjectPublicKeyInfo.algorithm.parameters in this case MUST have the When the id-GostR3410-2001 algorithm identifier appears as the
following structure: algorithm field in an AlgorithmIdentifier, the encoding MAY
completely omit the parameters field or set it to null. Otherwise
this field MUST have the following structure:
GostR3410-2001-PublicKeyParameters ::= GostR3410-2001-PublicKeyParameters ::=
SEQUENCE { SEQUENCE {
publicKeyParamSet publicKeyParamSet
OBJECT IDENTIFIER, OBJECT IDENTIFIER,
digestParamSet digestParamSet
OBJECT IDENTIFIER, OBJECT IDENTIFIER,
encryptionParamSet encryptionParamSet
OBJECT IDENTIFIER OPTIONAL OBJECT IDENTIFIER DEFAULT
id-Gost28147-89-CryptoPro-A-ParamSet
} }
where: where:
* publicKeyParamSet - public key parameters identifier for GOST R * publicKeyParamSet - public key parameters identifier for GOST R
34.10-2001 (see section 8.4 of [CPALGS]) 34.10-2001 (see section 8.4 of [CPALGS])
* digestParamSet - parameters identifier for GOST R 34.11-94 (see * digestParamSet - parameters identifier for GOST R 34.11-94 (see
section 8.2 of [CPALGS]) section 8.2 of [CPALGS])
* encryptionParamSet - optional parameters identifier for GOST * encryptionParamSet - parameters identifier for GOST 28147-89 (see
28147-89 (see section 8.1 of [CPALGS]) MAY be present in any section 8.1 of [CPALGS])
certificate and MUST be present if keyUsage includes keyAgreement or
keyEnchiperment.
If GOST R 34.10-2001 algorithm parameters are omitted in
subjectPublicKeyInfo, and CA signs subject certificate using GOST R
34.10-2001, then GOST R 34.10-2001 parameters taken from
subjectPublicKeyInfo field of issuer certificate are applicable to
public key of GOST R 34.10-2001 subject. That is, cryptographic
parameters inheritance takes place. If subjectPublicKeyInfo
AlgorithmIdentifier field contain no parameters, but CA sign
certificate using signature algorithm different from GOST R
34.10-2001, such certificate MUST be rejected by conforming
applications.
GOST R 34.10-2001 public key MUST be ASN.1 encoded in a following
way. GOST R 34.10-2001 specifies that public key is a point on the
elliptic curve Q = dP, where d is a private key, P is a base point,
and Q presents in a way of 512-bit vector (<Xq>256||<Yq>256). This
vector is DER-encoded as two data blocks. At first, <Xq>256 block,
then <Yq>256 block. subjectPublicKey field BIT STRING type is
presented as a taken up object GostR3410-2001-PublicKeyOctetString.
At that, least-significant of the first octet Absence of parameters SHALL be processed as described in RFC 3280
(GostR3410-2001-PublicKeyOctetString[0]) corresponds to least- [PROFILE], section 6.1, that is, parameters are inherited from the
significant (1-st) of vector <Xq>256||<Yq>256 (Yq1 = issuer certificate if possible.
(GostR3410-2001-PublicKeyOctetString[0] & 1)).
Whereas most-significant of 64-th octet The GOST R 34.10-2001 public key MUST be ASN.1 DER encoded as an
(GostR3410-2001-PublicKeyOctetString[63]) corresponds to most- OCTET STRING; this encoding shall be used as the contents (i.e., the
significant (512-d) of vector <Xq>256||<Yq>256 (Xq256 = value) of the subjectPublicKey component (a BIT STRING) of the
((GostR3410-2001-PublicKeyOctetString[63] & 0x80)>>7)). SubjectPublicKeyInfo data element.
In other words, <Xq>256||<Yq>256 vector is stored in little-endian, GostR3410-2001-PublicKey ::= OCTET STRING -- public key vector, Q
that correspond binary vector form and their concatenation in GOST R
34.10-2001 ch. 5.3. At first, key is placed in OCTET STRING, than is
DER-encoded and placed in BIT STRING.
GostR3410-2001-PublicKey ::= BIT STRING According to [GOSTR341001], public key is a point on the elliptic
curve Q = (x,y).
GostR3410-2001-PublicKeyOctetString ::= OCTET STRING GostR3410-2001-PublicKey MUST must contain 64 octets, where first 32
octets contain little endian representation of x and second 32 octets
contain little endian representation of y. This corresponds to the
binary representation of (<y>256||<x>256) from [GOSTR341001], ch.
5.3.
If the keyUsage extension is present in an end-entity certificate, If the keyUsage extension is present in an end-entity certificate,
which conveys a GOST R 34.10-2001 public key, the following values which contains a GOST R 34.10-2001 public key, the following values
MAY be present: MAY be present:
digitalSignature, digitalSignature,
nonRepudiation, nonRepudiation,
keyEncipherment, keyEncipherment,
keyAgreement. keyAgreement.
If the keyAgreement or keyEnchiperment extension is present in a If the keyAgreement or keyEnchiperment extension is present in a
certificate, the following values MAY be present: certificate, the following values MAY be present:
encipherOnly, encipherOnly,
decipherOnly. decipherOnly.
The keyUsage extension MUST NOT assert both encipherOnly and The keyUsage extension MUST NOT assert both encipherOnly and
decipherOnly. decipherOnly.
If the keyUsage extension is present in an CA or CRL signer If the keyUsage extension is present in an CA or CRL signer
certificate which contain a GOST R 34.10-2001 public key, the certificate which contains a GOST R 34.10-2001 public key, the
following values MAY be present: following values MAY be present:
digitalSignature, digitalSignature,
nonRepudiation, nonRepudiation,
keyCertSign, keyCertSign,
cRLSign. cRLSign.
3 Security Considerations 3 Security Considerations
It is RECCOMENDED, that applications verify signature values and It is RECOMMENDED, that applications verify signature values and
subject public keys to conform to [GOSTR34102001], [GOSTR341094] subject public keys to conform to [GOSTR341001] [GOSTR341094]
standards prior to their use. standards prior to their use.
When certificate is used as analogue to a manual signing, in the When certificate is used as analogue to a manual signing, in the
context of Russian Federal Digital Signature Law [RFDSL], certificate context of Russian Federal Digital Signature Law [RFDSL], certificate
MUST contain keyUsage extension, it MUST be critical, and keyUsage MUST contain keyUsage extension, it MUST be critical, and keyUsage
MUST NOT include keyEncipherment and keyAgreement. MUST NOT include keyEncipherment and keyAgreement.
When certificate validity period (typicaly 5 years for end entities When certificate validity period (typicaly 5 years for end entities
and 7 years for CAs in Russia) is not equal to the private key and 7 years for CAs in Russia) is not equal to the private key
validity period (typicaly 15 months in Russia) it is RECOMENDED to validity period (typicaly 15 months in Russia) it is RECOMMENDED to
use private key usage period extension. use private key usage period extension.
For security discussion concerning use of algorithm parameters, see For security discussion concerning use of algorithm parameters, see
section Security Considerations from [CPALGS]. section Security Considerations from [CPALGS].
4 Appendix Examples 4 Appendix Examples
4.1 GOST R 34.10-94 Certificate 4.1 GOST R 34.10-94 Certificate
0 30 527: SEQUENCE { -----BEGIN CERTIFICATE-----
4 30 444: SEQUENCE { MIICCzCCAboCECMO42BGlSTOxwvklBgufuswCAYGKoUDAgIEMGkxHTAbBgNVBAMM
8 02 16: INTEGER FEdvc3RSMzQxMC05NCBleGFtcGxlMRIwEAYDVQQKDAlDcnlwdG9Qcm8xCzAJBgNV
: 17 31 2A C2 1B D2 08 58 BC 04 1E 52 37 D0 74 50 BAYTAlJVMScwJQYJKoZIhvcNAQkBFhhHb3N0UjM0MTAtOTRAZXhhbXBsZS5jb20w
26 30 10: SEQUENCE { HhcNMDUwODE2MTIzMjUwWhcNMTUwODE2MTIzMjUwWjBpMR0wGwYDVQQDDBRHb3N0
28 06 6: OBJECT IDENTIFIER UjM0MTAtOTQgZXhhbXBsZTESMBAGA1UECgwJQ3J5cHRvUHJvMQswCQYDVQQGEwJS
: id_GostR3411_94_with_GostR3410_94 VTEnMCUGCSqGSIb3DQEJARYYR29zdFIzNDEwLTk0QGV4YW1wbGUuY29tMIGlMBwG
: ( 1 2 643 2 2 4) BiqFAwICFDASBgcqhQMCAiACBgcqhQMCAh4BA4GEAASBgLuEZuF5nls02CyAfxOo
36 05 0: NULL GWZxV/6MVCUhR28wCyd3RpjG+0dVvrey85NsObVCNyaE4g0QiiQOHwxCTSs7ESuo
: } v2Y5MlyUi8Go/htjEvYJJYfMdRv05YmKCYJo01x3pg+2kBATjeM+fJyR1qwNCCw+
38 30 105: SEQUENCE { eMG1wra3Gqgqi0WBkzIydvp7MAgGBiqFAwICBANBABHHCH4S3ALxAiMpR3aPRyqB
40 31 29: SET { g1DjB8zy5DEjiULIc+HeIveF81W9lOxGkZxnrFjXBSqnjLeFKgF1hffXOAP7zUM=
42 30 27: SEQUENCE { -----END CERTIFICATE-----
44 06 3: OBJECT IDENTIFIER
: commonName (2 5 4 3)
49 0C 20: UTF8String 'GostR3410-94 example'
: }
: }
71 31 18: SET {
73 30 16: SEQUENCE {
75 06 3: OBJECT IDENTIFIER
: organizationName (2 5 4 10)
80 0C 9: UTF8String 'CryptoPro'
: }
: }
91 31 11: SET {
93 30 9: SEQUENCE {
95 06 3: OBJECT IDENTIFIER
: countryName (2 5 4 6)
100 13 2: PrintableString 'RU'
: }
: }
104 31 39: SET {
106 30 37: SEQUENCE {
108 06 9: OBJECT IDENTIFIER
: emailAddress (1 2 840 113549 1 9 1)
119 16 24: IA5String 'GostR3410-94@example.com'
: }
: }
: }
145 30 30: SEQUENCE {
147 17 13: UTCTime '050203151651Z'
162 17 13: UTCTime '150203151651Z'
: }
177 30 105: SEQUENCE {
179 31 29: SET {
181 30 27: SEQUENCE {
183 06 3: OBJECT IDENTIFIER
: commonName (2 5 4 3)
188 0C 20: UTF8String 'GostR3410-94 example'
: }
: }
210 31 18: SET {
212 30 16: SEQUENCE {
214 06 3: OBJECT IDENTIFIER
: organizationName (2 5 4 10)
219 0C 9: UTF8String 'CryptoPro'
: }
: }
230 31 11: SET {
232 30 9: SEQUENCE {
234 06 3: OBJECT IDENTIFIER
: countryName (2 5 4 6)
239 13 2: PrintableString 'RU'
: }
: }
243 31 39: SET {
245 30 37: SEQUENCE {
247 06 9: OBJECT IDENTIFIER
: emailAddress (1 2 840 113549 1 9 1)
258 16 24: IA5String 'GostR3410-94@example.com'
: }
: }
: }
284 30 165: SEQUENCE {
287 30 28: SEQUENCE {
289 06 6: OBJECT IDENTIFIER
: id_GostR3410_94 ( 1 2 643 2 2 20)
297 30 18: SEQUENCE { 0 30 523: SEQUENCE {
299 06 7: OBJECT IDENTIFIER 4 30 442: SEQUENCE {
: id_GostR3410_94_CryptoPro_A_ParamSet 8 02 16: INTEGER
: ( 1 2 643 2 2 32 2) : 23 0E E3 60 46 95 24 CE C7 0B E4 94 18 2E 7E EB
308 06 7: OBJECT IDENTIFIER 26 30 8: SEQUENCE {
: id_GostR3411_94_CryptoProParamSet 28 06 6: OBJECT IDENTIFIER
: ( 1 2 643 2 2 30 1) : id-GostR3411-94-with-GostR3410-94 (1 2 643 2 2 4)
: } : }
: } 36 30 105: SEQUENCE {
317 03 132: BIT STRING 0 unused bits, encapsulates { 38 31 29: SET {
321 04 128: OCTET STRING 40 30 27: SEQUENCE {
: BB 84 66 E1 79 9E 5B 34 D8 2C 80 7F 13 A8 19 66 42 06 3: OBJECT IDENTIFIER commonName (2 5 4 3)
: 71 57 FE 8C 54 25 21 47 6F 30 0B 27 77 46 98 C6 47 0C 20: UTF8String 'GostR3410-94 example'
: FB 47 55 BE B7 B2 F3 93 6C 39 B5 42 37 26 84 E2 : }
: 0D 10 8A 24 0E 1F 0C 42 4D 2B 3B 11 2B A8 BF 66
: 39 32 5C 94 8B C1 A8 FE 1B 63 12 F6 09 25 87 CC
: 75 1B F4 E5 89 8A 09 82 68 D3 5C 77 A6 0F B6 90
: 10 13 8D E3 3E 7C 9C 91 D6 AC 0D 08 2C 3E 78 C1
: B5 C2 B6 B7 1A A8 2A 8B 45 81 93 32 32 76 FA 7B
: }
: }
: } : }
452 30 10: SEQUENCE { 69 31 18: SET {
454 06 6: OBJECT IDENTIFIER 71 30 16: SEQUENCE {
: id_GostR3411_94_with_GostR3410_94 ( 1 2 643 2 2 4) 73 06 3: OBJECT IDENTIFIER organizationName (2 5 4 10)
462 05 0: NULL 78 0C 9: UTF8String 'CryptoPro'
: }
: } : }
464 03 65: BIT STRING 0 unused bits 89 31 11: SET {
: 71 28 D8 4E 9A 38 33 FE 2E 42 12 02 CE C8 AC B3 91 30 9: SEQUENCE {
: F6 91 46 90 37 1A CA 6B 16 61 05 95 BF B0 99 D2 93 06 3: OBJECT IDENTIFIER countryName (2 5 4 6)
: 94 CC F0 8C CC CE 45 01 5B 71 87 B1 48 C2 16 96 98 13 2: PrintableString 'RU'
: A7 15 90 DF 83 6C EE 37 ED E4 4F EE BD E2 7F 41 : }
: }
102 31 39: SET {
104 30 37: SEQUENCE {
106 06 9: OBJECT IDENTIFIER emailAddress (1 2 840 113549 1 9 1)
117 16 24: IA5String 'GostR3410-94@example.com'
: }
: }
: }
143 30 30: SEQUENCE {
145 17 13: UTCTime '050816123250Z'
160 17 13: UTCTime '150816123250Z'
: }
175 30 105: SEQUENCE {
177 31 29: SET {
179 30 27: SEQUENCE {
181 06 3: OBJECT IDENTIFIER commonName (2 5 4 3)
186 0C 20: UTF8String 'GostR3410-94 example'
: }
: }
208 31 18: SET {
210 30 16: SEQUENCE {
212 06 3: OBJECT IDENTIFIER organizationName (2 5 4 10)
217 0C 9: UTF8String 'CryptoPro'
: }
: }
228 31 11: SET {
230 30 9: SEQUENCE {
232 06 3: OBJECT IDENTIFIER countryName (2 5 4 6)
237 13 2: PrintableString 'RU'
: }
: }
241 31 39: SET {
243 30 37: SEQUENCE {
245 06 9: OBJECT IDENTIFIER emailAddress (1 2 840 113549 1 9 1)
256 16 24: IA5String 'GostR3410-94@example.com'
: }
: }
: }
282 30 165: SEQUENCE {
285 30 28: SEQUENCE {
287 06 6: OBJECT IDENTIFIER id-GostR3410-94 (1 2 643 2 2 20)
295 30 18: SEQUENCE {
297 06 7: OBJECT IDENTIFIER
: id-GostR3410-94-CryptoPro-A-ParamSet
: (1 2 643 2 2 32 2)
306 06 7: OBJECT IDENTIFIER
: id-GostR3411-94-CryptoProParamSet
: (1 2 643 2 2 30 1)
: }
: }
315 03 132: BIT STRING 0 unused bits, encapsulates {
319 04 128: OCTET STRING
: BB 84 66 E1 79 9E 5B 34 D8 2C 80 7F 13 A8 19 66
: 71 57 FE 8C 54 25 21 47 6F 30 0B 27 77 46 98 C6
: FB 47 55 BE B7 B2 F3 93 6C 39 B5 42 37 26 84 E2
: 0D 10 8A 24 0E 1F 0C 42 4D 2B 3B 11 2B A8 BF 66
: 39 32 5C 94 8B C1 A8 FE 1B 63 12 F6 09 25 87 CC
: 75 1B F4 E5 89 8A 09 82 68 D3 5C 77 A6 0F B6 90
: 10 13 8D E3 3E 7C 9C 91 D6 AC 0D 08 2C 3E 78 C1
: B5 C2 B6 B7 1A A8 2A 8B 45 81 93 32 32 76 FA 7B
: }
: }
: }
450 30 8: SEQUENCE {
452 06 6: OBJECT IDENTIFIER
: id-GostR3411-94-with-GostR3410-94 (1 2 643 2 2 4)
: } : }
460 03 65: BIT STRING 0 unused bits
: 11 C7 08 7E 12 DC 02 F1 02 23 29 47 76 8F 47 2A
: 81 83 50 E3 07 CC F2 E4 31 23 89 42 C8 73 E1 DE
: 22 F7 85 F3 55 BD 94 EC 46 91 9C 67 AC 58 D7 05
: 2A A7 8C B7 85 2A 01 75 85 F7 D7 38 03 FB CD 43
: }
In the signature of the above certificate, r' equals to
0x22F785F355BD94EC46919C67AC58D7052AA78CB7852A017585F7D73803FBCD43
and s equals to
0x11C7087E12DC02F102232947768F472A818350E307CCF2E431238942C873E1DE
4.2 GOST R 34.10-2001 Certificate 4.2 GOST R 34.10-2001 Certificate
0 30 468: SEQUENCE { -----BEGIN CERTIFICATE-----
4 30 385: SEQUENCE { MIIB0DCCAX8CECv1xh7CEb0Xx9zUYma0LiEwCAYGKoUDAgIDMG0xHzAdBgNVBAMM
8 02 16: INTEGER Fkdvc3RSMzQxMC0yMDAxIGV4YW1wbGUxEjAQBgNVBAoMCUNyeXB0b1BybzELMAkG
: 48 E9 54 A5 CF E9 69 F5 C9 5C F7 55 E7 83 41 AF A1UEBhMCUlUxKTAnBgkqhkiG9w0BCQEWGkdvc3RSMzQxMC0yMDAxQGV4YW1wbGUu
26 30 10: SEQUENCE { Y29tMB4XDTA1MDgxNjE0MTgyMFoXDTE1MDgxNjE0MTgyMFowbTEfMB0GA1UEAwwW
28 06 6: OBJECT IDENTIFIER R29zdFIzNDEwLTIwMDEgZXhhbXBsZTESMBAGA1UECgwJQ3J5cHRvUHJvMQswCQYD
: id_GostR3411_94_with_GostR3410_2001 VQQGEwJSVTEpMCcGCSqGSIb3DQEJARYaR29zdFIzNDEwLTIwMDFAZXhhbXBsZS5j
: ( 1 2 643 2 2 3) b20wYzAcBgYqhQMCAhMwEgYHKoUDAgIkAAYHKoUDAgIeAQNDAARAhJVodWACGkB1
36 05 0: NULL CM0TjDGJLP3lBQN6Q1z0bSsP508yfleP68wWuZWIA9CafIWuD+SN6qa7flbHy7Df
: } D2a8yuoaYDAIBgYqhQMCAgMDQQA8L8kJRLcnqeyn1en7U23Sw6pkfEQu3u0xFkVP
38 30 109: SEQUENCE { vFQ/3cHeF26NG+xxtZPz3TaTVXdoiYkXYiD02rEx1bUcM97i
40 31 31: SET { -----END CERTIFICATE-----
42 30 29: SEQUENCE {
44 06 3: OBJECT IDENTIFIER 0 30 464: SEQUENCE {
: commonName (2 5 4 3) 4 30 383: SEQUENCE {
49 0C 22: UTF8String 'GostR3410-2001 example' 8 02 16: INTEGER
: } : 2B F5 C6 1E C2 11 BD 17 C7 DC D4 62 66 B4 2E 21
: } 26 30 8: SEQUENCE {
73 31 18: SET { 28 06 6: OBJECT IDENTIFIER
75 30 16: SEQUENCE { : id-GostR3411-94-with-GostR3410-2001 (1 2 643 2 2 3)
77 06 3: OBJECT IDENTIFIER : }
: organizationName (2 5 4 10) 36 30 109: SEQUENCE {
82 0C 9: UTF8String 'CryptoPro' 38 31 31: SET {
: } 40 30 29: SEQUENCE {
: } 42 06 3: OBJECT IDENTIFIER commonName (2 5 4 3)
93 31 11: SET { 47 0C 22: UTF8String 'GostR3410-2001 example'
95 30 9: SEQUENCE { : }
97 06 3: OBJECT IDENTIFIER
: countryName (2 5 4 6)
102 13 2: PrintableString 'RU'
: }
: }
106 31 41: SET {
108 30 39: SEQUENCE {
110 06 9: OBJECT IDENTIFIER
: emailAddress (1 2 840 113549 1 9 1)
121 16 26: IA5String 'GostR3410-2001@example.com'
: }
: }
: }
149 30 30: SEQUENCE {
151 17 13: UTCTime '050203151646Z'
166 17 13: UTCTime '150203151646Z'
: }
181 30 109: SEQUENCE {
183 31 31: SET {
185 30 29: SEQUENCE {
187 06 3: OBJECT IDENTIFIER
: commonName (2 5 4 3)
192 0C 22: UTF8String 'GostR3410-2001 example'
: }
: }
216 31 18: SET {
218 30 16: SEQUENCE {
220 06 3: OBJECT IDENTIFIER
: organizationName (2 5 4 10)
225 0C 9: UTF8String 'CryptoPro'
: }
: }
236 31 11: SET {
238 30 9: SEQUENCE {
240 06 3: OBJECT IDENTIFIER
: countryName (2 5 4 6)
245 13 2: PrintableString 'RU'
: }
: }
249 31 41: SET {
251 30 39: SEQUENCE {
253 06 9: OBJECT IDENTIFIER
: emailAddress (1 2 840 113549 1 9 1)
264 16 26: IA5String 'GostR3410-2001@example.com'
: }
: }
: }
292 30 99: SEQUENCE {
294 30 28: SEQUENCE {
296 06 6: OBJECT IDENTIFIER
: id_GostR3410_2001 ( 1 2 643 2 2 19)
304 30 18: SEQUENCE {
306 06 7: OBJECT IDENTIFIER
: id_GostR3410_2001_CryptoPro_XchA_ParamSet
: ( 1 2 643 2 2 36 0)
315 06 7: OBJECT IDENTIFIER
: id_GostR3411_94_CryptoProParamSet
: ( 1 2 643 2 2 30 1)
: }
: }
324 03 67: BIT STRING 0 unused bits, encapsulates {
327 04 64: OCTET STRING
: 84 95 68 75 60 02 1A 40 75 08 CD 13 8C 31 89 2C
: FD E5 05 03 7A 43 5C F4 6D 2B 0F E7 4F 32 7E 57
: 8F EB CC 16 B9 95 88 03 D0 9A 7C 85 AE 0F E4 8D
: EA A6 BB 7E 56 C7 CB B0 DF 0F 66 BC CA EA 1A 60
: }
: }
: } : }
393 30 10: SEQUENCE { 71 31 18: SET {
395 06 6: OBJECT IDENTIFIER 73 30 16: SEQUENCE {
: id_GostR3411_94_with_GostR3410_2001 ( 1 2 643 2 2 3) 75 06 3: OBJECT IDENTIFIER organizationName (2 5 4 10)
403 05 0: NULL 80 0C 9: UTF8String 'CryptoPro'
: }
: } : }
405 03 65: BIT STRING 0 unused bits 91 31 11: SET {
: 1F 0E 5D C3 F6 B0 FC E8 8D BC 7C 8E 13 AE 64 BF 93 30 9: SEQUENCE {
: 2A 38 1E 9D 2C 7F 3D DC B0 CE 94 52 4A 75 D1 53 95 06 3: OBJECT IDENTIFIER countryName (2 5 4 6)
: B6 E3 BA 1F 34 92 B7 B6 C2 DB 1C E2 E3 51 AA B3 100 13 2: PrintableString 'RU'
: 79 FA E5 19 BD 75 5A 91 D8 AE F5 85 83 E1 5C 2C : }
: }
104 31 41: SET {
106 30 39: SEQUENCE {
108 06 9: OBJECT IDENTIFIER emailAddress (1 2 840 113549 1 9 1)
119 16 26: IA5String 'GostR3410-2001@example.com'
: }
: }
: }
147 30 30: SEQUENCE {
149 17 13: UTCTime '050816141820Z'
164 17 13: UTCTime '150816141820Z'
: }
179 30 109: SEQUENCE {
181 31 31: SET {
183 30 29: SEQUENCE {
185 06 3: OBJECT IDENTIFIER commonName (2 5 4 3)
190 0C 22: UTF8String 'GostR3410-2001 example'
: }
: }
214 31 18: SET {
216 30 16: SEQUENCE {
218 06 3: OBJECT IDENTIFIER organizationName (2 5 4 10)
223 0C 9: UTF8String 'CryptoPro'
: }
: }
234 31 11: SET {
236 30 9: SEQUENCE {
238 06 3: OBJECT IDENTIFIER countryName (2 5 4 6)
243 13 2: PrintableString 'RU'
: }
: }
247 31 41: SET {
249 30 39: SEQUENCE {
251 06 9: OBJECT IDENTIFIER emailAddress (1 2 840 113549 1 9 1)
262 16 26: IA5String 'GostR3410-2001@example.com'
: }
: }
: }
290 30 99: SEQUENCE {
292 30 28: SEQUENCE {
294 06 6: OBJECT IDENTIFIER id-GostR3410-2001 (1 2 643 2 2 19)
302 30 18: SEQUENCE {
304 06 7: OBJECT IDENTIFIER
: id-GostR3410-2001-CryptoPro-XchA-ParamSet
: (1 2 643 2 2 36 0)
313 06 7: OBJECT IDENTIFIER
: id-GostR3411-94-CryptoProParamSet
: (1 2 643 2 2 30 1)
: }
: }
322 03 67: BIT STRING 0 unused bits, encapsulates {
325 04 64: OCTET STRING
: 84 95 68 75 60 02 1A 40 75 08 CD 13 8C 31 89 2C
: FD E5 05 03 7A 43 5C F4 6D 2B 0F E7 4F 32 7E 57
: 8F EB CC 16 B9 95 88 03 D0 9A 7C 85 AE 0F E4 8D
: EA A6 BB 7E 56 C7 CB B0 DF 0F 66 BC CA EA 1A 60
: }
: }
: }
391 30 8: SEQUENCE {
393 06 6: OBJECT IDENTIFIER
: id-GostR3411-94-with-GostR3410-2001 (1 2 643 2 2 3)
: } : }
401 03 65: BIT STRING 0 unused bits
: 3C 2F C9 09 44 B7 27 A9 EC A7 D5 E9 FB 53 6D D2
: C3 AA 64 7C 44 2E DE ED 31 16 45 4F BC 54 3F DD
: C1 DE 17 6E 8D 1B EC 71 B5 93 F3 DD 36 93 55 77
: 68 89 89 17 62 20 F4 DA B1 31 D5 B5 1C 33 DE E2
: }
In the public key of the above certificate, x equals to
0x577E324FE70F2B6DF45C437A0305E5FD2C89318C13CD0875401A026075689584
and y equals to
0x601AEACABC660FDFB0CBC7567EBBA6EA8DE40FAE857C9AD0038895B916CCEB8F
In the signature of the above certificate, r' equals to
0xC1DE176E8D1BEC71B593F3DD36935577688989176220F4DAB131D5B51C33DEE2
and s equals to
0x3C2FC90944B727A9ECA7D5E9FB536DD2C3AA647C442EDEED3116454FBC543FDD
5 References 5 References
[GOST28147] "Cryptographic Protection for Data Processing Sys- Normative references:
tem", GOST 28147-89, Gosudarstvennyi Standard of
USSR, Government Committee of the USSR for Standards,
1989. (In Russian);
[GOSTR341094] "Information technology. Cryptographic Data Security. [GOST28147] "Cryptographic Protection for Data Processing System",
Produce and check procedures of Electronic Digital GOST 28147-89, Gosudarstvennyi Standard of USSR, Gov-
Signatures based on Asymmetric Cryptographic Algo- ernment Committee of the USSR for Standards, 1989. (In
rithm.", GOST R 34.10-94, Gosudarstvennyi Standard of Russian);
Russian Federation, Government Committee of the Rus-
sia for Standards, 1994. (In Russian);
[GOSTR34102001] "Information technology. Cryptographic data security. [GOSTR341094] "Information technology. Cryptographic Data Security.
Signature and verification processes of [electronic] Produce and check procedures of Electronic Digital Sig-
digital signature.", GOST R 34.10-2001, Gosudarstven- natures based on Asymmetric Cryptographic Algorithm.",
nyi Standard of Russian Federation, Government Com- GOST R 34.10-94, Gosudarstvennyi Standard of Russian
mittee of the Russia for Standards, 2001. (In Rus- Federation, Government Committee of the Russia for
sian); Standards, 1994. (In Russian);
[GOSTR341194] "Information technology. Cryptographic Data Security. [GOSTR341001] "Information technology. Cryptographic data security.
Hashing function.", GOST R 34.10-94, Gosudarstvennyi Signature and verification processes of [electronic]
Standard of Russian Federation, Government Committee digital signature.", GOST R 34.10-2001, Gosudarstvennyi
of the Russia for Standards, 1994. (In Russian); Standard of Russian Federation, Government Committee of
the Russia for Standards, 2001. (In Russian);
[RFDSL] Russian Federal Digital Signature Law, 10 Jan 2002 [GOSTR341194] "Information technology. Cryptographic Data Security.
N1-FZ Hashing function.", GOST R 34.10-94, Gosudarstvennyi
Standard of Russian Federation, Government Committee of
the Russia for Standards, 1994. (In Russian);
[CPALGS] "Additional cryptographic algorithms for use with [CPALGS] "Additional cryptographic algorithms for use with GOST
GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST
and GOST R 34.11-94 algorithms", V. Popov, I. Kurep- R 34.11-94 algorithms", V. Popov, I. Kurepkin, S. Leon-
kin, S. Leontiev, February 2004, draft-popov-crypto- tiev, September 2005, draft-popov-cryptopro-
pro-cpalgs-01.txt work in progress; cpalgs-04.txt work in progress;
[Schneier95] B. Schneier, Applied cryptography, second edition, [PROFILE] Housley, R., Polk, W., Ford, W. and D. Solo, "Inter-
John Wiley & Sons, Inc., 1995; net X.509 Public Key Infrastructure Certificate and
Certificate Revocation List (CRL) Profile", RFC 3280,
April 2002.
[RFC3280] Housley, R., Polk, W., Ford, W. and D. Solo, [PKALGS] L. Bassham, W. Polk, R. Housley, "Algorithms and
"Internet X.509 Public Key Infrastructure Certificate Identifiers for the Internet X.509 Public Key Infras-
and Certificate Revocation List (CRL) Profile", RFC tructure Certificate and Certificate Revocation List
3280, April 2002. (CRL) Profile", RFC 3279, April 2002.
[RFC3279] Algorithms and Identifiers for the Internet X.509 [X.660] ITU-T Recommendation X.660 Information Technology -
Public Key Infrastructure Certificate and Certificate ASN.1 encoding rules: Specification of Basic Encoding
Revocation List (CRL) Profile. L. Bassham, W. Rules (BER), Canonical Encoding Rules (CER) and Distin-
Polk, R. Housley. April 2002. guished Encoding Rules (DER), 1997.
[RFC2119] Bradner, S., "Key Words for Use in RFCs to Indicate Informative references:
Requirement Levels", BCP 14, RFC 2119, March 1997.
[TLS] The TLS Protocol Version 1.0. T. Dierks, C. Allen. [Schneier95] B. Schneier, Applied cryptography, second edition, John
January 1999, RFC 2246. Wiley & Sons, Inc., 1995;
[X.660] ITU-T Recommendation X.660 Information Technology - [RFDSL] Russian Federal Digital Signature Law, 10 Jan 2002
ASN.1 encoding rules: Specification of Basic Encoding N1-FZ
Rules (BER), Canonical Encoding Rules (CER) and Dis-
tinguished Encoding Rules (DER), 1997. [RFC2119] Bradner, S., "Key Words for Use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[CMS] Housley, R., "Cryptographic Message Syntax (CMS)", RFC
3852, July 2004.
Acknowledgments Acknowledgments
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-TC, MD PREI, Infotecs GmbH, SPRCIS (SPbRCZI), CRYPTO-PRO, Factor-TS, MD PREI, Infotecs GmbH, SPRCIS (SPbRCZI),
Cryptocom, R-Alpha. The goal of this agreement is to achieve mutual Cryptocom, R-Alpha. The goal 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 provided information about Microsoft Corporation Russia for provided 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 colaboration and RSA Security Russia and Demos Co Ltd for active colaboration and
skipping to change at page 18, line 7 skipping to change at page 17, line 5
RSA Security Inc for compatibility testing of the proposed data RSA Security Inc for compatibility testing of the proposed data
formats while incorporating them into RSA Keon product. formats while incorporating them into RSA Keon product.
Baltimore Technology plc for compatibility testing of the proposed Baltimore Technology plc for compatibility testing of the proposed
data formats while incorporating them into UniCERT product. data formats while incorporating them into UniCERT product.
Russ Hously (Vigil Security, LLC, housley@vigilsec.com) and Russ Hously (Vigil Security, LLC, housley@vigilsec.com) and
Vasilij Sakharov (DEMOS Co Ltd, svp@dol.ru) for initiative Vasilij Sakharov (DEMOS Co Ltd, svp@dol.ru) for initiative
creating this document. creating this document.
Grigorij Chudov for navigating the IETF process for this document.
This document is based on a contribution of CRYPTO-PRO company. Any This document is based on a contribution of CRYPTO-PRO company. Any
substantial use of the text from this document must reference CRYPTO- substantial use of the text from this document must reference CRYPTO-
PRO. CRYPTO-PRO requests that all material mentioning or referencing PRO. CRYPTO-PRO requests that all material mentioning or referencing
this document identify this as "CRYPTO-PRO CPPK". this document identify this as "CRYPTO-PRO CPPK".
Author's Addresses Author's Addresses
Serguei Leontiev Serguei Leontiev
CRYPTO-PRO CRYPTO-PRO
38, Obraztsova, 38, Obraztsova,
Moscow, 127018, Russian Federation Moscow, 127018, Russian Federation
EMail: lse@cryptopro.ru EMail: lse@cryptopro.ru
Dennis Shefanovski Dennis Shefanovski
DEMOS Co Ltd DEMOS Co Ltd
6/1, Ovchinnikovskaja naberezhnaya, 6/1, Ovchinnikovskaja naberezhnaya,
Moscow, 113035, Russian Federation Moscow, 113035, Russian Federation
EMail: sdb@dol.ru EMail: sdb@dol.ru
Grigorij Chudov
CRYPTO-PRO
38, Obraztsova,
Moscow, 127018, Russian Federation
EMail: chudov@cryptopro.ru
Alexandr Afanasiev Alexandr Afanasiev
Factor-TC Factor-TS
office 711, 14, Presnenskij val, office 711, 14, Presnenskij val,
Moscow, 123557, Russian Federation Moscow, 123557, Russian Federation
EMail: aaaf@factor-ts.ru EMail: afa1@factor-ts.ru
Nikolaj Nikishin Nikolaj Nikishin
Infotecs GmbH Infotecs GmbH
p/b 35, 80-5, Leningradskij prospekt, p/b 35, 80-5, Leningradskij prospekt,
Moscow, 125315, Russian Federation Moscow, 125315, Russian Federation
EMail: nikishin@infotecs.ru EMail: nikishin@infotecs.ru
Boleslav Izotov Boleslav Izotov
FGUE STC "Atlas" FGUE STC "Atlas"
38, Obraztsova, 38, Obraztsova,
Moscow, 127018, Russian Federation Moscow, 127018, Russian Federation
EMail: izotov@stcnet.ru EMail: izotov@nii.voskhod.ru
Elena Minaeva Elena Minaeva
MD PREI MD PREI
build 3, 6A, Vtoroj Troitskij per., build 3, 6A, Vtoroj Troitskij per.,
Moscow, Russian Federation Moscow, Russian Federation
EMail: evminaeva@mo.msk.ru EMail: evminaeva@mail.ru
Serguei Murugov Serguei Murugov
R-Alpha R-Alpha
4/1, Raspletina, 4/1, Raspletina,
Moscow, 123060, Russian Federation Moscow, 123060, Russian Federation
EMail: msm@office.ru EMail: msm@top-cross.ru
Igori Ustinov Igor Ustinov
Cryptocom Cryptocom
office 239, 51, Leninskij prospekt, office 239, 51, Leninskij prospekt,
Moscow, 119991, Russian Federation Moscow, 119991, Russian Federation
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
Full Copyright Statement Disclaimer of Validity
Copyright (C) The Internet Society (2005). 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 (2005). 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.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 99 change blocks. 
541 lines changed or deleted 504 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/