[pkg-gnupg-maint] Bug#787313: Bug#787313: Bug#787313: Bug#787313: Systemd user unit for gnupg-agent

[Daniel Kahn Gillmor]

On Wed 2015-06-03 13:30:21 -0400, Moritz Mühlenhoff wrote:
> On Wed, Jun 03, 2015 at 10:03:42AM +0200, Werner Koch wrote:
>> On Wed,  3 Jun 2015 08:05, gniibe at fsij.org 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.

Should we mark this bug as wontfix, then, or close it?

>> >> 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.

Thanks for the nudge here.  2.1.4-2 (just uploaded to experimental) now
contains the following change of description:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-updated-gpg-agent-description.patch
Type: text/x-diff
Size: 1369 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20150603/065e8607/attachment.patch>
-------------- next part --------------

Feel free to suggest any other changes that you think might be worth
including in future versions.

Regards,

        --dkg