| Summary: | Provide key expiration notifications | ||
|---|---|---|---|
| Product: | [Applications] kgpg | Reporter: | Jaak Ristioja <jaak> |
| Component: | general | Assignee: | Rolf Eike Beer <kde> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | All | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Jaak Ristioja
2015-12-31 10:15:03 UTC
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. |