diff options
Diffstat (limited to 'src/content/docs/advanced')
| -rw-r--r-- | src/content/docs/advanced/key-package.md | 63 | ||||
| -rw-r--r-- | src/content/docs/advanced/sync-all-public-keys.md | 76 |
2 files changed, 139 insertions, 0 deletions
diff --git a/src/content/docs/advanced/key-package.md b/src/content/docs/advanced/key-package.md new file mode 100644 index 0000000..28b8014 --- /dev/null +++ b/src/content/docs/advanced/key-package.md @@ -0,0 +1,63 @@ +--- +title: KeyPackage Functionality +sidebar: + label: KeyPackage +--- + +## Overview + +The KeyPackage is a feature designed to securely package and transfer key data +between different devices. It encapsulates both the public and private keys of +multiple key pairs, ensuring that users can maintain cryptographic functionality +across various platforms. This document outlines the process of creating, +exporting, and safely transferring a KeyPackage. + +## Creating a KeyPackage + + + +## Exporting the KeyPackage + +After configuring the export settings: + +1. Click on the 'OK' button to create the KeyPackage. +2. The interface will generate two files: + - A `.gpgpack` file containing the packaged keys. + - A `.key` file which should be kept confidential and deleted after the transfer is complete. + +## Security Notice + +When the KeyPackage is successfully created, a message will inform you that the +package is protected with encryption algorithms (e.g., AES-256-ECB) and is safe +to transfer. However, it emphasizes that the key file must not be disclosed +under any circumstances. Users are advised to delete the KeyPackage file and the +key file as soon as possible after the transfer is complete. + +## Transferring the KeyPackage + +To transfer the KeyPackage: + +1. Use a secure transfer method to move the `.gpgpack` file to the target + device. This could be through a secured network connection, encrypted email, + or a physical device like a USB drive, which should be encrypted as well. +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 + + + +## Best Practices + +- Always ensure that you are transferring key data over a secure channel. +- Keep the passphrase strong and confidential. +- Delete the KeyPackage files from all devices and any intermediaries (like + email servers or cloud storage) after the transfer is complete to prevent + unauthorized access. + +## Conclusion + +The KeyPackage feature streamlines the process of transferring key data between +devices while maintaining high security standards. By following the steps +outlined in this document, users can effectively manage their cryptographic keys +across multiple platforms. diff --git a/src/content/docs/advanced/sync-all-public-keys.md b/src/content/docs/advanced/sync-all-public-keys.md new file mode 100644 index 0000000..4266fc3 --- /dev/null +++ b/src/content/docs/advanced/sync-all-public-keys.md @@ -0,0 +1,76 @@ +--- +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. + +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 +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. +2. Locate and click the **Sync Public Key** button. This initiates the automatic + synchronization. + + + +_Note: Replace the placeholder text with the actual link to the image showing +the Sync Public Key button._ + +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. + +### 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. + + + +_Note: 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. + +## 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. |