All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deepika Sundar <sundar.deepika18@gmail.com>
To: linux-audit@redhat.com
Subject: Re: New field to auditd.conf file
Date: Wed, 6 Apr 2016 17:25:36 +0530	[thread overview]
Message-ID: <CAHj_pNf9Ktnz2ZThwWK+YTHKWZYiY0RE1UzmU6inv8A0jNz_ug@mail.gmail.com> (raw)
In-Reply-To: <2428041.aDPSTkrCU6@x2>


[-- Attachment #1.1: Type: text/plain, Size: 501 bytes --]

Ok.If i wanted to add the new field to experiment on the requirement, which
are the files(programs) that need changes or  to be updated to take effect
on new field in auditd.conf?

On Wed, Apr 6, 2016 at 5:20 PM, Steve Grubb <sgrubb@redhat.com> wrote:

> On Wednesday, April 06, 2016 05:06:08 PM Deepika Sundar wrote:
> > Can it be possible to add new field to auditd.conf file?
>
> That depends entirely on what functionality is being added and if its
> acceptable to people in general.
>
> -Steve
>

[-- Attachment #1.2: Type: text/html, Size: 884 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2016-04-06 11:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06 11:36 New field to auditd.conf file Deepika Sundar
2016-04-06 11:50 ` Steve Grubb
2016-04-06 11:55   ` Deepika Sundar [this message]
2016-04-06 12:17     ` Steve Grubb
2016-04-07  4:47       ` Deepika Sundar
2016-04-07 18:42         ` Paul Moore
2016-04-13  5:33           ` Deepika Sundar
2016-04-13 12:31             ` Steve Grubb
2016-04-20  4:35               ` Deepika Sundar
2016-04-20 12:30                 ` Steve Grubb
2016-04-21  5:25                   ` Deepika Sundar
2016-04-21 12:58                     ` Paul Moore
2016-04-25  6:56                       ` Deepika Sundar
2016-04-26  0:37                         ` Richard Guy Briggs
2016-04-28  5:59                           ` Deepika Sundar
2016-04-29  2:47                             ` 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=CAHj_pNf9Ktnz2ZThwWK+YTHKWZYiY0RE1UzmU6inv8A0jNz_ug@mail.gmail.com \
    --to=sundar.deepika18@gmail.com \
    --cc=linux-audit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.