From: Paul Moore <paul.moore@hp.com>
To: etienne <etienne.basset@numericable.fr>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
LSM <linux-security-module@vger.kernel.org>,
Dmitriy Romashkin <dmitriy.romashkin@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PACH][RFC] SMACK : add logging support V1
Date: Sat, 7 Mar 2009 16:46:40 -0500 [thread overview]
Message-ID: <200903071646.40839.paul.moore@hp.com> (raw)
In-Reply-To: <49B27134.2020103@numericable.fr>
On Saturday 07 March 2009 08:05:56 am etienne wrote:
> Hello,
>
> the following patch, against current 2.6.29-rc7, add logging of smack
> decisions. This is of course very useful to understand what your current
> smack policy does. It borrows a lot from selinux;
>
> It introduces a '/smack/logging' switch :
> 0: no logging
> 1: log denied (default)
> 2: log accepted
> 3: log denied&accepted
>
>
> example of logs produced :
>
> type=1400 audit(1236429348.858:5655879): SMACK[smack_task_kill]: denied
> pid=6521 comm="bash" subject:'toto' object:'_' requested:w pid=5757
> comm="knetworkmanager" type=1400 audit(1236429361.477:5655882):
> SMACK[smk_curacc_shm]: denied pid=6533 comm="ipcrm" subject:'toto'
> object:'_' requested:rw key=491521 type=1400 audit(1236429392.389:5655885):
> SMACK[smack_sb_mount]: denied pid=6536 comm="mount" subject:'toto'
> object:'_' requested:w path="/debug" dev=sda5 ino=16161 type=1400
> audit(1236429485.009:5655890): SMACK[smack_ptrace_may_access]: denied
> pid=6539 comm="strace" subject:'toto' object:'_' requested:rw pid=5634
> comm="python" type=1400 audit(1236429527.693:5655893):
> SMACK[smack_inode_getattr]: denied pid=6544 comm="ls" subject:'toto'
> object:'etienne' requested:r path="/home/etienne/linux" dev=sda8
> ino=2342913 type=1400 audit(1236429741.006:6006665):
> SMACK[smack_socket_sendmsg]: granted pid=6580 comm="ping" subject:'toto'
> object:'@' requested:w daddr=192.168.0.10 type=1400
> audit(1236429741.006:6006666): SMACK[smack_socket_sock_rcv_skb]: granted
> pid=6580 comm="ping" subject:'@' object:'toto' requested:w
> saddr=192.168.0.10 daddr=192.168.0.10 netif=lo
You will want to send this to the audit mailing list (linux-audit@redhat.com)
for review, I suspect they will have several comments.
--
paul moore
linux @ hp
prev parent reply other threads:[~2009-03-07 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 13:05 [PACH][RFC] SMACK : add logging support V1 etienne
2009-03-07 21:46 ` Paul Moore [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=200903071646.40839.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=casey@schaufler-ca.com \
--cc=dmitriy.romashkin@gmail.com \
--cc=etienne.basset@numericable.fr \
--cc=linux-kernel@vger.kernel.org \
--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