CryptoPro CSP Packages — Customer-Provided

This directory is a placeholder for customer-provided CryptoPro CSP binaries.

Why Are Binaries Not Included?

CryptoPro CSP is commercial software licensed per-deployment by CryptoPro LLC (crypto-pro.ru). StellaOps cannot redistribute these binaries due to licensing restrictions.

Distribution Model:

• StellaOps ships: Plugin interface code (BUSL-1.1) + documentation
• Customer provides: Licensed CryptoPro CSP binaries + EULA acceptance

How to Obtain CryptoPro CSP

1. Visit CryptoPro Downloads

2. Purchase an appropriate license for your deployment

3. Download the package bundle for your target architecture:

   • linux-amd64_deb.tgz — Intel/AMD 64-bit (most common)
   • linux-arm64_deb.tgz — ARM 64-bit
   • linux-armhf_deb.tgz — ARM hard float (32-bit)
   • linux-ia32.tgz — Legacy 32-bit x86
   • linux-e2k*_deb.tgz — MCST Elbrus architectures
   • linux-riscv64_deb.tgz — RISC-V 64-bit

4. Place the .tgz file in this directory

Installation

After placing your licensed bundle here:

# Set the EULA acceptance flag (only if you agree to CryptoPro's EULA)
export CRYPTOPRO_ACCEPT_EULA=1

# Run the installer script
./devops/services/cryptopro/install-linux-csp.sh

The installer will:

• Auto-detect your host architecture
• Extract the appropriate bundle
• Install minimal required packages (CSP core + PKCS#11)

Plugin Initialization

Without valid CSP binaries installed, the CryptoPro plugin will NOT initialize.

The plugin performs runtime checks for CSP availability. If CSP is not installed or not licensed, the plugin will:

1. Log a warning about missing CSP
2. Return null from ICryptoProvider resolution
3. Fall back to alternative providers (if configured)

Environment Variables

Licensing Reference

• Product: CryptoPro CSP 5.0
• Vendor: CRYPTO-PRO LLC
• License: Commercial (per-deployment, ~$50-200 USD per instance)
• EULA: Presented during installation; must be accepted by customer

For licensing questions, contact CryptoPro directly: https://cryptopro.ru/contacts

This file was generated during compliance cleanup on 2025-12-26. See docs/legal/crypto-compliance-review.md for full licensing analysis.