stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

feat(crypto): Complete Phase 2 - Configuration-driven crypto architecture with 100% compliance

Browse Source 
## 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
2025-12-23 18:20:00 +02:00
parent b444284be5
commit dac8e10e36
241 changed files with 22567 additions and 307 deletions
Download Patch File Download Diff File Expand all files Collapse all files

174
src/__Libraries/StellaOps.TestKit/README.md Normal file
View File

@@ -0,0 +1,174 @@
# StellaOps.TestKit
Test infrastructure and fixtures for StellaOps projects. Provides deterministic time/random, canonical JSON assertions, snapshot testing, database fixtures, and OpenTelemetry capture.
## Features
### Deterministic Time
```csharp
using StellaOps.TestKit.Time;
// Create a clock at a fixed time
var clock = new DeterministicClock();
var now = clock.UtcNow; // 2025-01-01T00:00:00Z
// Advance time
clock.Advance(TimeSpan.FromMinutes(5));
// Or use helpers
var clock2 = DeterministicClockExtensions.AtTestEpoch();
var clock3 = DeterministicClockExtensions.At("2025-06-15T10:30:00Z");
```
### Deterministic Random
```csharp
using StellaOps.TestKit.Random;
// Create deterministic RNG with standard test seed (42)
var rng = DeterministicRandomExtensions.WithTestSeed();
// Generate reproducible values
var number = rng.Next(1, 100);
var text = rng.NextString(10);
var item = rng.PickOne(new[] { "a", "b", "c" });
```
### Canonical JSON Assertions
```csharp
using StellaOps.TestKit.Json;
// Assert JSON equality (ignores formatting)
CanonicalJsonAssert.Equal(expectedJson, actualJson);
// Assert object equivalence
CanonicalJsonAssert.EquivalentObjects(expectedObj, actualObj);
// Hash-based regression testing
var hash = CanonicalJsonAssert.ComputeHash(json);
CanonicalJsonAssert.MatchesHash("abc123...", json);
```
### Snapshot Testing
```csharp
using StellaOps.TestKit.Snapshots;
public class MyTests
{
[Fact]
public void TestOutput()
{
var output = GenerateSomeOutput();
// Compare against __snapshots__/test_output.txt
var snapshotPath = SnapshotHelper.GetSnapshotPath("test_output");
SnapshotHelper.VerifySnapshot(output, snapshotPath);
}
[Fact]
public void TestJsonOutput()
{
var obj = new { Name = "test", Value = 42 };
// Compare JSON serialization
var snapshotPath = SnapshotHelper.GetSnapshotPath("test_json", ".json");
SnapshotHelper.VerifyJsonSnapshot(obj, snapshotPath);
}
}
// Update snapshots: set environment variable UPDATE_SNAPSHOTS=1
```
### PostgreSQL Fixture
```csharp
using StellaOps.TestKit.Fixtures;
using Xunit;
[Collection("Postgres")]
public class DatabaseTests
{
private readonly PostgresFixture _postgres;
public DatabaseTests(PostgresFixture postgres)
{
_postgres = postgres;
}
[Fact]
public async Task TestQuery()
{
// Use connection string
await using var conn = new Npgsql.NpgsqlConnection(_postgres.ConnectionString);
await conn.OpenAsync();
// Execute SQL
await _postgres.ExecuteSqlAsync("CREATE TABLE test (id INT)");
// Create additional databases
await _postgres.CreateDatabaseAsync("otherdb");
}
}
```
### Valkey/Redis Fixture
```csharp
using StellaOps.TestKit.Fixtures;
using Xunit;
[Collection("Valkey")]
public class CacheTests
{
private readonly ValkeyFixture _valkey;
public CacheTests(ValkeyFixture valkey)
{
_valkey = valkey;
}
[Fact]
public void TestCache()
{
var connectionString = _valkey.ConnectionString;
// Use with your Redis/Valkey client
}
}
```
### OpenTelemetry Capture
```csharp
using StellaOps.TestKit.Telemetry;
[Fact]
public void TestTracing()
{
using var otel = new OTelCapture("my-service");
// Code that emits traces
using (var activity = otel.ActivitySource.StartActivity("operation"))
{
activity?.SetTag("key", "value");
}
// Assert traces
otel.AssertActivityExists("operation");
otel.AssertActivityHasTag("operation", "key", "value");
// Get summary for debugging
Console.WriteLine(otel.GetTraceSummary());
}
```
## Usage in Tests
Add to your test project:
```xml
<ItemGroup>
<ProjectReference Include="..\..\__Libraries\StellaOps.TestKit\StellaOps.TestKit.csproj" />
</ItemGroup>
```
## Design Principles
- **Determinism**: All utilities produce reproducible results
- **Offline-first**: No network dependencies (uses Testcontainers for local infrastructure)
- **Minimal dependencies**: Only essential packages
- **xUnit-friendly**: Works seamlessly with xUnit fixtures and collections