blob: e753fa68ac8a707b36de3b98c698024cf8d27d2b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
|
---
title: Text Operations
sidebar:
order: 5
---
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
### Only Encrypt
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.
### Encrypt & Sign
This method encrypts the message with the recipient's public key and signs it
with **your own private key**, ensuring:
- Confidentiality
- Message authenticity
- Proof of origin
To use this method:
- Choose the recipient’s public key.
- Select **your private key** with signing capability (`Usage = S`).
> 📄 The resulting ciphertext is longer due to the signature. The Info Board
> will display signature details after encryption.
## Signing Text
### Signature Only
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.
### Sign with Encryption
Sign and encrypt together by selecting the recipient's public key and your own
private signing key:
- Ensures both confidentiality and authenticity.
- Common in secure messaging or business communication.
---
## Decrypting Text
### Decrypt Only
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.
### Decrypt & Verify
If the message was signed, GpgFrontend will:
- Verify the signature using the **sender’s public key**.
- Display whether the signature is valid.
Use this for added assurance of sender authenticity and message integrity.
---
## 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.
|
