On Wed, Jun 03, 2015 at 10:03:42AM +0200, Werner Koch wrote:
> On Wed, 3 Jun 2015 08:05, [email protected] said:
>
> > Thank you. I think it makes sense.
>
> I don't think so. GnuPG uses a locking mechanism to avoid that several
> instances of gpg and friends start gpg-agent. Thus watching the socket
> file and starting gpg-agent on a connect attempt won't work too well.
I wasn't aware of the new agent standard socket and the on-demand loading
you mentioned. I agree that's the better approach than using a systemd
unit.
> >> Description=GNU privacy guard password agent
> > ^^^^^^^^
> >
> > This is not accurate description, today. In modern GnuPG, gpg-agent
> > basically handles operations for secret keys.
>
> Actually since 1.9 (in 2003) where this has always been required by
> GnuPG's CMS/X.509 (aka S/MIME) part.
You're right. I took that from the gnupg-agent Debian package description,
though. We should fix that one as well, then.
Cheers,
Moritz
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
