gpg stalls key management, seahorse enigmail all affected

galen · 08-07-2019, 04:05 PM

somehow I deleted a secret key, after 2 decades using pgp gpg I would know better.
I restored the directory but now key management is broken / stalled.
I generally use enigmail to manage keys but it stalls, seahorse stalls.

Code:

gpg --list-secret-keys
gpg: checking the trustdb
gpg: public key ACBB164BCF73EC4C is 1479 days newer than the signature
gpg: public key ACBB164BCF73EC4C is 326 days newer than the signature
gpg: public key ACBB164BCF73EC4C is 1479 days newer than the signature
gpg: public key ACBB164BCF73EC4C is 326 days newer than the signature
gpg: public key ACBB164BCF73EC4C is 326 days newer than the signature
gpg: public key ACBB164BCF73EC4C is 326 days newer than the signature
gpg: public key ACBB164BCF73EC4C is 326 days newer than the signature
gpg: public key ACBB164BCF73EC4C is 1479 days newer than the signature
gpg: public key ACBB164BCF73EC4C is 326 days newer than the signature

any hope of repair?

computer_freak_8 · 08-17-2019, 03:00 PM

Quote:

Originally Posted by galen

Code:

gpg: public key ACBB164BCF73EC4C is 1479 days newer than the signature
gpg: public key ACBB164BCF73EC4C is 326 days newer than the signature

My first question would be to confirm the clock is set properly? Though likely not the issue.

When you say "restored the directory", do you mean with or without the private key? If it's without the private key, I'd assume it's just not going to work right. I'd probably move the directory to a .bak variant, let it rebuilt what it needs upon launching.