feat(crypto): Complete Phase 2 - Configuration-driven crypto architecture with 100% compliance
## Summary
This commit completes Phase 2 of the configuration-driven crypto architecture, achieving
100% crypto compliance by eliminating all hardcoded cryptographic implementations.
## Key Changes
### Phase 1: Plugin Loader Infrastructure
- **Plugin Discovery System**: Created StellaOps.Cryptography.PluginLoader with manifest-based loading
- **Configuration Model**: Added CryptoPluginConfiguration with regional profiles support
- **Dependency Injection**: Extended DI to support plugin-based crypto provider registration
- **Regional Configs**: Created appsettings.crypto.{international,russia,eu,china}.yaml
- **CI Workflow**: Added .gitea/workflows/crypto-compliance.yml for audit enforcement
### Phase 2: Code Refactoring
- **API Extension**: Added ICryptoProvider.CreateEphemeralVerifier for verification-only scenarios
- **Plugin Implementation**: Created OfflineVerificationCryptoProvider with ephemeral verifier support
- Supports ES256/384/512, RS256/384/512, PS256/384/512
- SubjectPublicKeyInfo (SPKI) public key format
- **100% Compliance**: Refactored DsseVerifier to remove all BouncyCastle cryptographic usage
- **Unit Tests**: Created OfflineVerificationProviderTests with 39 passing tests
- **Documentation**: Created comprehensive security guide at docs/security/offline-verification-crypto-provider.md
- **Audit Infrastructure**: Created scripts/audit-crypto-usage.ps1 for static analysis
### Testing Infrastructure (TestKit)
- **Determinism Gate**: Created DeterminismGate for reproducibility validation
- **Test Fixtures**: Added PostgresFixture and ValkeyFixture using Testcontainers
- **Traits System**: Implemented test lane attributes for parallel CI execution
- **JSON Assertions**: Added CanonicalJsonAssert for deterministic JSON comparisons
- **Test Lanes**: Created test-lanes.yml workflow for parallel test execution
### Documentation
- **Architecture**: Created CRYPTO_CONFIGURATION_DRIVEN_ARCHITECTURE.md master plan
- **Sprint Tracking**: Created SPRINT_1000_0007_0002_crypto_refactoring.md (COMPLETE)
- **API Documentation**: Updated docs2/cli/crypto-plugins.md and crypto.md
- **Testing Strategy**: Created testing strategy documents in docs/implplan/SPRINT_5100_0007_*
## Compliance & Testing
- ✅ Zero direct System.Security.Cryptography usage in production code
- ✅ All crypto operations go through ICryptoProvider abstraction
- ✅ 39/39 unit tests passing for OfflineVerificationCryptoProvider
- ✅ Build successful (AirGap, Crypto plugin, DI infrastructure)
- ✅ Audit script validates crypto boundaries
## Files Modified
**Core Crypto Infrastructure:**
- src/__Libraries/StellaOps.Cryptography/CryptoProvider.cs (API extension)
- src/__Libraries/StellaOps.Cryptography/CryptoSigningKey.cs (verification-only constructor)
- src/__Libraries/StellaOps.Cryptography/EcdsaSigner.cs (fixed ephemeral verifier)
**Plugin Implementation:**
- src/__Libraries/StellaOps.Cryptography.Plugin.OfflineVerification/ (new)
- src/__Libraries/StellaOps.Cryptography.PluginLoader/ (new)
**Production Code Refactoring:**
- src/AirGap/StellaOps.AirGap.Importer/Validation/DsseVerifier.cs (100% compliant)
**Tests:**
- src/__Libraries/__Tests/StellaOps.Cryptography.Plugin.OfflineVerification.Tests/ (new, 39 tests)
- src/__Libraries/__Tests/StellaOps.Cryptography.PluginLoader.Tests/ (new)
**Configuration:**
- etc/crypto-plugins-manifest.json (plugin registry)
- etc/appsettings.crypto.*.yaml (regional profiles)
**Documentation:**
- docs/security/offline-verification-crypto-provider.md (600+ lines)
- docs/implplan/CRYPTO_CONFIGURATION_DRIVEN_ARCHITECTURE.md (master plan)
- docs/implplan/SPRINT_1000_0007_0002_crypto_refactoring.md (Phase 2 complete)
## Next Steps
Phase 3: Docker & CI/CD Integration
- Create multi-stage Dockerfiles with all plugins
- Build regional Docker Compose files
- Implement runtime configuration selection
- Add deployment validation scripts
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
master
105
etc/appsettings.crypto.china.yaml
Normal file
105
etc/appsettings.crypto.china.yaml
Normal file
@@ -0,0 +1,105 @@
|
||||
# StellaOps Cryptography Configuration - China Profile (SM)
|
||||
# This configuration enforces SM2/SM3/SM4 (ShangMi) cryptographic standards
|
||||
# for People's Republic of China deployments requiring OSCCA compliance.
|
||||
|
||||
StellaOps:
|
||||
Crypto:
|
||||
Plugins:
|
||||
# Path to the plugin manifest JSON file
|
||||
ManifestPath: "/etc/stellaops/crypto-plugins-manifest.json"
|
||||
|
||||
# Discovery mode: "explicit" (only load configured plugins) or "auto" (load all compatible)
|
||||
# Production deployments should use "explicit" for security
|
||||
DiscoveryMode: "explicit"
|
||||
|
||||
# List of enabled plugins with optional priority and configuration overrides
|
||||
Enabled:
|
||||
# SM software provider (primary)
|
||||
- Id: "sm.soft"
|
||||
Priority: 100
|
||||
Options: {}
|
||||
|
||||
# SM remote HSM provider (for hardware-backed operations)
|
||||
- Id: "sm.remote"
|
||||
Priority: 90
|
||||
Options:
|
||||
baseAddress: "http://sm-hsm.internal:8900"
|
||||
timeout: 30000
|
||||
retryCount: 3
|
||||
|
||||
# CRITICAL: Disable ALL non-SM providers
|
||||
Disabled:
|
||||
- "default" # Standard .NET crypto (SHA-256, ECDSA)
|
||||
- "libsodium" # Ed25519, XChaCha20-Poly1305
|
||||
- "openssl.gost" # Russian GOST
|
||||
- "pkcs11.gost"
|
||||
- "cryptopro.gost"
|
||||
- "wine.csp"
|
||||
- "eidas.*" # European eIDAS
|
||||
- "fips.*" # FIPS 140-3
|
||||
- "pq.*" # Post-quantum
|
||||
- "sim.*" # Simulation providers
|
||||
|
||||
# Fail application startup if SM provider cannot be loaded
|
||||
FailOnMissingPlugin: true
|
||||
|
||||
# Require at least one SM provider
|
||||
RequireAtLeastOne: true
|
||||
|
||||
Compliance:
|
||||
# Compliance profile: SM (ShangMi - Commercial Cipher)
|
||||
ProfileId: "sm"
|
||||
|
||||
# CRITICAL: Enable strict validation
|
||||
# This will REJECT any signature/hash algorithm that is not SM-compliant
|
||||
StrictValidation: true
|
||||
|
||||
# Enforce jurisdiction filtering
|
||||
EnforceJurisdiction: true
|
||||
|
||||
# Only allow Chinese jurisdiction plugins
|
||||
AllowedJurisdictions:
|
||||
- "china"
|
||||
|
||||
# Canonical algorithms (SM2 signature, SM3 hash, SM4 encryption)
|
||||
HashAlgorithm: "SM3"
|
||||
SignatureAlgorithm: "SM2"
|
||||
SymmetricAlgorithm: "SM4"
|
||||
|
||||
# Enable warnings for any non-SM algorithm attempts
|
||||
WarnOnWeakAlgorithms: true
|
||||
|
||||
# SM Algorithm Overview (GM/T standards):
|
||||
# - SM2: Public key cryptography (similar to ECDSA, uses 256-bit curve)
|
||||
# Standard: GM/T 0003-2012
|
||||
# - SM3: Cryptographic hash function (256-bit output, similar to SHA-256)
|
||||
# Standard: GM/T 0004-2012
|
||||
# - SM4: Block cipher (128-bit key, 128-bit block, similar to AES)
|
||||
# Standard: GM/T 0002-2012
|
||||
# - SM9: Identity-based cryptography
|
||||
# Standard: GM/T 0044-2016
|
||||
|
||||
# OSCCA (Office of State Commercial Cryptography Administration) Compliance:
|
||||
# - All cryptographic operations MUST use SM algorithms
|
||||
# - Hardware Security Modules (HSMs) MUST be OSCCA-certified
|
||||
# - Certificates MUST comply with GM/T 0015 (Certificate Profile)
|
||||
|
||||
# Optional: SM remote HSM configuration
|
||||
# Crypto:
|
||||
# SmRemote:
|
||||
# # Base URL of SM-compliant HSM service
|
||||
# BaseAddress: "https://sm-hsm.example.com:8900"
|
||||
# # API authentication token
|
||||
# ApiKey: "${SM_HSM_API_KEY}"
|
||||
# # Connection timeout (ms)
|
||||
# Timeout: 30000
|
||||
# # Enable TLS client certificate authentication
|
||||
# ClientCertificatePath: "/etc/stellaops/certs/sm-client.pfx"
|
||||
# ClientCertificatePassword: "${SM_CLIENT_CERT_PASSWORD}"
|
||||
|
||||
# Optional: Override default provider preferences
|
||||
# Crypto:
|
||||
# Registry:
|
||||
# PreferredProviders:
|
||||
# - "sm.soft"
|
||||
# - "sm.remote"
|
||||
Reference in New Issue
Block a user