diff options
| author | saturneric <[email protected]> | 2024-06-14 20:11:13 +0000 |
|---|---|---|
| committer | saturneric <[email protected]> | 2024-06-14 20:11:13 +0000 |
| commit | 0d806fc1d0bea83b89c5af9910e6203b76cb939d (patch) | |
| tree | f65ea4a756ea36545f483629f492fafc87477459 /src/content/docs/advanced | |
| parent | Merge branch 'main' of https://github.com/saturneric/GpgFrontend-Manual (diff) | |
| download | Manual-0d806fc1d0bea83b89c5af9910e6203b76cb939d.tar.gz Manual-0d806fc1d0bea83b89c5af9910e6203b76cb939d.zip | |
feat: fit documents to v2.1.3
Diffstat (limited to 'src/content/docs/advanced')
| -rw-r--r-- | src/content/docs/advanced/key-package.md | 37 | ||||
| -rw-r--r-- | src/content/docs/advanced/sync-all-public-keys.md | 44 |
2 files changed, 65 insertions, 16 deletions
diff --git a/src/content/docs/advanced/key-package.md b/src/content/docs/advanced/key-package.md index 3f5868e..fd85173 100644 --- a/src/content/docs/advanced/key-package.md +++ b/src/content/docs/advanced/key-package.md @@ -70,7 +70,42 @@ To transfer the KeyPackage: 2. Once transferred, import the KeyPackage into the key management tool on the target device using the passphrase set during the creation process. -## After Transfer: Importing and Verifying +## After Transfer: Importing + +To import the KeyPackage after transferring it to the target device, follow +these steps: + + + +1. **Initiate Import**: + + - Open the key management tool on the target device and click on the "Import + Key" button. + +2. **Select KeyPackage Option:** + + - As shown in the image, from the dropdown menu, select the "Key Package" + option. This indicates that you will be importing a KeyPackage. + +3. **Select KeyPackage File**: + + - A file selection dialog will appear. First, choose the `.gpgpack` file that + you transferred. This file contains the packaged keys. + +4. **Select Key File**: + + - After selecting the `.gpgpack` file, another file selection dialog will + prompt you to choose the corresponding key file. This key file is used to + decrypt the KeyPackage. + +5. **Import Keys**: + - Once both files are selected, the key management tool will automatically + import the keys contained within the KeyPackage. You will be prompted to + enter the passphrase that was set during the creation of the KeyPackage to + complete the import process. + +By following these steps, you can securely import your cryptographic keys from +the KeyPackage into the key management tool on the target device. ## Best Practices diff --git a/src/content/docs/advanced/sync-all-public-keys.md b/src/content/docs/advanced/sync-all-public-keys.md index 687e553..3dc0eac 100644 --- a/src/content/docs/advanced/sync-all-public-keys.md +++ b/src/content/docs/advanced/sync-all-public-keys.md @@ -28,23 +28,37 @@ 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. -2. In the list of public keys, you can now select specific keys to sync by - checking the boxes next to them. -3. Locate and click the **Sync Public Key** button. This initiates the automatic - synchronization for the selected keys. If no keys are selected, all public - keys will be synchronized. In this case, a confirmation prompt will appear to - confirm full synchronization. +1. **Open the Key Management Interface**: - + - Navigate to the Key Management interface by clicking on the "Manage Keys" + button in the main interface. -_Note: Replace the placeholder text with the actual link to the image showing -the Sync Public Key button._ +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. + + -The feature works by checking all the public keys in your possession against the -key server. If there's 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 +communications. ### Choosing the Right Key Server @@ -53,7 +67,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. - + _Note: Replace the placeholder text with the actual link to the image showing the key server settings._ |