Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-07 Thread Daniel Kahn Gillmor
On Tue 2017-02-07 13:00:31 -0500, Yuri D'Elia wrote: > I need to output extra debugging in the cron job, but I need some extra > time to set some testing environment. please report back when you have that info! > For example, does using ssh trigger the creation of the agent now, > simply because

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-07 Thread Yuri D'Elia
On Mon, Feb 06 2017, Daniel Kahn Gillmor wrote: >> gpg --batch -qe -r keyid "$@" > > sure, but what's the "$@" ? Is it guaranteed to be a simple file name? > or could it be more gpg options? I left that out in a copy-paste, but it's empty. There are no extra args to given to gpg that I didn't

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-06 Thread Daniel Kahn Gillmor
On Mon 2017-02-06 11:32:06 -0500, Yuri D'Elia wrote: > On Sat, Feb 04 2017, Daniel Kahn Gillmor wrote: >> Can you give me the exact invocation? If the agent is being >> queried/auto-launched when it doesn't need to be, that'd be something >> worth asking GnuPG upstream to take a look at. > >

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-06 Thread Daniel Kahn Gillmor
On Mon 2017-02-06 12:34:36 -0500, Yuri D'Elia wrote: > On Mon, Feb 06 2017, Michael Biebl wrote: >>> These are all single processes just waiting. >>> So for gpg purposes, the agent is working as intended. >>> However, I'm perplexed as of why I have so many running. >> >> I guess all of this could

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-06 Thread Yuri D'Elia
On Mon, Feb 06 2017, Michael Biebl wrote: >> These are all single processes just waiting. >> So for gpg purposes, the agent is working as intended. >> However, I'm perplexed as of why I have so many running. > > I guess all of this could be solved if gnupg-agent was using > exit-on-idle (with some

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-06 Thread Michael Biebl
Am 06.02.2017 um 17:32 schrieb Yuri D'Elia: > On Sat, Feb 04 2017, Daniel Kahn Gillmor wrote: >> Can you give me the exact invocation? If the agent is being >> queried/auto-launched when it doesn't need to be, that'd be something >> worth asking GnuPG upstream to take a look at. > > Nothing

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-06 Thread Yuri D'Elia
On Sat, Feb 04 2017, Daniel Kahn Gillmor wrote: > Can you give me the exact invocation? If the agent is being > queried/auto-launched when it doesn't need to be, that'd be something > worth asking GnuPG upstream to take a look at. Nothing fancy. The command line is: gpg --batch -qe -r keyid

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-04 Thread Daniel Kahn Gillmor
On Sat 2017-02-04 09:06:12 -0500, Yuri D'Elia wrote: > On Sat, Feb 04 2017, Daniel Kahn Gillmor wrote: >> What are you doing with gpg? if whatever you're doing needs the secret >> keyring, the agent will be launched. if it doesn't need the secret >> keyring, the agent will not be launched. > >

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-04 Thread Yuri D'Elia
On Sat, Feb 04 2017, Daniel Kahn Gillmor wrote: > What are you doing with gpg? if whatever you're doing needs the secret > keyring, the agent will be launched. if it doesn't need the secret > keyring, the agent will not be launched. In one instance, I have a couple of gpg --batch processes that

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-03 Thread Daniel Kahn Gillmor
On Fri 2017-02-03 09:02:47 -0500, Yuri D'Elia wrote: > On Fri, Feb 03 2017, Michael Biebl wrote: >>> When gpg is used via command line, the agent is started automatically >>> and then it's left sitting there. But for a system without seats, the >>> agent doesn't make sense. It shouldn't be

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-03 Thread Yuri D'Elia
On Fri, Feb 03 2017, Michael Biebl wrote: >> When gpg is used via command line, the agent is started automatically >> and then it's left sitting there. But for a system without seats, the >> agent doesn't make sense. It shouldn't be running. > > That doesn't make sense. Even if you stop the

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-03 Thread Michael Biebl
Am 03.02.2017 um 14:45 schrieb Yuri D'Elia: > On Fri, Feb 03 2017, Michael Biebl wrote: >>> I'm quite happy about the listening sockets by default on desktop, but >>> on servers it's exactly the opposite. And masking is currently >> >> What's the problem with having them started on servers? Those

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-03 Thread Yuri D'Elia
On Fri, Feb 03 2017, Michael Biebl wrote: >> I'm quite happy about the listening sockets by default on desktop, but >> on servers it's exactly the opposite. And masking is currently > > What's the problem with having them started on servers? Those are UNIX > sockets, not something which is

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-03 Thread Michael Biebl
Am 03.02.2017 um 13:45 schrieb Yuri D'Elia: > On Fri, Feb 03 2017, Michael Biebl wrote: >>> I wouldn't change anything for stretch and keep the status quo. >> >> And as already said, once we have support for user services in i-s-h, >> this can be revisited post stretch. > > i-s-h? > > So the

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-03 Thread Yuri D'Elia
On Fri, Feb 03 2017, Michael Biebl wrote: >> I wouldn't change anything for stretch and keep the status quo. > > And as already said, once we have support for user services in i-s-h, > this can be revisited post stretch. i-s-h? So the reasoning here is that dh-systemd doesn't support presetting

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-02 Thread Michael Biebl
Am 03.02.2017 um 02:12 schrieb Michael Biebl: > > I wouldn't change anything for stretch and keep the status quo. > And as already said, once we have support for user services in i-s-h, this can be revisited post stretch. -- Why is it that all of the instruments seeking intelligent life in

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-02 Thread Michael Biebl
Am 03.02.2017 um 02:08 schrieb Daniel Kahn Gillmor: > Hi Yuri-- > > On Wed 2017-02-01 17:25:44 -0500, Yuri D'Elia wrote: >> Package: gnupg-agent >> Version: 2.1.18-3 >> Severity: normal >> >> According to upstream, it's incorrect to ship user/sockets.target.wants/* >> files >> directly, as those

Bug#853905: [pkg-gnupg-maint] Bug#853905: Ships incorrect /usr/lib/systemd/user/sockets.target.wants files, makes disabling impossible

2017-02-02 Thread Daniel Kahn Gillmor
Hi Yuri-- On Wed 2017-02-01 17:25:44 -0500, Yuri D'Elia wrote: > Package: gnupg-agent > Version: 2.1.18-3 > Severity: normal > > According to upstream, it's incorrect to ship user/sockets.target.wants/* > files > directly, as those cannot be disabled by the administrator. > > Quote: > > ...