From: Paul Moore <paul.moore@hp.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Correct audit field for a netmask?
Date: Fri, 16 Nov 2007 11:25:21 -0500 [thread overview]
Message-ID: <200711161125.21373.paul.moore@hp.com> (raw)
In-Reply-To: <200711161110.56596.sgrubb@redhat.com>
On Friday 16 November 2007 11:10:55 am Steve Grubb wrote:
> On Thursday 15 November 2007 16:12:53 Paul Moore wrote:
> > I was wondering what was the correct way to send a netmask in an audit
> > message?
>
> That is a curious one. I don't think we've ever recorded a netmask since we
> don't audit the routing tables. How does this net mask get used in a way
> that needs to be audited. Just curious. :)
It's not a routing table, but rather an IP selector/filter used to assign
static/fallback security labels to incoming traffic. There has been a lot of
discussion about this on the SELinux list over the summer and RFC patches
have been available for a week or two, the audit relevant patch is below
(once we get these issues resolved I'll respin the audit patch and send it
here for review):
* http://marc.info/?l=linux-security-module&m=119514613623937&w=2
> > Or is there some other field specifically for the netmask?
> >
> > addr=10.0.0.0 X=8
>
> This would probably be better so that extra parsing of the value is not
> needed. I'd suggest something short like "net" to save diskspace.
Okay, so for single addresses we should still go with "addr":
addr=10.0.0.1
... but for networks we should go with "net":
net=10.0.0.0/8
?
--
paul moore
linux security @ hp
next prev parent reply other threads:[~2007-11-16 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 21:12 Correct audit field for a netmask? Paul Moore
2007-11-16 16:10 ` Steve Grubb
2007-11-16 16:25 ` Paul Moore [this message]
2007-11-17 0:07 ` Casey Schaufler
2007-11-17 0:14 ` Paul Moore
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=200711161125.21373.paul.moore@hp.com \
--to=paul.moore@hp.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;
as well as URLs for NNTP newsgroup(s).