From b3b7b4e8b84b6fb938197b28d7f572d3fb0917f0 Mon Sep 17 00:00:00 2001 From: saturneric Date: Thu, 12 Jun 2025 07:22:55 +0200 Subject: docs(sync-public-keys): update and reorder sync public keys documentation - rename file from sync-all-public-keys.md to sync-public-keys.md - add order 4 to sidebar - fix indentation in numbered list - improve formatting and consistency - ensure proper line endings --- src/content/docs/advanced/sync-all-public-keys.md | 78 ---------------------- src/content/docs/advanced/sync-public-keys.md | 79 +++++++++++++++++++++++ 2 files changed, 79 insertions(+), 78 deletions(-) delete mode 100644 src/content/docs/advanced/sync-all-public-keys.md create mode 100644 src/content/docs/advanced/sync-public-keys.md diff --git a/src/content/docs/advanced/sync-all-public-keys.md b/src/content/docs/advanced/sync-all-public-keys.md deleted file mode 100644 index d3ddb79..0000000 --- a/src/content/docs/advanced/sync-all-public-keys.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: Synchronizing Public Keys with Key Server -sidebar: - label: Sync Public Keys ---- - -Keeping your public keys in sync with those stored on a key server is crucial -for secure communications. This synchronization ensures that any changes to -public keys, such as revocations or the addition of subkeys, are reflected in -your local keyring. Without this, you may be vulnerable to security risks like -man-in-the-middle attacks or authentication errors. - -## Importance of Public Key Synchronization - -**Key Revocation:** If a key is revoked by its owner, it's vital to stop using -it immediately. Revocation might occur if the private key is compromised or if -the key is no longer used. - -**Subkey Updates:** If a new signing subkey is generated, it's essential for -your local gpg to recognize it. Without the updated information, gpg won't -authenticate signatures made with the new subkey. - -## How to Sync Public Keys - -GpgFrontend automates the public key synchronization process through a -user-friendly interface. Here’s how to use it: - -1. Open the Key Management Interface: Navigate to the Key Management interface -by clicking on the "Manage Keys" button in the main interface. -2. Select Keys to Sync: In the list of public keys, you can select specific keys -to sync by checking the boxes next to them. If you want to sync all public keys, -you do not need to select any specific keys. -3. Click the Sync Public Key Button: Locate and click the **Sync Public Key** -button. This button is represented by a cloud icon with a refresh symbol, -located in the toolbar at the top of the Key Management interface.If you have -selected specific keys, the synchronization process will initiate for those -keys. If no keys are selected, a confirmation prompt will appear, asking you to -confirm if you want to synchronize all public keys. -4. Synchronization Process: The feature works by checking all the public keys in -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. - -![](https://image.cdn.bktus.com/i/2024/06/15/8771cd76-1a46-321e-8bf9-93d8db2a9f78.webp) - -By following these steps, you can ensure that your public keys are always -up-to-date, enhancing the security and reliability of your cryptographic -communications. - -### Choosing the Right Key Server - -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. - -![](https://image.cdn.bktus.com/i/2024/06/15/03471d32-54f2-2be7-53a3-eeee03f74372.webp) - -:::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: - -1. Navigate to the key server settings within GpgFrontend. -2. Add your preferred key server's details. -3. Set it as the default for future synchronizations. - -## Best Practices for Key Synchronization - -- **Regular Sync:** Regularly sync your keys to ensure you have the latest - updates, especially before engaging in secure communication. -- **Verify Changes:** After syncing, verify any changes or updates to ensure - they are legitimate. -- **Secure Network:** Always perform key synchronization over a secure network - to prevent interception or tampering. \ No newline at end of file diff --git a/src/content/docs/advanced/sync-public-keys.md b/src/content/docs/advanced/sync-public-keys.md new file mode 100644 index 0000000..4c4b4d1 --- /dev/null +++ b/src/content/docs/advanced/sync-public-keys.md @@ -0,0 +1,79 @@ +--- +title: Synchronizing Public Keys with Key Server +sidebar: + label: Sync Public Keys + order: 4 +--- + +Keeping your public keys in sync with those stored on a key server is crucial +for secure communications. This synchronization ensures that any changes to +public keys, such as revocations or the addition of subkeys, are reflected in +your local keyring. Without this, you may be vulnerable to security risks like +man-in-the-middle attacks or authentication errors. + +## Importance of Public Key Synchronization + +**Key Revocation:** If a key is revoked by its owner, it's vital to stop using +it immediately. Revocation might occur if the private key is compromised or if +the key is no longer used. + +**Subkey Updates:** If a new signing subkey is generated, it's essential for +your local gpg to recognize it. Without the updated information, gpg won't +authenticate signatures made with the new subkey. + +## How to Sync Public Keys + +GpgFrontend automates the public key synchronization process through a +user-friendly interface. Here’s how to use it: + +1. Open the Key Management Interface: Navigate to the Key Management interface + by clicking on the "Manage Keys" button in the main interface. +2. Select Keys to Sync: In the list of public keys, you can select specific keys + to sync by checking the boxes next to them. If you want to sync all public keys, + you do not need to select any specific keys. +3. Click the Sync Public Key Button: Locate and click the **Sync Public Key** + button. This button is represented by a cloud icon with a refresh symbol, + located in the toolbar at the top of the Key Management interface.If you have + selected specific keys, the synchronization process will initiate for those + keys. If no keys are selected, a confirmation prompt will appear, asking you to + confirm if you want to synchronize all public keys. +4. Synchronization Process: The feature works by checking all the public keys in + 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. + +![](https://image.cdn.bktus.com/i/2024/06/15/8771cd76-1a46-321e-8bf9-93d8db2a9f78.webp) + +By following these steps, you can ensure that your public keys are always +up-to-date, enhancing the security and reliability of your cryptographic +communications. + +### Choosing the Right Key Server + +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. + +![](https://image.cdn.bktus.com/i/2024/06/15/03471d32-54f2-2be7-53a3-eeee03f74372.webp) + +:::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: + +1. Navigate to the key server settings within GpgFrontend. +2. Add your preferred key server's details. +3. Set it as the default for future synchronizations. + +## Best Practices for Key Synchronization + +- **Regular Sync:** Regularly sync your keys to ensure you have the latest + updates, especially before engaging in secure communication. +- **Verify Changes:** After syncing, verify any changes or updates to ensure + they are legitimate. +- **Secure Network:** Always perform key synchronization over a secure network + to prevent interception or tampering. -- cgit v1.2.3