diff options
| author | saturneric <[email protected]> | 2025-04-09 19:44:05 +0000 |
|---|---|---|
| committer | saturneric <[email protected]> | 2025-04-09 19:44:05 +0000 |
| commit | 548ee447aa72abd2c7bb1a85bb878ca53b77e808 (patch) | |
| tree | d25a75f71fdd6deb98d95c34997d67917c4de72f /src/content/docs/advanced/sync-all-public-keys.md | |
| parent | feat: adapt manual to v2.1.7 (diff) | |
| download | Manual-548ee447aa72abd2c7bb1a85bb878ca53b77e808.tar.gz Manual-548ee447aa72abd2c7bb1a85bb878ca53b77e808.zip | |
chore: make structure better
Diffstat (limited to 'src/content/docs/advanced/sync-all-public-keys.md')
| -rw-r--r-- | src/content/docs/advanced/sync-all-public-keys.md | 64 |
1 files changed, 24 insertions, 40 deletions
diff --git a/src/content/docs/advanced/sync-all-public-keys.md b/src/content/docs/advanced/sync-all-public-keys.md index 3dc0eac..d3ddb79 100644 --- a/src/content/docs/advanced/sync-all-public-keys.md +++ b/src/content/docs/advanced/sync-all-public-keys.md @@ -10,9 +10,6 @@ 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. -Here's a structured guide to maintaining public key synchronization using the -GpgFrontend's Public Key Sync feature. - ## Importance of Public Key Synchronization **Key Revocation:** If a key is revoked by its owner, it's vital to stop using @@ -28,33 +25,22 @@ authenticate signatures made with the new subkey. 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. - - +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. + + By following these steps, you can ensure that your public keys are always up-to-date, enhancing the security and reliability of your cryptographic @@ -67,10 +53,14 @@ 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 -_Note: Replace the placeholder text with the actual link to the image showing -the key server settings._ +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: @@ -85,10 +75,4 @@ If you need to use a different key server: - **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. - -## Conclusion - -By following this guide, you can ensure that your public keys are always -up-to-date, reflecting the current status on the key server, thereby maintaining -the integrity of your encrypted communications. + to prevent interception or tampering.
\ No newline at end of file |