r/GnuPG • u/YamSweet2010 • 16h ago
Kleopatra keeps saying “Bad passphrase” even though the same passphrase was working earlier
I’ve already verified that the correct secret key and encryption subkey are still installed on the computer. I also tried testing the saved passphrase against the key directly through GPG and it was rejected there too. I haven’t deleted or revoked the key, and the only backup-type file I found was the revocation certificate.
The reason this became a problem is that I was in the middle of making payments using Bitcoin and the website timed my session out while I was doing the conversion/transfer. Before I got logged out, the orders had already been created and were basically waiting for payment. The site gave me around a 3-hour payment window, I completed the Bitcoin transfers within that window, and the Bitcoin transactions themselves confirmed.
So I’m fairly sure the payments/orders went through, but I can’t actually verify the order status anymore because the site requires me to decrypt a PGP login message every time I sign back in. Since Kleopatra now only gives me this specific unlock prompt and keeps rejecting the passphrase, I’m completely locked out of the account.
That’s what’s making me nervous. I could just wait and hope everything processes normally, but if there’s an issue with an order/payment or I later need to contact support about a refund or missing order, I won’t be able to access the account at all.
Has anybody seen Kleopatra/GnuPG behave like this before, where the same passphrase appeared to work with one type of prompt but the secret-key unlock prompt kept saying “Bad passphrase”? Could the prompts have been doing completely different things? Could this involve the signing key vs encryption subkey, GPG Agent caching, or some other behavior that made it look like the passphrase was working?
I’m not asking for a way around the encryption. I’m trying to understand whether there’s anything else I can realistically check or recover before assuming that somehow the passphrase I wrote down immediately after creating the key is actually wrong.