Ed25519 Private Key (PEM) — SAMPLE
Deterministic SAMPLE Ed25519 private key for SSH/TLS tooling tests.
-----BEGIN PRIVATE KEY-----
MC4CAQAwBQYDK2VwBCIEIJ4wPHCocX8jQQjyvFsitoUfR3NY73LbaZg4a1IM8vfV
-----END PRIVATE KEY-----
Specifications
- Algorithm
- Ed25519
- Format
- PKCS#8 PEM
- Sample Only
- true
- Seed
- 47001
Testing contract
Expected to pass- Scenario
- Exercise Ed25519 Private Key (PEM) — SAMPLE in its pki workflow. Deterministic SAMPLE Ed25519 private key for SSH/TLS tooling tests.
- Expected result
- 3 text lines, decoded as UTF-8; first nonempty line is '-----BEGIN PRIVATE KEY-----'. Declared feature checks: algorithm=Ed25519.
What is a .key file?
A .key file holds a private key, usually PEM-encoded in PKCS#8 (BEGIN PRIVATE KEY) or a key-type-specific format. It is the secret half of a TLS or SSH identity and must normally be protected. The examples here are published, sample-only keys that must never be used in production.
How to use this file
Use an example .key to test PEM key parsers, PKCS#8 decoders, and key-format converters (for example PEM to DER or OpenSSH). These are deliberately published sample keys, for parser testing only, never for real use.
How to use this file for testing
“Ed25519 Private Key (PEM) — SAMPLE” is a deterministic Novus Examples fixture for Certificate & key testing. Self-signed X.509 certificates (PEM, CRT, DER), a CSR, RSA and Ed25519 keys, an SSH public key, a PKCS#12 bundle, and an htpasswd file, all published sample-only material, for testing certificate parsers, TLS tooling, keystore importers, and PEM/DER decoders.
Documented properties for this file: seed 47001 · Ed25519 · PKCS#8 PEM. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
This is published, SAMPLE-only security material, never a real secret. Point certificate, key, or token parsers at it, test PEM/DER decoding and PKCS handling, and confirm your tooling reads the documented fields; any sample password is printed on this page.
This is a published, sample-only certificate/key. Parse it, verify the chain or signature, and test PEM↔DER conversion, never deploy it anywhere real.
Related files
- jsonCRL Metadata JSON — SAMPLESAMPLE CRL metadata JSON (no binary CRL) for revocation-list UI and loader tests.
- keyEncrypted PKCS#8 RSA Key — SAMPLEPassword-encrypted SAMPLE PKCS#8 private key (password printed in specs) for decrypt-import tests.
- csrPKCS#10 CSR — Security SAMPLEPKCS#10 certificate signing request SAMPLE for CSR parsers and CA tooling smoke tests.
- p12PKCS#12 Bundle (.p12) — SAMPLESAMPLE PKCS#12 keystore (password `novus-sample-wg`) for keystore importer tests. Not byte-stable.
- pemSAMPLE CA Bundle — Root + IntermediateThe two CA certificates concatenated in trust-store order, the shape a `--cafile` or `ca-bundle.crt` argument expects. Point a client at this and every other valid p7 leaf becomes verifiable.
- pemSAMPLE Certificate Revocation List — EmptyA correctly signed CRL with an absent revokedCertificates field — what a CA publishes when it has revoked nothing. Parsers that assume the list is always present tend to fault here rather than report zero entries.
Generated by generation/security_wave_g.py. Free for any use, no attribution required, license.