aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorsaturneric <[email protected]>2025-06-12 05:22:55 +0000
committersaturneric <[email protected]>2025-06-12 05:22:55 +0000
commitb3b7b4e8b84b6fb938197b28d7f572d3fb0917f0 (patch)
tree149812ed775fa40096dbb0304af6a897bfbd0696
parentdocs(advanced/key-database): update multi-key database documentation (diff)
downloadManual-b3b7b4e8b84b6fb938197b28d7f572d3fb0917f0.tar.gz
Manual-b3b7b4e8b84b6fb938197b28d7f572d3fb0917f0.zip
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
-rw-r--r--src/content/docs/advanced/sync-public-keys.md (renamed from src/content/docs/advanced/sync-all-public-keys.md)23
1 files changed, 12 insertions, 11 deletions
diff --git a/src/content/docs/advanced/sync-all-public-keys.md b/src/content/docs/advanced/sync-public-keys.md
index d3ddb79..4c4b4d1 100644
--- a/src/content/docs/advanced/sync-all-public-keys.md
+++ b/src/content/docs/advanced/sync-public-keys.md
@@ -2,6 +2,7 @@
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
@@ -26,19 +27,19 @@ 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.
+ 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.
+ 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.
+ 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.
+ 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)
@@ -75,4 +76,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. \ No newline at end of file
+ to prevent interception or tampering.