/crypto.pgp
Configure your PGP armor for Kerberos — generation, import, verification, and encrypted communication.
/why.pgp
Kerberos relies on PGP to bind messages, onion mirrors, and vendor identities to cryptographic proof. PGP does not hide traffic, but it ensures that the data you receive has not been altered and truly originates from a holder of the Kerberos private key. Without PGP verification, users are exposed to phishing panels, cloned login screens, and malicious support impersonation.
/kerberos.fingerprint
Use the following fingerprint when importing or verifying the official Kerberos public key:
Match all segments exactly; if any group differs, treat the key as compromised and do not proceed.
/public.key.block
You can also copy the full public key block from this section and import it into your local keychain. Always compare the fingerprint after import.
/generate.keypair
To interact with Kerberos in a privacy‑preserving way, generate a dedicated PGP keypair used only for this darknet identity. Do not reuse keys from clearnet email or professional contexts. Use a strong passphrase and store any backups offline.
CLI (GnuPG)
Run gpg --full-generate-key, select RSA‑4096 or ECC, set expiry (e.g. 1 year), and choose a pseudonymous name and email.
GUI Clients
On desktop systems you can use tools like Kleopatra or other OpenPGP frontends, as long as they operate locally and do not sync to cloud.
Backup
Export a revocation certificate and store it offline so you can revoke the key in case of compromise or device failure.
/encrypt.messages
Once you have imported the Kerberos public key and generated your own, you can encrypt messages so that only the intended recipient can read them. Always sign your messages with your private key, and encrypt to the Kerberos key. This combination provides both authenticity and confidentiality.
- Use
gpg --encrypt --sign --recipient "Kerberos"to protect outgoing messages. - Verify signatures of incoming messages before trusting any payment or link instructions.
- Never paste decrypted content into web forms outside of Tor or into logging text editors.
/verify.signatures
PGP verification is the main defense against phishing within the Kerberos darknet ecosystem. Market announcements, mirror rotations, and emergency bulletins should always include a detached signature or a signed message body. If a message claims to be from Kerberos but fails verification, treat it as malicious until proven otherwise.
Detached
Use gpg --verify file.asc file.txt to match the signature against the content. Any failure means the file was tampered with or not signed by Kerberos.
Inline
For armored inline messages, use gpg --verify directly. Ensure the fingerprint shown matches the Kerberos fingerprint above.