Skip to content
Testaroo
pub102 B

SSH Public Key (Ed25519)

An OpenSSH-format Ed25519 public key (the shareable half of the key pair): a single line of algorithm, Base64 key blob, and comment, for testing SSH public-key parsers and authorized_keys tooling.

Preview, first 2 linespub
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAOhB7/zzhC+HXDdGOdLwJln5NYwm6UNXx3chmQSVTG4 novus-sample@example

Specifications

Format
OpenSSH public key
Algorithm
ssh-ed25519
Comment
novus-sample@example
Sample Only
true

Testing contract

Expected to pass
Scenario
Exercise SSH Public Key (Ed25519) in its security workflow. An OpenSSH-format Ed25519 public key (the shareable half of the key pair): a single line of algorithm, Base64 key blob, and comment, for testing SSH public-key parsers and authorized_keys tooling.
Expected result
1 text lines, decoded as UTF-8; first nonempty line is 'ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAOhB7/zzhC+HXDdGOdLwJln5NYwm6UNXx3chmQSVTG4 novus-sample@example'. Declared feature checks: algorithm=ssh-ed25519; comment=novus-sample@example.

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

“SSH Public Key (Ed25519)” is a deterministic Testaroo fixture for Certificate & key testing, Editor 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: ssh-ed25519 · 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.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

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.

Generated by generation/pki_security.py. Free for any use, no attribution required, license.