Detached Signature, ASCII Armor: SAMPLE Shape
An ASCII-armored detached signature block of the shape that accompanies a SHA256SUMS file. It is a SAMPLE placeholder, not a valid OpenPGP signature: armor detectors will find it, verifiers must reject it. Signatures, key ids and certificates here are SAMPLE placeholders: the base64 decodes to the words 'SAMPLE SIGNATURE', so verification must fail. Nothing here is cryptographically valid and no key material is real.
# Signatures, key ids and certificates here are SAMPLE placeholders — the base64 decodes to the words 'SAMPLE SIGNATURE', so verification must fail. Nothing here is cryptographically valid and no key material is real.
-----BEGIN PGP SIGNATURE-----
Comment: SAMPLE detached signature — not a real OpenPGP signature
U0FNUExFIFNJR05BVFVSRSAtIE5PVCBBIFJFQUwgU0lHTkFUVVJFLCBWRVJJRklDQVRJT04gTVVTVCBGQUlMIFtkZXRhY2hlZC0xXQ==
U0FNUExFIFNJR05BVFVSRSAtIE5PVCBBIFJFQUwgU0lHTkFUVVJFLCBWRVJJRklDQVRJT04gTVVTVCBGQUlMIFtkZXRhY2hlZC0yXQ==
=SMPL
-----END PGP SIGNATURE-----
Specifications
- Seed
- 51200
- Sample Only
- true
- Format
- ASCII armor placeholder
- Armor Type
- PGP SIGNATURE
- Cryptographically Valid
- false
- Note
- served as .txt so it previews inline
- Line Endings
- LF
Testing contract
Expected to fail- Scenario
- Detect an armored signature block and attempt verification.
- Expected result
- The armor headers and =SMPL checksum line are recognised, and verification fails with a bad-signature error rather than an unhandled exception.
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
“Detached Signature, ASCII Armor: SAMPLE Shape” is a deterministic Testaroo fixture for Config parsing, Certificate & key testing, Error handling. TOML and INI configuration files with nested sections and typed values, for testing config parsers and loaders.
Documented properties for this file: seed 51200 · LF · ASCII armor placeholder. 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.
SBOM, lockfile, provenance, and advisory fixtures describe the same fabricated component tree across formats, so a converter or scanner can be diffed against a known answer. Every package name, version, hash, and advisory ID is invented, never treat a finding here as real.
Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.
Generated by generation/supply_chain.py. Free for any use, no attribution required, license.
Related files
- txtRelease SHA256SUMS ManifestThe oldest supply-chain artifact there is: a sha256sum manifest with the exact two-space separator the tool emits, listing a fictional release tarball and its nine dependency archives. Every package, version, hash and licence is fictional: the tree describes nothing real.
- lockCargo.lock, Truncated: Intentionally CorruptAn intentionally corrupt Cargo.lock: a valid version 4 lockfile cut off inside a [[package]] table so the final key/value pair is incomplete. Small on purpose. Every package, version, hash and licence is fictional: the tree describes nothing real.
- lockGemfile.lock (Bundler)A Bundler lockfile in its indentation-significant block format: specs nested under GEM, transitive requirements nested one level deeper, and the BUNDLED WITH version on its own indented line. Every package, version, hash and licence is fictional: the tree describes nothing real.
- txtgo.sum Checksum Lines (as .txt)go.sum content: two h1: lines per fictional module (one for the module zip and one for its go.mod), which is the pairing a verifier must require. Served as .txt because go.sum has no registered media type. Every package, version, hash and licence is fictional: the tree describes nothing real.
- lockmix.lock (Elixir)An Elixir mix.lock: a literal Elixir map whose values are tuples of atoms, strings and lists. It is neither JSON nor TOML, so a generic lockfile reader has to special-case it. Every package, version, hash and licence is fictional: the tree describes nothing real.
- spdxSPDX 2.3 Minimal SBOM (Tag-Value)An SPDX 2.3 tag-value document with only the mandatory document header and a single fictional package (no relationships, no files) for testing that a parser accepts a document with every optional block absent. Every package, version, hash and licence is fictional: the tree describes nothing real.
