diff options
Diffstat (limited to 'src/content/docs/guides')
| -rw-r--r-- | src/content/docs/guides/key-server-operations.md | 48 | ||||
| -rw-r--r-- | src/content/docs/guides/openpgp-trust-manage.md | 4 | ||||
| -rw-r--r-- | src/content/docs/guides/symmetric-encrypt-decrypt.mdx (renamed from src/content/docs/guides/symmetric-encrypt-decrypt.md) | 57 |
3 files changed, 60 insertions, 49 deletions
diff --git a/src/content/docs/guides/key-server-operations.md b/src/content/docs/guides/key-server-operations.md index f11dd4d..ab58439 100644 --- a/src/content/docs/guides/key-server-operations.md +++ b/src/content/docs/guides/key-server-operations.md @@ -26,7 +26,7 @@ straightforward for all users.  -### How to Import: +### How to Import 1. Choose a key server from the drop-down list. 2. Enter a **Key ID**, **Fingerprint**, or **Email Address** into the search @@ -70,13 +70,13 @@ After v2.1.6, **GpgFrontend uses by default. This server uses the **Verifying Keyserver (VKS) Interface**, which provides extra protection against spam and key poisoning. -### Key Points: +### Key Points -- π **Only public keys are uploaded**, never private keys. -- β
**Master key is required** to export. -- βοΈ `keys.openpgp.org` requires email verification before your key becomes +- **Only public keys are uploaded**, never private keys. +- **Master key is required** to export. +- `keys.openpgp.org` requires email verification before your key becomes publicly searchable. -- 𧱠Uploaded keys are **propagated through the VKS protocol** and cannot be + Uploaded keys are **propagated through the VKS protocol** and cannot be deleted. To export: @@ -101,14 +101,16 @@ GpgFrontend will: - Compare the server copy with your local one. - Indicate if any update is applied. -> β οΈ Synchronization is **not available** if you have the private key locally. -> In this case, you are expected to **publish** updates, not pull them. +:::caution[Sync/Publish] -## Key Server Related Settings +Synchronization is **not available** if you have the private key locally. In +this case, you are expected to **publish** updates, not pull them. + +::: -You can configure your key server preferences in: +## Key Server Related Settings -> **Settings β Key Servers** +You can configure your key server preferences in: Settings β Key Servers  @@ -141,14 +143,12 @@ Setting a default key server **only affects key searches/imports**. This behavior ensures improved security and global consistency in public key management. -::: - -### Want to restore previous behavior? - -You can disable the `KeyServerSync` module in the module controller. This will -prevent GpgFrontend from forcing export/sync operations to use +Restore: You can disable the `KeyServerSync` module in the module controller. +This will prevent GpgFrontend from forcing export/sync operations to use `keys.openpgp.org`, allowing custom server logic to take effect again. +::: + ## Tips about Key Servers | Key Server | Fuzzy Search | VKS Interface | Notes | @@ -159,10 +159,14 @@ prevent GpgFrontend from forcing export/sync operations to use > π `keys.openpgp.org` does **not** support fuzzy search β you must use the > **exact email**, **full fingerprint**, or **full key ID**. -> β οΈ **Don't confuse search servers with export/sync servers** β even if you -> perform key searches using a custom server like `keyserver.ubuntu.com`, -> **Export** and **Sync** operations will still use `keys.openpgp.org` by -> default in **GpgFrontend v2.1.6 and later**. +:::caution[Confusing Concepts] + +**Don't confuse `search servers` with `export/sync servers`** β even if you perform +key searches using a custom server like `keyserver.ubuntu.com`, **Export** and +**Sync** operations will still use `keys.openpgp.org` by default in +**GpgFrontend v2.1.6 and later**. + +::: ## Automatically Check Key Publish Status @@ -181,8 +185,6 @@ helping users keep track of their key visibility on the VKS-based keyserver. ### How to Enable -To activate this: - 1. Go to `Settings β Network` tab. 2. Under **Network Ability**, check the box: `Automatically fetch key publish status from key server` diff --git a/src/content/docs/guides/openpgp-trust-manage.md b/src/content/docs/guides/openpgp-trust-manage.md index d7749d6..f21f48b 100644 --- a/src/content/docs/guides/openpgp-trust-manage.md +++ b/src/content/docs/guides/openpgp-trust-manage.md @@ -71,13 +71,13 @@ not fully considered.  -Currently: +### Current Behavior - GpgFrontend does not automatically upload signed UIDs to OpenPGP key servers. - Whether a signature update is accepted depends entirely on the specific key serverβs policy. -Reasons for not enforcing automatic synchronization: +### Reasons for not enforcing automatic synchronization Uncontrollable Behavior of Key Servers diff --git a/src/content/docs/guides/symmetric-encrypt-decrypt.md b/src/content/docs/guides/symmetric-encrypt-decrypt.mdx index 30512fa..88606ed 100644 --- a/src/content/docs/guides/symmetric-encrypt-decrypt.md +++ b/src/content/docs/guides/symmetric-encrypt-decrypt.mdx @@ -4,7 +4,7 @@ sidebar: label: Symmetric Crypto --- -## π What Is Symmetric Encryption? +## What Is Symmetric Encryption? **Symmetric encryption** is a method of securing data where the **same password** is used to both encrypt and decrypt information. @@ -13,42 +13,48 @@ Unlike **asymmetric encryption**, which uses a public/private key pair, symmetric encryption relies on a single shared secret (the password). This approach is: -- β
Fast and efficient -- β
Ideal for large files or quick one-time sharing -- β Best used when both parties can safely share the password +- Fast and efficient +- Ideal for large files or quick one-time sharing +- Best used when both parties can safely share the password -> π If someone intercepts the password, the encrypted data is no longer secure -> β so always handle password exchange carefully. +> If someone intercepts the password, the encrypted data is no longer secure β +> so always handle password exchange carefully. -## π How It Works +## How It Works 1. You choose a **strong password**. 2. That password is used to **encrypt** the data. 3. Anyone with the **same password** can **decrypt** it. 4. No key pair is required β only the shared password. -> π Encryption security depends entirely on the strength and secrecy of the +> Encryption security depends entirely on the strength and secrecy of the > password used. -## βοΈ Encrypting Data Symmetrically +## Encrypting Data Symmetrically To encrypt text using symmetric encryption in GpgFrontend (v2.1.9 and later): -Enable Symmetric Encryption Feature +### Enable Symmetric Encryption Feature 1. Go to the Settings. -2. Under the Appearance tab, check the `Sym. Encrypt` checkbox to enable symmetric encryption functionality. +2. Under the Appearance tab, check the `Sym. Encrypt` checkbox to enable + symmetric encryption functionality. -Access the Symmetric Encryption Button + -1. After enabling, youβll see a dedicated `Sym. Encrypt` button on the main interface. +### Access the Symmetric Encryption Button -Enter the Text or Select a File +After enabling, youβll see a dedicated `Sym. Encrypt` button on the main +interface. + + + +### Enter the Text or Select a File - Input the plaintext you wish to protect in the text editor. - Select a file to encrypt using the file panel. -Symmetric Encryption +### Symmetric Encryption 1. Without selecting any public key, click the `Sym. Encrypt` button. 2. When prompted, enter a strong, unique password. @@ -56,21 +62,24 @@ Symmetric Encryption 4. The text or file will be encrypted into ciphertext. 5. You can save or share the encrypted result. -> π The recipient will need the **exact same password** to decrypt the message. + + +> The recipient will need the **exact same password** to decrypt the message. -## π Decrypting Symmetric Encrypted Data +## Decrypting Symmetric Encrypted Data To decrypt content that was encrypted symmetrically: -1. Paste the Ciphertext: The message should begin with `-----BEGIN PGP MESSAGE-----` and end with `-----END PGP MESSAGE-----`. +1. Paste the Ciphertext: The message should begin with `-----BEGIN PGP + MESSAGE-----` and end with `-----END PGP MESSAGE-----`. 2. Initiate Decryption: Choose to decrypt the message. -3. Enter the Password: Input the **same password** that was used for - encryption. -4. View the Plaintext: If the password is correct, the original message will be revealed. +3. Enter the Password: Input the **same password** that was used for encryption. +4. View the Plaintext: If the password is correct, the original message will be + revealed. -> π§ If the password is incorrect or mistyped, decryption will fail. +> If the password is incorrect or mistyped, decryption will fail. -## π‘ When to Use Symmetric Encryption? +## When to Use Symmetric Encryption? Symmetric encryption is a great choice when: @@ -83,7 +92,7 @@ Symmetric encryption is a great choice when: However, it is **not ideal** for public communication where secure password exchange is difficult. -## π‘οΈ Tips for Better Security +## Tips for Better Security - Always use a **strong, complex password** (longer is better). - Never send passwords through insecure channels (e.g., unencrypted email). |