1. Cryptopro For Mac Pro
2. Cryptopro For Mac Computers

Aug 27, 2020 CryptoPro CSP is a cryptographic software package which implements the Russian cryptographic algorithms developed in accordance with the Microsoft – Cryptographic Service Provider (CSP) interface. To achieve near complete integration with Windows applications, it injects itself into appropriate processes to enforce the use of its algorithms. I honestly don't know why you'd rate with one star when in the description it says it currently is only for BTC, ETH and LTC. And what's more, I have work on this project for a lot of hours, and the app is totally free, so I think you could have suggested me adding more coins while still rating it with 3 stars to be more kind if you do like the speed/features/interface of the app. Free to try Tension Software Mac OS X 10.4 Intel/PPC, Mac OS X 10.5 Intel/PPC Version 1.4.2 Full Specs. Download Now Secure Download. Publisher's Description. From Tension Software. CryptoPro CAdES Browser plug-in. First, you need to download the installation file and install it following this Manual. For distributive and its installation manual, go to link 1. Download the installation program. For CryptoPro CAdES Browser plug-in, go to link 2. Run cadesplugin.exe file. Confirm the installation of CryptoPro CAdES.

GOST 28147-89 Cipher Suites for Transport Layer Security (TLS)
draft-chudov-cryptopro-cptls-04

This document is intended to register new cipher suites for the Transport Layer Security (TLS) protocol, according to the procedure specified in TLS Protocol standards. These cipher suites are based on Russian national cryptographic standards - GOST R 34.10-94 and GOST R 34.10-2001 public keys, GOST 28147-89 encryption algorithm and GOST R 34.11-94 digest algorithm.

This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http:/⁠/⁠datatracker.ietf.org/⁠drafts/⁠current/⁠.

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.'

This Internet-Draft will expire on June 02, 2009.

Copyright (c) 2008 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http:/⁠/⁠trustee.ietf.org/⁠license-⁠info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.

• 1. Introduction
• 2. CipherSuite Definitions
• 2.1. Key Exchange
• 2.2. PRF, Signature and Hash
• 2.3. Cipher and MAC
• 3. Data Structures and Computations
• 3.1. Algorithms
• 3.2. Keys Calculation
• 3.3. Server Certificate
• 3.4. Server Key Exchange
• 3.5. Certificate Request
• 3.6. Client Key Exchange Message
• 3.7. Certificate Verify
• 3.8. Finished
• 4. Compatibility
• 5. Security Considerations
• 6. IANA Considerations
• 7. References
• 7.1. Normative references
• 7.2. Informative references
• Appendix A. ASN.1 Modules
• Appendix A.1. Gost-CryptoPro-TLS
• Appendix B. Acknowledgments

This document proposes the addition of new cipher suites to the Transport Layer Security (TLS) protocol to support GOST R 34.11-94 digest, GOST 28147-89 encryption and VKO GOST R 34.10-94/2001 key exchange algorithms. The cipher suites defined here were proposed by CRYPTO-PRO Company for the 'Russian Cryptographic Software Compatibility Agreement' community.

Algorithms GOST R 34.10-94, GOST R 34.10-2001, GOST 28147-89 and GOST R 34.11-94 have been developed by Russian Federal Agency of Governmental Communication and Information (FAGCI) and 'All-Russian Scientific and Research Institute of Standardization'. They are described in [GOSTR341094], [GOSTR341001], [GOSTR341194] and [GOST28147] ([GOST3431095], [GOST3431004], [GOST3431195]). Algorithms VKO GOST R 34.10-94/2001 and PRF_GOSTR3411 are described in [CPALGS].

This document defines two configurations:

• anonymous client - authenticated server (only server provides a certificate);
• authenticated client - authenticated server (client and server exchange certificates).

The presentation language used here is the same as in [TLS1.2]. Since this specification extends [TLS1.2], these descriptions should be merged with those in the TLS specification and any others that extend TLS. This means, that enum types may not specify all possible values and structures with multiple formats chosen with a select() clause may not indicate all possible cases.

