diff options
Diffstat (limited to 'src/content/docs/advanced/sync-public-keys.md')
| -rw-r--r-- | src/content/docs/advanced/sync-public-keys.md | 26 |
1 files changed, 17 insertions, 9 deletions
diff --git a/src/content/docs/advanced/sync-public-keys.md b/src/content/docs/advanced/sync-public-keys.md index 4c4b4d1..07d19a4 100644 --- a/src/content/docs/advanced/sync-public-keys.md +++ b/src/content/docs/advanced/sync-public-keys.md @@ -41,7 +41,7 @@ user-friendly interface. Here’s how to use it: your possession against the key server. If there is an updated version of a key you own, GpgFrontend will import the new details to your local keyring. - + By following these steps, you can ensure that your public keys are always up-to-date, enhancing the security and reliability of your cryptographic @@ -54,14 +54,7 @@ To know which key server GpgFrontend interacts with, follow these steps: 1. Go to the settings section of GpgFrontend. 2. The default key server configured will be listed here. - - -:::tip - -Replace the placeholder text with the actual link to the image showing -the key server settings. - -::: + If you need to use a different key server: @@ -69,6 +62,21 @@ If you need to use a different key server: 2. Add your preferred key server's details. 3. Set it as the default for future synchronizations. +:::caution[Changes (v2.1.6 and later)] + +Setting a default key server **only affects key searches/imports**. + +- **Export** and **Sync** operations are no longer affected by this setting. +- These operations **always use `https://keys.openpgp.org`**, which implements + the Verifying Keyserver (VKS) API. + +This behavior ensures improved security and global consistency in public key +management. + +Or: [Want to restore previous behavior?](/guides/key-server-operations/#want-to-restore-previous-behavior) + +::: + ## Best Practices for Key Synchronization - **Regular Sync:** Regularly sync your keys to ensure you have the latest |