pub192 B

SAMPLE OpenSSH Public Key — ECDSA P-256

The P-256 public key in OpenSSH form, whose blob names the curve twice — once in the key type and once inside the payload. Parsers that read only one of the two mis-handle mismatched keys.

Certificate & key testing

Preview — first 2 linespub

ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBFvg0bZA8+Cnw4FJPHg9MXW/lK0a5f3IoklsCdO7l+yJ9IE+5maLT4yN/XTTwuR2AEjeuENKSTwGqGGqhmQli+E= novus-p7-sample@sample.example

Specifications

Format: OpenSSH public key
Algorithm: ecdsa-sha2-nistp256
Curve: P-256
Comment: novus-p7-sample@sample.example
Sample Only: true
Seed: 70117

Testing contract

Expected to pass

Scenario: Parse the line and read back the key type and the curve name embedded in the key blob.
Expected result: Both report nistp256, and the point matches the EC public key PEM shipped beside it.

What is a .pub file?

A .pub file holds an SSH public key in the single-line OpenSSH format — an algorithm name (such as ssh-ed25519), a Base64-encoded key blob, and an optional comment. It is the shareable half of an SSH key pair, added to a server's authorized_keys to grant access.

How to use this file

Use an example .pub to test SSH public-key parsers, authorized_keys tooling, and key-format converters, or to verify fingerprint computation. Sample key material only.

How to use this file for testing

“SAMPLE OpenSSH Public Key — ECDSA P-256” 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 · ecdsa-sha2-nistp256 · OpenSSH public key. 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.