key119 B

SAMPLE Ed25519 Private Key — PKCS#8

The Ed25519 key behind the Ed25519 leaf and the EdDSA JWTs, in PKCS#8. RFC 8410 keys have no traditional-OpenSSL container at all, which is why only one serialisation ships.

Certificate & key testing

Preview — first 4 lineskey

-----BEGIN PRIVATE KEY-----
MC4CAQAwBQYDK2VwBCIEIN47NSfFR2syxqNYEqnMQm0EAHrmjYu+B0+0GsbHz9gl
-----END PRIVATE KEY-----

Specifications

Algorithm: Ed25519
Container: PKCS#8
Armour: BEGIN PRIVATE KEY
Bytes: 119
Encrypted: false
Derivation: SHA-256 of a fixed label as the 32-byte seed
Sample Only: true
Seed: 70117

Testing contract

Expected to pass

Scenario: Load the key and sign the p7 EdDSA JWT signing input with it.
Expected result: The produced signature is byte-identical to the one in the shipped EdDSA JWT fixture.

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

“SAMPLE Ed25519 Private Key — PKCS#8” 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 70117 · Ed25519. 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.