From: Steve Grubb <sgrubb@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: paul.moore@hp.com, redhat-lspp@redhat.com, selinux@tycho.nsa.gov,
linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
sds@epoch.ncsc.mil, jmorris@redhat.com
Subject: Re: [RFC 2/7] NetLabel: core network changes
Date: Thu, 22 Jun 2006 11:05:00 -0400 [thread overview]
Message-ID: <200606221105.00331.sgrubb@redhat.com> (raw)
In-Reply-To: <20060622.020055.115910616.davem@davemloft.net>
On Thursday 22 June 2006 05:00, David Miller wrote:
> > #define NETLINK_GENERIC 16
> > +#define NETLINK_NETLABEL 17 /* Network packet labeling */
> >
> > #define MAX_LINKS 32
>
> Please use generic netlink.
Since this is a security interface, shouldn't it be its own protocol so that
SE Linux can control commands being sent? Paul's patches do include a netlink
table in security/selinux/nlmsgtab.c. But I do not see any hooks to control
generic netlink messages. (There seems to be several protocols that SE Linux
is not controlling.) I could see that someone in secadm role should be able
to issue these commands, but someone at sysadm or auditadm would not.
If moving this over to generic is a must, then I think SE Linux will have to
clip into generic to control its packet flow.
-Steve
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
WARNING: multiple messages have this Message-ID (diff)
From: Steve Grubb <sgrubb@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: jmorris@redhat.com, paul.moore@hp.com, sds@epoch.ncsc.mil,
redhat-lspp@redhat.com, linux-security-module@vger.kernel.org,
selinux@tycho.nsa.gov, netdev@vger.kernel.org
Subject: Re: [RFC 2/7] NetLabel: core network changes
Date: Thu, 22 Jun 2006 11:05:00 -0400 [thread overview]
Message-ID: <200606221105.00331.sgrubb@redhat.com> (raw)
In-Reply-To: <20060622.020055.115910616.davem@davemloft.net>
On Thursday 22 June 2006 05:00, David Miller wrote:
> > #define NETLINK_GENERIC 16
> > +#define NETLINK_NETLABEL 17 /* Network packet labeling */
> >
> > #define MAX_LINKS 32
>
> Please use generic netlink.
Since this is a security interface, shouldn't it be its own protocol so that
SE Linux can control commands being sent? Paul's patches do include a netlink
table in security/selinux/nlmsgtab.c. But I do not see any hooks to control
generic netlink messages. (There seems to be several protocols that SE Linux
is not controlling.) I could see that someone in secadm role should be able
to issue these commands, but someone at sysadm or auditadm would not.
If moving this over to generic is a must, then I think SE Linux will have to
clip into generic to control its packet flow.
-Steve
next prev parent reply other threads:[~2006-06-22 15:05 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 19:42 [RFC 0/7] Updated NetLabel patch paul.moore
2006-06-21 19:42 ` paul.moore
2006-06-21 19:42 ` [RFC 1/7] NetLabel: documentation paul.moore
2006-06-21 19:42 ` paul.moore
2006-06-21 19:42 ` [RFC 2/7] NetLabel: core network changes paul.moore
2006-06-21 19:42 ` paul.moore
2006-06-22 9:00 ` David Miller
2006-06-22 15:05 ` Steve Grubb [this message]
2006-06-22 15:05 ` Steve Grubb
2006-06-22 18:58 ` James Morris
2006-06-22 21:32 ` David Miller
2006-06-22 9:07 ` David Miller
2006-06-22 13:20 ` Paul Moore
2006-06-22 13:20 ` Paul Moore
2006-06-21 19:42 ` [RFC 3/7] NetLabel: CIPSOv4 engine paul.moore
2006-06-21 19:42 ` paul.moore
2006-06-22 9:12 ` David Miller
2006-06-22 13:43 ` Paul Moore
2006-06-22 13:43 ` Paul Moore
2006-06-22 15:57 ` Ryan Pratt
2006-06-23 18:48 ` Ted
2006-06-23 20:15 ` David Miller
2006-06-23 20:34 ` Ted
2006-06-23 23:24 ` James Morris
2006-06-23 23:45 ` Paul Moore
2006-06-26 15:32 ` James Morris
2006-06-26 23:14 ` [redhat-lspp] " Joe Nall
2006-06-26 23:14 ` Joe Nall
2006-06-27 0:33 ` James Morris
2006-06-27 0:33 ` James Morris
2006-06-27 2:45 ` Paul Moore
2006-06-27 2:45 ` Paul Moore
2006-06-27 19:41 ` Klaus Weidner
2006-06-27 19:41 ` Klaus Weidner
2006-06-21 19:42 ` [RFC 4/7] NetLabel: core NetLabel subsystem paul.moore
2006-06-21 19:42 ` paul.moore
2006-06-21 21:15 ` Steve Grubb
2006-06-21 21:24 ` [redhat-lspp] " Paul Moore
2006-06-21 21:26 ` Steve Grubb
2006-06-21 19:42 ` [RFC 5/7] NetLabel: SELinux support paul.moore
2006-06-21 19:42 ` paul.moore
2006-06-21 19:42 ` [RFC 6/7] NetLabel: CIPSOv4 integration paul.moore
2006-06-21 19:42 ` paul.moore
2006-06-21 19:42 ` [RFC 7/7] NetLabel: unlabeled packet handling paul.moore
2006-06-21 19:42 ` 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=200606221105.00331.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=davem@davemloft.net \
--cc=jmorris@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=redhat-lspp@redhat.com \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@tycho.nsa.gov \
/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.