I often fail to remember when my GPG keys expire, so when it happens I have created new keys, and temporarily rolled back the computer time/date to sign the new keys with the expired keys. It were proactively nice to be able to get notifications before selected keys expire (and dismiss/postpone these notifications). Per key, this probably requires a notification time and a boolean whether the notification is active. Changes to the expiration time of monitored keys also need to be handled. It were also nice if KGPG would also ask to enable the notifications after (or during) key generation or import. Reproducible: Always
I wonder if a setting per key is really needed, do you really have that many secret keys that this would have to be set per key?
I think it is needed. Personally, I only need notifications for keys I'm responsible for and need to update or keep track of. For example, I would not care much when another person's key is about to expire, unless I want to manually update that key from a keyserver. PS: Is kgpg also missing a "refresh all keys" feature? Should I file a separate bug for this?
> I think it is needed. > > Personally, I only need notifications for keys I'm responsible for and need > to update or keep track of. For example, I would not care much when another > person's key is about to expire, unless I want to manually update that key > from a keyserver. I was talking about only watching keys where you have the secret key for. > PS: Is kgpg also missing a "refresh all keys" feature? Should I file a > separate bug for this? Ctrl-A, rightclick, refresh. That's fast enough that I will not add a shortcut for this.