https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #20 from michaelk83 <mk.mat...@gmail.com> --- (In reply to michaelk83 from comment #18) > A related question is where does GPG take its passphrase from when Secret > Service is not running? To answer my own question after re-reading the OP, the alternative passphrase source is simply a user prompt (and I guess gpg-agent after that). According to https://unix.stackexchange.com/a/188813/455274 : > When a GPG process needs the key, it contacts the running gpg-agent program > through a socket and > requests the key. If the agent process has the key, it provides it to gpg. If > it doesn't, it attempts > to load the encrypted key from your keyring, and prompts you for the key's > passphrase. Once the agent > has obtained the decrypted key, it passes it to the gpg process. ... > The main point of using a key agent is so that you don't have to type your > passphrase every single > time you use your key. The agent keeps the key in memory from one time to the > next. The problem step is "attempts to load the encrypted key from your keyring". @nic.christin, could you run `dbus-monitor "destination=org.freedesktop.secrets" "sender=org.freedesktop.secrets"` before launching the app that tries to access KWallet, and until the passphrase prompt shows up? Mask out any byte arrays before posting that here, as they may contain secret data. (Hmm.. we might need Bug 458341 fixed first, not sure. Anyway, no harm in trying.) And two other experiments: 1. After providing the passphrase, if you close the wallet, and then launch that app again, do you get the delay again? In theory, the key should already be in gpg-agent, so the problem step should be skipped. 2. If you load the key/passphrase into gpg-agent before accessing KWallet for the 1st time, do you still get the delay? (For example, try using the same key to encrypt/decrypt some other file.) -- You are receiving this mail because: You are watching all bug changes.