The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT','SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in [RFC2119].

The cipher suites defined here use the following key exchange algorithms:

Key derivation algorithms based on GOST R 34.10-94 and GOST R 34.10-2001 public keys (VKO GOST R 34.10-94, VKO GOST R 34.10-2001) are described in [CPALGS].

The cipher suites described here use HMAC and TLS PRF, as described in section 5 of [TLS1.2], based on GOST R 34.11-94 hash function (HMAC_GOSTR3411 and PRF_GOSTR3411), with parameter set identified by id-GostR3411-94-CryptoProParamSet (refer to [CPALGS]). The same PRF MUST be used for all dependent protocols, such as [EAP-TLS].

GOST R 34.10-94/2001 signature is used for CertificateVerify message.

GOST R 34.11 digest algorithm ([GOSTR341194]) is used for CertificateVerify.signature.gostR3411_hash and Finished.verify_data (see sections 7.4.10 and 7.4.11 of [TLS1.2])

The following cipher algorithm and MAC functions are used (for details refer to Section 3.1):

For all four cipher suites, the use of MAC is slighttly different from the one, described in section 6.2.3.1 of [TLS1.2] for standard stream ciphers, where MAC is calculated from the following data:

Cipher suites defined in this document use the same input for first record, but for each consequent record the input from all previous records is concatenated:

GOST 28147-89 [GOST28147] uses 256-bit key size and 8-byte IV. Cipher suites, defined here, use GOST 28147-89 as a stream cipher in counter mode with S-box parameter from id-Gost28147-89-CryptoPro-A-ParamSet (see [CPALGS]) and CryptoPro key meshing algorithm.

IMIT_GOST28147 is GOST 28147-89 [GOST28147] in 'IMITOVSTAVKA' mode (4 bytes)

Key calculation is done according to section 6.3 of [TLS1.2], using PRF_GOSTR3411. The parameters are as follows:

Length of necessary key material is 144 bytes.

For these cipher suites this message is required and it MUST contain a certificate, with a public key algorithm matching ServerHello.cipher_suite.

This message MUST NOT be used in these cipher suites, because all the parameters necessary are present in server certificate (see [CPPK]).

This message is used as described in section 7.4.4 of [TLS1.2], and extended as follows:

gostr341094 and gostr34102001 certificate types identify that the server accepts GOST R 34.10-94 and GOST R 34.10-2001 public key certificates.

gostr3411 hash type identifes that the server accepts GOST R 34.11-94 hash function. It is RECOMMENDED to populate CertificateRequest.certificate_hash only with gostr3411 value, when one of the cipher suites described in this document is chosen.

The server SHOULD populate supported_signature_algorithm field with SignatureAndHashAlgorithm pairs, where HashAlgorithm equals gostr3411 and SignatureAlgorithm matches corresponding ClientCertificateType.

This message is used as described in section 7.4.7 of [TLS1.2], it is required for these suites, and contains DER-encoded TLSGostKeyTransportBlob structure [X.660].

ASN1-syntax for this structure is:

GostR3410-KeyTransport is defined in [CPCMS].

keyBlob.transportParameters MUST be present.

keyBlob.transportParameters.ephemeralPublicKey MUST be present if the server didn't request client certificate or client's public key algorithm and parameters do not match those of the recipient. Else it SHOULD be omited.

proxyKeyBlobs - (optional) contains key exchange for secondary recipients (for example, for the firewall, which audits connections).

cert - contains secondary recipient's certificate.

Actions of client:

First, the client generates a random 32-byte premaster_secret.

Then shared_ukm is calculated as first 8 bytes of digest of concatenated client random and server random:

Then client chooses a sender key. If keyBlob.transportParameters.ephemeralPublicKey is present, the corresponding secret key MUST be used as a sender key. If it is missing, the secret key, corresponding to the client certificate MUST be used.

Using the sender key and recipient's public key, algorithm VKO GOST R 34.10-94 or VKO GOST R 34.10-2001 (described in [CPALGS]) is applied to produce KEK. VKO GOST R 34.10-2001 is used with shared_ukm as UKM.

