26 30 8: SEQUENCE {
28 06 6: OBJECT IDENTIFIER
: id-GostR3411-94-with-GostR3410-2001 (1 2 643 2 2 3)
: }
36 30 109: SEQUENCE {
38 31 31: SET {
40 30 29: SEQUENCE {
42 06 3: OBJECT IDENTIFIER commonName (2 5 4 3)
47 0C 22: UTF8String ’GostR3410-2001 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 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
0x577E324FE70F2B6DF45C437A0305E5FD2C89318C13CD0875401A026075689584
and y equals
0x601AEACABC660FDFB0CBC7567EBBA6EA8DE40FAE857C9AD0038895B916CCEB8F
The corresponding private key d equals
0x0B293BE050D0082BDAE785631A6BAB68F35B42786D6DDA56AFAF169891040F77
In the signature of the above certificate, r equals
0xC1DE176E8D1BEC71B593F3DD36935577688989176220F4DAB131D5B51C33DEE2
and s equals
0x3C2FC90944B727A9ECA7D5E9FB536DD2C3AA647C442EDEED3116454FBC543FDD
5. Acknowledgements
This document was created in accordance with "Russian Cryptographic
Software Compatibility Agreement", signed by FGUE STC "Atlas",
CRYPTO-PRO, Factor-TS, MD PREI, Infotecs GmbH, SPRCIS (SPbRCZI),
Cryptocom, R-Alpha. The goal of this agreement is to achieve mutual
compatibility of the products and solutions.
The authors wish to thank the following:
Microsoft Corporation Russia for providing information about
company products and solutions, and also for technical consulting
in PKI.
RSA Security Russia and Demos Co Ltd for active collaboration and
critical help in creation of this document.
RSA Security Inc for compatibility testing of the proposed data
formats while incorporating them into the RSA Keon product.
Baltimore Technology plc for compatibility testing of the proposed
data formats while incorporating them into their UniCERT product.
Peter Gutmann for his helpful "dumpasn1" program.
Russ Housley (Vigil Security, LLC, housley@vigilsec.com) and
Vasilij Sakharov (DEMOS Co Ltd, svp@dol.ru) for encouraging the
authors to create this document.
Grigorij Chudov for navigating the IETF process for 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.
6. References
6.1. Normative References
[GOST28147] "Cryptographic Protection for Data Processing System",
GOST 28147-89, Gosudarstvennyi Standard of USSR,
Government Committee of the USSR for Standards, 1989.
(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.
Produce and check procedures of Electronic Digital
Signatures based on Asymmetric Cryptographic
Algorithm.", GOST R 34.10-94, Gosudarstvennyi Standard
of Russian Federation, Government Committee of the
Russia for Standards, 1994. (In Russian)
[GOSTR341001] "Information technology. Cryptographic data security.
Signature and verification processes of [electronic]
digital signature.", GOST R 34.10-2001, Gosudarstvennyi
Standard of Russian Federation, Government Committee of
the Russia for Standards, 2001. (In Russian)
[GOSTR341194] "Information technology. Cryptographic Data Security.
Hashing function.", GOST R 34.10-94, Gosudarstvennyi
Standard of Russian Federation, Government Committee of
the Russia for Standards, 1994. (In Russian)
[CPALGS] Popov, V., Kurepkin, I., and S. Leontiev, "Additional
Cryptographic Algorithms for Use with GOST 28147-89,
GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94
Algorithms", RFC 4357, January 2006.
[PKALGS] Bassham, L., Polk, W., and R. Housley, "Algorithms and
Identifiers for the Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation
List (CRL) Profile", RFC 3279, April 2002.
[PROFILE] Housley, R., Polk, W., Ford, W., and D. Solo, "Internet
X.509 Public Key Infrastructure Certificate and
Certificate Revocation List (CRL) Profile", RFC 3280,
April 2002.
[X.660] ITU-T Recommendation X.660 Information Technology -
ASN.1 encoding rules: Specification of Basic Encoding
Rules (BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER), 1997.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
6.2. Informative References
[Schneier95] B. Schneier, Applied Cryptography, Second Edition, John
Wiley & Sons, Inc., 1995.
[RFEDSL] Russian Federal Electronic Digital Signature Law, 10
Jan 2002 N 1-FZ.
[CMS] Housley, R., "Cryptographic Message Syntax (CMS)", RFC
3852, July 2004.
Authors’ Addresses
Serguei Leontiev, Ed.
CRYPTO-PRO
38, Obraztsova,
Moscow, 127018, Russian Federation
EMail: lse@cryptopro.ru
Dennis Shefanovski, Ed.
Mobile TeleSystems OJSC
4, Marksistskaya Str.,
Moscow, 109147, Russian Federation
EMail: dbs@mts.ru
Grigorij Chudov
CRYPTO-PRO
38, Obraztsova,
Moscow, 127018, Russian Federation
EMail: chudov@cryptopro.ru
Alexandr Afanasiev
Factor-TS
office 711, 14, Presnenskij val,
Moscow, 123557, Russian Federation
EMail: afa1@factor-ts.ru
Nikolaj Nikishin
Infotecs GmbH
p/b 35, 80-5, Leningradskij prospekt,
Moscow, 125315, Russian Federation
EMail: nikishin@infotecs.ru
Boleslav Izotov
FGUE STC "Atlas"
38, Obraztsova,
Moscow, 127018, Russian Federation
EMail: izotov@nii.voskhod.ru
Elena Minaeva
MD PREI
build 3, 6A, Vtoroj Troitskij per.,
Moscow, Russian Federation
EMail: evminaeva@mail.ru
Igor Ovcharenko
MD PREI
Office 600, 14, B.Novodmitrovskaya,
Moscow, Russian Federation
EMail: igori@mo.msk.ru
Serguei Murugov
R-Alpha
4/1, Raspletina,
Moscow, 123060, Russian Federation
EMail: msm@top-cross.ru
Igor Ustinov
Cryptocom
office 239, 51, Leninskij prospekt,
Moscow, 119991, Russian Federation
EMail: igus@cryptocom.ru
Anatolij Erkin
SPRCIS (SPbRCZI)
1, Obrucheva,
St.Petersburg, 195220, Russian Federation
EMail: erkin@nevsky.net
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
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
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
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).