subject says all.
Description
Event Timeline
Replacing revoked keys made me wonder if we actually need an auto-refresh key.
If we try to return one valid key with --locate-keys wouldn't it make more sense
semantically if we use the auto-key-locate mechanisms with locate-keys when a
key is expired in the local store?
This would also work better for revoked keys where a Parcimonie style auto
refresh would pick up the revocation and locate-keys would then look for a new key.
Especially when an LDAP is configured, keys should be automatically refreshed in short intervals (5 days? Configurable?) to notify users about revoked keys or signatures from a trusted key.
Keys that are close to their expiration dates should be prioritized.
Maybe users want to configure for what mail domains a lookup on a configured LDAP should be done.
Additionally, a configurable list of fingerprints for "important keys" should be implemented.
If a key from that list is not available it should always be automatically imported, and updated more often than regular keys.
Maybe it should be configurable if a key refresh should also look for keys on a WKD. (This configuration is possible in Kleopatra.)