txt294 B

SAMPLE Detached Signature Payload

The exact bytes covered by the detached PKCS#7 signature shipped beside it. LF line endings are part of the contract — rewriting the file with CRLF is the fastest way to watch a signature check fail for a reason nobody suspects.

Certificate & key testing

Preview — first 6 linestxt

Novus Examples SAMPLE signed payload
-------------------------------------
This file is the detached-signature subject for the p7 PKCS#7 fixture.
Its bytes are fixed: any edit, including a newline change, invalidates the signature.
Signer: CN=leaf.pki.sample.example (SAMPLE), serial 0x701001.

Specifications

Encoding: UTF-8
Line Endings: LF
Bytes: 294
Signed By: the p7 PKCS#7 detached signature
Sample Only: true
Seed: 70117

Testing contract

Reference control

Scenario: Verify the detached signature against this file, then against a CRLF-converted copy.
Expected result: Verification succeeds on the original bytes and fails on the CRLF copy, proving the check is byte-exact.

What is a .txt file?

TXT is a plain-text file containing unformatted character data with no styling or structure beyond line breaks. Its interpretation depends on character encoding, most commonly UTF-8, and on line-ending convention. It is the most universal and portable text container.

How to use this file

Use an example TXT to test encoding detection, line-ending (LF versus CRLF) handling, and any tool that reads or streams raw text input.

How to use this file for testing

“SAMPLE Detached Signature Payload” 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 · UTF-8 · LF. 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.