Text Operations

GpgFrontend is a user-friendly graphical interface for GnuPG that simplifies the core cryptographic operations: encryption, decryption, signing, and verification. It supports secure communication through public key cryptography and provides intuitive workflows for both beginners and advanced users.

Understanding the Basics

Public key cryptography relies on key pairs:

• Public Key: Used to encrypt or verify.
• Private Key: Used to decrypt or sign.

Before performing encryption or signing operations, users must generate their own key pair and exchange public keys with their communication partners.

Encrypting Text

Use the recipient’s public key to encrypt plaintext. This method:

• Produces a shorter ciphertext.
• Does not reveal the sender’s identity.
• Is ideal when anonymity is preferred.

🔐 Tip: Don’t use your own public key to encrypt unless you’re sending a message to yourself.

Signing Text

Use your private key to sign text without encrypting it:

• This confirms authorship.
• Anyone with your public key can verify it.

Check the key’s Usage column for S to confirm it’s suitable for signing.

Decrypting Text

Paste or load the ciphertext into GpgFrontend. The tool will:

• Automatically use the correct private key.
• Notify you if no valid key is available.

✅ No need to check Usage manually; the tool handles key matching.

Verifying Signatures

To verify a detached or embedded signature:

• Use the sender’s public key.
• Paste or load the signed message.

GpgFrontend will:

• Check the integrity.
• Report any mismatch or missing public keys.

📥 If the required public key is missing, GpgFrontend prompts you to import it.

Best Practices

• Always verify a message before decrypting when possible.
• Share only your public key, and never your private key.
• Use Encrypt & Sign for secure and authenticated communication.
• Use Sign Only for publishing documents or messages that require integrity but not secrecy.