ASC

Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.

PGP Armored Preview.

At a glance


Purpose	An ASCII-armoured OpenPGP file (.asc): a public or private key block, a signature, or a message.
Extensions	`.asc`
Poka parser	`poka-pgp-armored`
Viewer	`poka-tree-viewer`
Depth tier	Parser with a shared viewer (see Depth tiers)
Breadth tier	B3 Core (see Breadth tiers)

How much Poka reads

B3 Core. Only the main content type or types are decoded (for example geometry but not materials, layers or annotations, or only one version family). The list of gaps is substantial.

Confidence: medium (the reviewer read the code). Basis: Reviewed 2026-10-26: read parsers/poka-pgp-armored/src/main.rs (943 lines) and plugin.json. No unit tests or tests/samples.rs; the corpus has spark-wallet_SHA256SUMS.asc, read by no test. Covers .asc and .gpg-armored. The tree reads every armour block (type, headers, CRC-24), decodes the Base64 body and walks the OpenPGP packets: public and secret keys (algorithm, size or curve, version, creation, key ID, fingerprint), user IDs and signatures (type), with a packet list. Judgement: B3: keys and user IDs, the main content of key files, are decoded; messages are only walked.

What Poka does not read

Messages are not decrypted or decompressed: literal and compressed data are listed as packets only
Signature subpackets (expiry, preferences, issuer) are not decoded and signatures are not verified
Subkey binding and revocation status are not evaluated
User attributes (photo IDs) are not shown
Caps of 200 packets and 50 user IDs

Libraries

Libraries Poka uses or has assessed for this format, with the status, licence and language the registry records.

pem (candidate; MIT; Rust; https://github.com/jcreekmore/pem-rs) — PGP armored path

Sources

parsers/poka-pgp-armored/src/main.rs
parsers/poka-pgp-armored/plugin.json