aboutsummaryrefslogtreecommitdiffstats
path: root/manual/features
diff options
context:
space:
mode:
Diffstat (limited to 'manual/features')
-rw-r--r--manual/features/automatic-pubkey-exchange.md17
-rw-r--r--manual/features/introduce.md4
-rw-r--r--manual/features/short-ciphertext.md14
3 files changed, 35 insertions, 0 deletions
diff --git a/manual/features/automatic-pubkey-exchange.md b/manual/features/automatic-pubkey-exchange.md
new file mode 100644
index 00000000..94ae12de
--- /dev/null
+++ b/manual/features/automatic-pubkey-exchange.md
@@ -0,0 +1,17 @@
+# Public Key Sync
+
+Sometimes, you need to keep your local key consistent with the one on the key server. This is critical in cases where a key owner revokes its key, at which point you need to stop using the key immediately. This avoids potential man-in-the-middle attacks. Or, if the key owner creates a new subkey for signing, gpg will not be able to verify the validity of the ciphertext if the ciphertext he sends to you signs with the subkey and you do not have local information about the subkey.
+
+## How to use
+
+It's very simple, after clicking the Sync Public Key button in the Key ToolBox or the Key Management interface on the homepage, things will be done automatically.
+
+![image-20220101232228519](_media/automatic-pubkey-exchange/image-20220101232228519.png)
+
+This feature will check all the public keys you now have (only the public key, not any private keys) and then search for it in the key server. If the corresponding public key is found in the key server, GpgFrontend will import the latest public key from the key server to the local.
+
+### Key server
+
+How do I know which key server GpgFrontend accessed? It's simple, GpgFrontned will exchange keys using the default key server you set up. If you need to change the key server you need to access, you just need to add your key server in the settings and set it as the default.
+
+![image-20220101232902590](_media/automatic-pubkey-exchange/image-20220101232902590.png)
diff --git a/manual/features/introduce.md b/manual/features/introduce.md
new file mode 100644
index 00000000..eb250877
--- /dev/null
+++ b/manual/features/introduce.md
@@ -0,0 +1,4 @@
+# Introduce Features
+
+GpgFrontend provides some advanced functions that can meet the needs of certain scenarios.
+These features will be gradually introduced as the version is updated.
diff --git a/manual/features/short-ciphertext.md b/manual/features/short-ciphertext.md
new file mode 100644
index 00000000..8e301966
--- /dev/null
+++ b/manual/features/short-ciphertext.md
@@ -0,0 +1,14 @@
+# Short Cipher-text
+
+**NOTICE: As of version 2.0.0, GpgFrontend has eliminated this feature.**
+
+The short ciphertext function allows OpenPGP to transfer ciphertext quickly and conveniently in instant messaging software.
+After successfully configuring the own key and obtaining the Service Token, you can use the short cipher text function.
+
+After the encryption and signature operations, you can click the short crypto button in the additional operations menu.
+GpgFrontend will return a very short ciphertext, and you can publish the short ciphertext anywhere.
+
+You can paste the ciphertext into the text tab of GpgFrontend and select decryption and verification operations.
+At this time, GpgFrontend will perform the corresponding operations.
+
+Note: The short ciphertext is valid within seven days of being generated. The short ciphertext function has restrictions on the length of the ciphertext.