Then CryptoPro Key Wrap algorithm is applied to encrypt premaster_secret and produce CEK_ENC and CEK_MAC. Again, shared_ukm is used as UKM. keyBlob.transportParameters.encryptionParamSet is used for all encryption operations.

The resulting encrypted key (CEK_ENC) is placed in keyBlob.sessionEncryptedKey.encryptedKey field, it's mac (CEK_MAC) is placed in keyBlob.sessionEncryptedKey.macKey field, and shared_ukm (UKM) is placed in keyBlob.transportParameters.ukm field.

Actions of server:

Server MUST verify, that keyBlob.transportParameters.ukm is equal to GOSTR3411(client_random|server_random)[0..7], before decrypting the premaster_secret.

Server applies VKO GOST R 34.10-94 or VKO GOST R 34.10-2001, (depending on the client public key type), and CryptoPro Key Unwrap algorithm in the simillar manner to decrypt the premaster_secret.

Server MUST verify keyBlob.sessionEncryptedKey.macKey after decrypting the premaster_secret.

This message is used as described in section 7.4.8 of [TLS1.2]. If the client have sent both a client certificate and an ephemeral public key, it MUST send a certificate verify message, as a proof of possession of the private key for provided certificate.

The TLS structures are extended as follows:

This message is used as described in section 7.4.9 of [TLS1.2].

For historical reasons, some applications use the cipher suites specified herein with [TLS1.0], using some features of [TLS1.2], including cipher-suite dependent PRF, Finished and Certificate Verify computations.

It is RECOMMENDED that software applications verify signature values, subject public keys and algorithm parameters to conform to [GOSTR341001], [GOSTR341094] standards prior to their use.

Use of the same key for signature and key derivation is NOT RECOMMENDED.

It is RECOMMENDED for both client and server to verify the private key usage period, if this extension is present in the certificate.

The cipher suites TLS_GOSTR341094_WITH_28147_CNT_IMIT and TLS_GOSTR341001_WITH_28147_CNT_IMIT proposed hereby, have been analyzed by special certification laboratory of Scientific and Technical Centre 'ATLAS' in appropriate levels of target_of_evaluation (TOE).

It is RECOMMENDED to subject the implementations of these cipher suites to examination by an authorized agency with approved methods of cryptographic analysis.

This document defines the following new cipher suites, whose values presented here are used by several implementations of the same cipher suites for TLS 1.0, and were described in previous drafts. They are currently listed in the registry as reserved. IANA is requested to update the TLS Cipher Suite registry defined in [RFC5246] with these values.

Cryptopro For Mac Pro

This document defines the following new client certificate types, whose values presented here are used by several implementations of the same suites for TLS 1.0, and were described in previous drafts. They are currently listed in the registry as reserved. IANA is requested to update the TLS ClientCertificateType Identifiers Registry defined in [RFC5246] with these values.

This document defines the following new signature algorithm types, whose values are to be assigned from the TLS SignatureAlgorithm Registry defined in [RFC5246].

This document defines the following new hash algorithm types, whose values are to be assigned from the TLS HashAlgorithm Registry defined in [RFC5246].

Additional ASN.1 modules, referenced here, can be found in [CPALGS] and [CPCMS].

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 aim of this agreement is to achieve mutual compatibility of the products and solutions.

The authors wish to thank:

Cryptopro For Mac Computers

• Microsoft Corporation Russia for provided information about company products and solutions, and also for technical consulting in PKI.
• RSA Security Russia and Demos Co Ltd for active colaboration and critical help in creation of this document.
• NIP Informzachita for compatibility testing of the proposed data formats while incorporating them into company products.
• Citrix Inc for help in compatibility testing Citrix products for Microsoft Windows.
• Russ Hously (Vigil Security, LLC, housley@vigilsec.com) and Vasilij Sakharov (DEMOS Co Ltd, svp@dol.ru) for initiative, creating this document.

Author's Addresses