key1.6 KB

SAMPLE RSA Private Key — PKCS#1, Unencrypted

The identical key material wrapped in the legacy PKCS#1 container (BEGIN RSA PRIVATE KEY), which omits the algorithm OID that PKCS#8 carries. Diff it against its PKCS#8 twin to see exactly what a container migration changes.

Certificate & key testing Conversion testing

Preview — first 28 lineskey

Specifications

Algorithm: RSA
Bits: 2048
Container: PKCS#1 (traditional OpenSSL)
Armour: BEGIN RSA PRIVATE KEY
Encrypted: false
Note: same key material as the PKCS#8 twin, different container
Sample Only: true
Seed: 70117

Testing contract

Expected to pass

Scenario: Load both this key and its PKCS#8 twin and compare their RSA private numbers.
Expected result: Both containers yield identical modulus, exponents, and primes despite different PEM armour.

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 RSA Private Key — PKCS#1, Unencrypted” is a deterministic Novus Examples fixture for Certificate & key testing, Conversion 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 · RSA. 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.