Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Li,Rongqing" <lirongqing@baidu.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: 答复: [PATCH][RFC] audit: set wait time to zero when audit failed
Date: Thu, 19 Sep 2019 07:12:40 +0000	[thread overview]
Message-ID: <104dff43c31444088b7559a21d73d451@baidu.com> (raw)
In-Reply-To: <20190918223344.3ec262cb@ivy-bridge>



> -----邮件原件-----
> 发件人: Steve Grubb [mailto:sgrubb@redhat.com]
> 发送时间: 2019年9月19日 10:34
> 收件人: Li,Rongqing <lirongqing@baidu.com>
> 抄送: Paul Moore <paul@paul-moore.com>; linux-audit@redhat.com
> 主题: Re: [PATCH][RFC] audit: set wait time to zero when audit failed
> 
> On Thu, 19 Sep 2019 01:50:05 +0000
> "Li,Rongqing" <lirongqing@baidu.com> wrote:
> 
> > No need knobs, auditctl can change the backlog length and wait time.
> > And it is helpless to change the backlog length if auditd is hung
> > forever, as a task can be hung forever due to disk/filesystem's
> > abnormal, etc
> >
> > I am saying the audit default behaviors which is changed, I truly meet
> > the issue as description of the below commit, if we can make change,
> > other can avoid this issue.
> 
> I'd like to offer an opinion because this a long term issue that we have faced
> and what exists is the result of having to meet certain requirements.
> 
> If the machine boots with audit=0, which I think is default, then the end user
> has no expectation of audit ever being in use. Audit events may be discarded if
> the backlog fills up.
> 
> If however the machine boots with audit=1, then the user is expecting that
> there will eventually be an audit daemon and they want all events.
> All of them without fail. So, we have to take all measures to deliver those
> events because this is required by common criteria as well as other security
> standards such as PCI-DSS.
> 

Ok, I see

Thanks

-RongQing


> So, there are 2 paths. One which does not care about audit and one that does.
> The original behavior did not meet requirements. If there is any patch that fixes
> this, it would be to not have an audit backlog wait time if audit has never been
> enabled. We have to be careful to consider audit never enabled, audit disabled
> but previously enabled, and audit enabled.
> 
> HTH...
> 
> -Steve

--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2019-09-19  7:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-12  3:19 [PATCH][RFC] audit: set wait time to zero when audit failed Li RongQing
2019-09-12 13:01 ` Paul Moore
2019-09-16  2:55   ` 答复: " Li,Rongqing
2019-09-16 22:52     ` Paul Moore
2019-09-17  1:08       ` 答复: " Li,Rongqing
2019-09-17 19:16         ` Paul Moore
2019-09-18  1:07           ` 答复: " Li,Rongqing
2019-09-18 12:23             ` Paul Moore
2019-09-19  1:50               ` 答复: " Li,Rongqing
2019-09-19  2:30                 ` Paul Moore
2019-09-19  2:33                 ` Steve Grubb
2019-09-19  7:12                   ` Li,Rongqing [this message]
2019-09-19 14:04                   ` Richard Guy Briggs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=104dff43c31444088b7559a21d73d451@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=linux-audit@redhat.com \
    --cc=sgrubb@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox