-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 7/7/19 1:55 am, Jason White via luv-main wrote:
Andrew McGlashan via luv-main <luv-main@luv.asn.au> wrote:
The gpg.conf change didn't help, still got micahflee key growing just with an "automatic, checking trustdb" action, triggered on use of gpg. :
What happens if you remove that key and retrieve it again - this time from the alternative key server.
There's a good subscriber-only LWN article on this issue.
The SKS servers are poisoned, it is the /usual/ place to get keys; a better option is sometimes more direct without using any key servers. I had a lesser size key for micahflee and afer deleting the active key and re-importing from a non poisoned .asc file, it still grew when gpg did a "checking trustdb'. If the key is there and there is a means to update it, it will grow. All SKS servers are meant to, normally, distribute data; once you poison a key, it will propagate to all the servers because none of them is doing the sanity checking that is needed and they might not be able to do so anyway if they wanted to. The easiest thing to do right now is to simply delete the bad keys and only import them from clean sources *if* you need to use them, then delete them again when done. *MAYBE* my Enigmail has been part of the problem in refreshing keys, but I don't think so. I've just changed Enigmail settings, to see if that helps. Kind Regards AndrewM -----BEGIN PGP SIGNATURE----- iHUEAREIAB0WIQTJAoMHtC6YydLfjUOoFmvLt+/i+wUCXSGPXQAKCRCoFmvLt+/i +wjvAP9VQojj9r48rYdvx991Od7YxiyIVEefYQsumTYUE6m2pwD9GCtxYAck5V9b qv6QVJ64JnIue3Uh4Y8VQAWsqSu3GvA= =5fd3 -----END PGP SIGNATURE-----