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 systemd[1246]: Listening on GnuPG
> cryptographic agent and passphrase cache.
> Feb 17 01:24:15 sideshowbarker systemd[1246]: Listening on GnuPG network
> certificate management daemon.
> Feb 17 01:24:15 sideshowbarker systemd[1246]: Listening on GnuPG
> cryptographic agent and passphrase cache (restricted).
> Feb 17 01:24:15 sideshowbarker systemd[1246]: Listening on GnuPG
> cryptographic agent (access for web browsers).
> Feb 17 01:24:15 sideshowbarker systemd[1246]: Listening on GnuPG
> cryptographic agent (ssh-agent emulation).
> Feb 17 01:24:16 sideshowbarker systemd[1246]: Closed GnuPG network
> certificate management daemon.
> Feb 17 01:24:16 sideshowbarker systemd[1246]: Closed GnuPG cryptographic
> agent and passphrase cache.
> Feb 17 01:24:16 sideshowbarker systemd[1246]: Closed GnuPG cryptographic
> agent and passphrase cache (restricted).
> Feb 17 01:24:16 sideshowbarker systemd[1246]: Closed GnuPG cryptographic
> agent (ssh-agent emulation).
> Feb 17 01:24:16 sideshowbarker systemd[1246]: Closed GnuPG cryptographic
> agent (access for web browsers).
>
> Would it be possible for the package maintainers to add logcheck filters
> for those? Should I file a separate bug to request that?
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 next release.
All the best,
--dkg
