On Tue, Jul 06, 2010 at 06:26:10PM -0700, Russ Allbery wrote:
I wonder if the right way of handling this would be to instead install a
logcheck rule as part of the libpam-krb5 package that looks something
like:
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ [[:alnum:]]+(\[[0-9]+\])?:
Michel Messerschmidt wrote:
On Tue, Jul 06, 2010 at 06:26:10PM -0700, Russ Allbery wrote:
I wonder if the right way of handling this would be to instead install a
logcheck rule as part of the libpam-krb5 package that looks something
like:
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+
On Tue, Jul 06, 2010 at 06:26:10PM -0700, Russ Allbery wrote:
I wonder if the right way of handling this would be to instead install a
logcheck rule as part of the libpam-krb5 package that looks something
This would be the preferred solution for me.
I just haven't found a way to configure
Michel Messerschmidt li...@michel-messerschmidt.de writes:
On Tue, Jul 06, 2010 at 06:26:10PM -0700, Russ Allbery wrote:
I wonder if the right way of handling this would be to instead install a
logcheck rule as part of the libpam-krb5 package that looks something
This would be the preferred
Michel Messerschmidt li...@michel-messerschmidt.de writes:
Many of my logcheck reports are triggered by regular user authentication
against kerberos enabled services.
Here are rules to ignore authentication success messages for some common
daemons.
violations.ignore.d/logcheck-sudo:
^\w{3}
5 matches
Mail list logo
