public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Etienne Basset <etienne.basset@numericable.fr>
To: Eric Paris <eparis@redhat.com>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
	LSM <linux-security-module@vger.kernel.org>,
	linux-audit@redhat.com
Subject: Re: [PATCH 2/2] security/smack implement logging V3
Date: Mon, 13 Apr 2009 21:39:40 +0200	[thread overview]
Message-ID: <49E394FC.5040805@numericable.fr> (raw)
In-Reply-To: <1239648807.4320.4.camel@localhost.localdomain>

Eric Paris wrote:
> On Wed, 2009-04-08 at 20:40 +0200, Etienne Basset wrote:
>> the following patch, add logging of Smack security decisions. 
>> This is of course very useful to understand what your current smack policy does.
>> As suggested by Casey, it also now forbids labels with ', " or \
>>
>> It introduces a '/smack/logging' switch :
>> 0: no logging
>> 1: log denied (default)
>> 2: log accepted 
>> 3: log denied&accepted 
>>
>>
>> Signed-off-by: Etienne Basset <etienne.basset@numericable.fr>
> 
> Acked-by: Eric Paris <eparis@redhat.com>
> 
thanks!

> I don't think it's worth doing now, but if for some reason you have to
> make another round....
> 
> smk_ad_setfield_u_tsk and friends could be generic functions since
> SELinux could use them just as well to clear up some of their code.
> 

well, we need these in Smack to cover the !CONFIG_AUDIT case
Since SELinux does depend on AUDIT, i dont think they will need this

regards
Etienne



      reply	other threads:[~2009-04-13 19:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 18:40 [PATCH 2/2] security/smack implement logging V3 Etienne Basset
2009-04-11  3:28 ` Casey Schaufler
2009-04-13 18:53 ` Eric Paris
2009-04-13 19:39   ` Etienne Basset [this message]

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=49E394FC.5040805@numericable.fr \
    --to=etienne.basset@numericable.fr \
    --cc=casey@schaufler-ca.com \
    --cc=eparis@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-security-module@vger.kernel.org \
    /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