Use keyserver specific cache instead of general
Reported by Support | October 20th, 2022 @ 05:31 PM
Assigned to
Stable #121371. Currently the answer for queries if a public
key exists or not on a keyserver are cached in a plist. The results
however are not mapped to a specific keyserver and instead all go
into one list.
This generally works, since SKS based keyserver are synchronizing
between each other, so the assumption that if a key is found on one
it will be on the others is not incorrect.
If however the user switches between different keyservers and they
report different states (in case of a bug for example), the cached
result could be valid for one keyserver but not the other, leading
to inconsistent behavior in for example GPG Keychain.
(See discussion for how to reproduce. Created by Luke Le)
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Luke Le
steve
Support