mirror of https://github.com/SHOGGOTH-SECTOR/sica-fondt.git synced 2026-08-01 08:30:20 +00:00

Consolidate 22 sibling repos into layered organism structure

Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):

- brain/        LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
                dispatch, A51 channels, and the OSINT cluster
- knowledge/    LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
                MITRE ATT&CK data
- reference/    defensive threat-reference (C3, shhbruh doc) + AdaYaml parser

License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.

Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.

https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c

2026-06-10 06:53:01 +00:00

3.4 KiB

Raw Blame History

name

description

domain

subdomain

Implementing RSA Key Pair Management

Overview

RSA (Rivest-Shamir-Adleman) is the most widely deployed asymmetric cryptographic algorithm, used for digital signatures, key exchange, and encryption. This skill covers generating, storing, rotating, and managing RSA key pairs following NIST SP 800-57 key management guidelines, including key serialization formats (PEM, DER, PKCS#8), passphrase protection, and key strength validation.

When to Use

When deploying or configuring implementing rsa key pair management capabilities in your environment
When establishing security controls aligned to compliance requirements
When building or improving security architecture for this domain
When conducting security assessments that require this implementation

Prerequisites

Familiarity with cryptography concepts and tools
Access to a test or lab environment for safe execution
Python 3.8+ with required dependencies installed
Appropriate authorization for any testing activities

Objectives

Generate RSA key pairs with appropriate key sizes (2048, 3072, 4096 bits)
Serialize keys in PEM and DER formats with PKCS#8
Protect private keys with strong passphrase encryption
Implement key rotation with versioning
Extract public key components and fingerprints
Validate key strength and detect weak keys
Sign and verify data using RSA-PSS

Key Concepts

RSA Key Sizes and Security Strength

Key Size (bits)	Security Strength (bits)	Recommended Until
2048	112	2030
3072	128	Beyond 2030
4096	~140	Beyond 2030

RSA Padding Schemes

Scheme	Use Case	Standard
OAEP	Encryption	PKCS#1 v2.2 (RFC 8017)
PSS	Signatures	PKCS#1 v2.2 (RFC 8017)
PKCS#1 v1.5	Legacy only	Deprecated for new systems

Key Storage Formats

PEM: Base64-encoded with headers, human-readable
DER: Binary ASN.1 encoding, compact
PKCS#8: Standard for private key encapsulation
PKCS#12/PFX: Bundled key + certificate, password-protected

Security Considerations

Minimum 3072-bit keys for new deployments (NIST recommendation)
Always protect private keys with AES-256-CBC passphrase encryption
Use RSA-PSS for signatures (not PKCS#1 v1.5)
Use RSA-OAEP for encryption (not PKCS#1 v1.5)
Store private keys with restrictive file permissions (0600)
Implement key rotation at least annually

Validation Criteria

Key generation produces valid RSA key pair
Public key can be extracted from private key
Private key is protected with passphrase
RSA-PSS signature verification succeeds
Tampered signature verification fails
Key fingerprint is computed correctly
Key rotation maintains old key access for verification

3.4 KiB Raw Blame History