Name: Exit Protocol
Author: Exit Protocol

How to Use the Published OpenPGP Key

Operational guide for encrypting a message body or file and checking an explicit OpenPGP signature. Fingerprint comparison is a key reference, not organizational identity certification.

Rotated 2026-06-25: encrypt only to the active fingerprint on this page. The prior compromised key fingerprint 7C6B C2FE A871 2A59 38D9 BD9C B41D AFF8 AE70 0CAB is revoked and must not be used for new encryption. Its published public material and revocation certificate cannot decrypt ciphertext.

Protocol A: Encrypting Data

Import the public key

Download the .asc key from the public key page and import it into GPG, Kleopatra, GPG Suite, or another OpenPGP client.

Encrypt the file or message

Select the material you need to protect and encrypt it to support@exitprotocols.com using the published Exit Protocol key.

Transmit only the encrypted output

Send the resulting .gpg or .pgp file through the agreed intake path. Keep the unencrypted source file out of ordinary email.

Protocol B: Checking an OpenPGP Signature

Locate the signed material

Signed releases or security notices may include an OpenPGP signature block or a detached .sig file.

Run verification

Use your PGP client to verify the message or detached signature against the published public key.

Confirm fingerprint and source

A valid result only shows that the corresponding private key signed the checked bytes. Compare the full fingerprint and independently confirm the sender and authority; this is not PKI identity certification.

Terminal Operations

Import via curl

$ curl https://exitprotocols.com/pgp.asc | gpg --import
$ gpg --fingerprint E517B8153F556DD3

Encrypt a report $ gpg --encrypt --recipient C832474F32FE014415B9DD06E517B8153F556DD3 data.pdf