blob: cfc87d601c9aa557af14ed3c9e78adaf801d019f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
# 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 the Key Management interface, things will be done
automatically.
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.
### Which Key Server Was Used
How do I know which key server GpgFrontend accessed? It's simple, GpgFrontend 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.
|
