Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200502235146.GB18570@pi3.com.pl>
Date: Sun, 3 May 2020 01:51:46 +0200
From: Adam Zabrocki <pi3@....com.pl>
To: lkrg-users@...ts.openwall.com
Subject: Re: fake alert (?)

On Sat, May 02, 2020 at 06:54:44PM +0200, Solar Designer wrote:
> On Sat, May 02, 2020 at 06:40:46PM +0200, Adam Zabrocki wrote:
> > Yes, this is normal behaviour. It is nothing to do with LKRG, it just informs 
> > about *_JUMP_LABEL engine activities.
> > 
> > We might change the default log_level from being WARN to ERR. In such case we 
> > won't see messages like that as well.
> > However, I believe that default log_level=WARN is very well balanced. If 
> > someone don't want to see such messages, LKRG can be configured to use 
> > different log_level. It can be done from the beginning via module param.
> 
> I think we should keep the default log level as-is, but avoid logging
> things that are normal as WARN.  They're more reasonably called INFO.
> 

Hm... sure. I will update log level for *_JUMP_LABEL engine.

> Warning means that we think sometimes is likely wrong.  That's not the
> case for jump label modifications.
> 
> Alexander

-- 
pi3 (pi3ki31ny) - pi3 (at) itsec pl
http://pi3.com.pl

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.