SAMPLE PKCS#12 Keystore — No Password
The same leaf key and certificate in a PKCS#12 file with no password and no encryption. Several importers refuse an empty password, prompt anyway, or treat it as the literal empty string, so this is the fixture that finds out which.
| Field | Value |
|---|---|
| Type | PKCS#12 / PFX keystore (binary) |
| Password | none — unencrypted |
| Private key | RSA-2048, leaf.pki.sample.example |
| Certificate | leaf.pki.sample.example 0x701001 |
| CA certificates | none |
| Bytes | 2908 |
Specifications
- Format
- PKCS#12 (PFX)
- Password
- (none)
- Encryption
- none
- Contains
- RSA-2048 leaf key + leaf certificate
- Pinned
- PKCS#12 MAC salt is per-run random, so these bytes are pinned in the generator
- Sample Only
- true
- Seed
- 70117
Testing contract
Expected to pass- Scenario
- Import the keystore supplying no password, then supply an empty string.
- Expected result
- Both attempts load the same key and certificate; the importer neither prompts nor rejects the file for a missing password.
What is a .p12 file?
A .p12 file is a PKCS#12 (PFX) bundle — a password-protected binary archive that packages a certificate together with its private key (and optionally a chain) in one importable file. It is the standard way to move a complete TLS or client identity between systems.
How to use this file
Use an example .p12 to test PKCS#12 parsers and importers, keystore tooling, and password-protected bundle handling. The sample password is documented on the file's page; this is published sample material, not a real identity.
How to use this file for testing
“SAMPLE PKCS#12 Keystore — No Password” is a deterministic Novus Examples fixture for Certificate & key testing, Error handling. 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 · PKCS#12 (PFX). 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
- 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.
- pemSAMPLE Certificate Revocation List — StaleA validly signed CRL whose nextUpdate passed in 2020. Whether a client hard-fails, soft-fails, or silently trusts stale revocation data is a real policy decision, and this is the fixture that reveals which one it made.
- csrSAMPLE CSR — Intentionally Corrupt Base64An intentionally corrupt PKCS#10 request: the PEM armour is intact but four illegal characters have been substituted into the Base64 body, so decoding fails part-way. It exists to check that a CSR intake path reports a parse error instead of a stack trace or a partially populated record.
- pemSAMPLE Leaf Certificate — ExpiredA correctly signed leaf whose notAfter fell in the past (2020). The only thing wrong with it is the clock, which makes it the clean way to assert that an expiry error is reported as expiry and not as a signature failure.
- pemSAMPLE Leaf Certificate — No SAN ExtensionA pre-RFC 6125-style certificate carrying only a Common Name and no subjectAltName extension. Every current browser and most TLS libraries reject it outright, which makes it a precise legacy-compatibility probe.
- pemSAMPLE Leaf Certificate — Not Yet ValidThe mirror of the expired leaf: identical in every respect except that notBefore is 2035, so it is rejected from the other side of the validity window. Pairs with it to prove a verifier distinguishes the two clock errors.
Generated by generation/security_p7.py. Free for any use, no attribution required — license.