Daniel Kahn Gillmor , 2017-02-28 16:12 -0800:
> ...
> Sure, i'd be happy to accept reasonable logcheck filters to the
> gpg-agent and dirmngr binary packages. Please submit a separate bug
> report with the suggested filters, and i'll review them and roll them
> into the
On Tue 2017-02-28 13:04:15 -0800, Michael[tm] Smith wrote:
> OK one small very concrete thing I think would help would be if the package
> added logcheck filters for messages the change has caused to now start
> getting logged to syslog in the following form:
>
> Feb 17 01:24:15 sideshowbarker
Daniel Kahn Gillmor , 2017-02-21 10:18 -0500:
> On Mon 2017-02-20 23:11:56 -0500, Michael[tm] Smith wrote:
...
> if there's nothing concretely wrong with current defaults, please stick
> with them, rather than changing them gratuitously (or encouraging others
> to do so).
On Mon 2017-02-20 23:11:56 -0500, Michael[tm] Smith wrote:
> Yes, but how is that any different from the state my system was in
> before the change was made in 2.1.17 to have systemd automatically
> launch gpg-agent?
>
> I mean, the way it worked previously caused no observable problems for
> me.
Daniel Kahn Gillmor , 2017-02-20 15:27 -0500:
> On Sun 2017-02-19 21:20:52 -0500, Michael[tm] Smith wrote:
> > "Michael[tm] Smith" , 2017-02-20 11:11 +0900:
> >
> > Can you confirm what the exact command is for globally disabling the
> > gpg-agent
> > user
On Sun 2017-02-19 21:20:52 -0500, Michael[tm] Smith wrote:
> "Michael[tm] Smith" , 2017-02-20 11:11 +0900:
>>
>> Can you confirm what the exact command is for globally disabling the
>> gpg-agent
>> user service? Is it the following?
>>
>> systemctl --global --user mask --now
6 matches
Mail list logo