OpenPGP messages and keys are often sent as ASCII armor (RFC 4880): a cleartext block with headers, Base64 body (76-character lines), and a CRC-24 checksum line starting with =.
-----BEGIN PGP MESSAGE-----
…
(Base64 body, 76-char lines)
=XXXX
-----END PGP MESSAGE-----The Base64 alphabet matches standard RFC 4648 (+ / with = padding). The extras are framing and the CRC, not a different alphabet.
Versus MIME Base64
| MIME (RFC 2045) | OpenPGP armor | |
|---|---|---|
| Line length | ≤ 76 | ≤ 76 |
| Headers | MIME Content-Transfer-Encoding | BEGIN / END armor |
| Checksum | none | CRC-24 (=XXXX) |
Developer tips
- Never treat armored text as encryption by itself—the armor is packaging; OpenPGP encryption is separate.
- Strip headers before feeding the body to a generic decoder, or use a tool that understands armor.
- Our encoder/decoder supports the OpenPGP ASCII armor standard for body encode/decode workflows; use the detector if you are unsure which wrapping you have.
댓글 (0)
“OpenPGP ASCII armor”에 대한 질문, 아이디어, 버그가 있으신가요? 댓글을 남기거나 도구를 평가하거나 다른 사람에게 답글을 달아 주세요.
아직 댓글이 없습니다. 첫 번째로 의견을 남겨 주세요!