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

2015-06-03 Thread Moritz Muehlenhoff
On Wed, Jun 03, 2015 at 02:22:07PM -0400, Daniel Kahn Gillmor wrote: > 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, gni...@fsij.org said: > >> > >> > Thank you. I think it makes sense. >

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

2015-06-03 Thread 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, gni...@fsij.org said: >> >> > Thank you. I think it makes sense. >> >> I don't think so. GnuPG uses a locking mechanism to avoid that several >

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

2015-06-03 Thread Moritz Mühlenhoff
On Wed, Jun 03, 2015 at 10:03:42AM +0200, Werner Koch wrote: > On Wed, 3 Jun 2015 08:05, gni...@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

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

2015-06-03 Thread Werner Koch
On Wed, 3 Jun 2015 08:05, gni...@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 we

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

2015-06-02 Thread NIIBE Yutaka
On 05/31/2015 06:25 PM, Moritz Muehlenhoff wrote: > I've configured it on my notebooks for a while now: > > If you install the attached unit file to /usr/lib/systemd/user > the unit can be activated on a per-user basis with > "systemctl --user enable gpg-agent.service" > > (Of course, following t

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

2015-05-31 Thread Werner Koch
Hi, doing a ./configure --enable-standard-socket or at adding use-standard-socket to gpg-agent.conf is much easier and works on all platforms. For 2.1 the standard socket is anyway the only way to connect to gpg-agent. All gpg related tools will start gpg-agent as needed. Salam-Shal

Bug#787313: Systemd user unit for gnupg-agent

2015-05-31 Thread Moritz Muehlenhoff
Package: gnupg-agent Version: 2.0.26-6 Severity: wishlist Tags: patch Hi, I've started to explore how to use more of systemd's functionality for stretch. Beside starting system service systemd also allows to run units on a per-user basis which is a typical use case for gpg-agent. I've configured