https://bugs.kde.org/show_bug.cgi?id=448408
Bug ID: 448408
Summary: Kwallet unable to find key to decrypt wallet file
Product: frameworks-kwallet
Version: 5.90.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: general
Assignee: va...@kde.org
Reporter: ad...@arkades.org
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
preface: Today kleopatra corrupted my gpg keyring.
$gpg --list-secret-keys; threw lots of errors about database corruption.
I removed the ~/.gnupg/pubring.gpg and left ~/.gnupg unchanged.
$gpg --list-secret-keys; did output nothing. But ~/.gnupg/private-keys-v1.d
still existing of course.
Now I had to restore my secret keys by importing my own public keys from
keyserver.
So $gpg --list-secret-keys; does list my private keys again.
But now suddenly kwalletmanager is unable to decrypt my gpg encrypted wallet,
lets name it "publicwallet".
The error message says:
"Error when attempting to decrypt the wallet publicwallet using GPG. If you're
using a SmartCard, please ensure it's inserted then try again.
GPG error was No secret key"
Creating a new gpg wallet "testwallet" works as expected:
it asks me to choose one of my trusted keys (which I restored before)
and for passphrase, which also works as expected.
So I don't understand why "No secret key" is thrown by GPG as I try to open
"publicwallet" because it was created and encrypted with the exact same gpg key
for sure!
Now how do I find out which KEY ID Kwallet backend is requesting from GPG?
Is it possible to decrypt the kwallet file "publicwallet.kwl" with gpg only,
for testing purposes?
--
You are receiving this mail because:
You are watching all bug changes.
