Bug#760102: gnome keyring & gpg agent

[Daniel Kahn Gillmor]

On Fri 2015-06-05 00:36:04 -0400, Michael Biebl wrote:
> Am 05.06.2015 um 06:20 schrieb Daniel Kahn Gillmor:
>> If gnome-keyring can Depend: pinentry-gnome3 (#787786), it should be
>> able to build with --disable-gpg-agent.
>
> I just installed pinentry-gnome3 to give it a try, but apparently it
> needs further configuration to be used by gnome-keyring.
> Can you explain, how?

You need to:

 * disable gnome-keyring's gpg-agent mechanism (either by rebuilding
gnome-keyring with --disable-gpg-agent or by fiddling with
/etc/xdg/autostart/gnome-keyring-gpg.desktop) , and

 * make sure the gnupg-agent package is installed, and that gpg-agent is
running in your session (usually started by
/etc/X11/Xsession.d/90gpg-agent for gpg-agent < 2.1, or automatically
when needed for gpg2 and gpg-agent >= 2.1)

Then any gpg or gpg2 process that wants to talk to the gpg-agent will
find it.  when gpg-agent wants a passphrase, it will invoke pinentry,
which should now be provided by pinentry-gnome3.  this uses gcr for
prompting, and uses libsecret to (optionally) store passphrases with
gnome-keyring.

make sense?  does this work for you?  please let me know if you're
having any trouble with it, i'm happy to help.

       --dkg