From: Paul Moore <paul.moore@hp.com>
To: Eric Paris <eparis@parisplace.org>
Cc: selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH v1 5/6] selinux: Convert socket related access controls to use socket labels
Date: Tue, 4 May 2010 11:38:17 -0400 [thread overview]
Message-ID: <201005041138.17454.paul.moore@hp.com> (raw)
In-Reply-To: <z2z7e0fb38c1005040730i9918785n488181e55eafa994@mail.gmail.com>
On Tuesday 04 May 2010 10:30:05 am Eric Paris wrote:
> On Mon, May 3, 2010 at 6:11 PM, Paul Moore <paul.moore@hp.com> wrote:
> > At present, the socket related access controls use a mix of inode and
> > socket labels; while there should be no practical difference (they
> > _should_ always be the same), it makes the code more confusing. This
> > patch attempts to convert all of the socket related access control
> > points (with the exception of some of the inode/fd based controls) to
> > use the socket's own label. In the process, I also converted the
> > socket_has_perm() function to take a 'sock' argument instead of a
> > 'socket' since that was adding a bit more overhead in some cases.
>
> Should it be renamed to sock_has_perm() then?
BTW, thanks for the review too ...
Yeah, I can change the name, in fact, I'll do that right now ...
--
paul moore
linux @ hp
--
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.
next prev parent reply other threads:[~2010-05-04 15:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 22:11 [RFC PATCH v1 0/6] UNIX domain socket fixes and other cleanups Paul Moore
2010-05-03 22:11 ` [RFC PATCH v1 1/6] selinux: Update socket's label alongside inode's label Paul Moore
2010-05-04 13:03 ` Stephen Smalley
2010-05-04 15:29 ` Paul Moore
2010-05-03 22:11 ` [RFC PATCH v1 2/6] selinux: Set the peer label correctly on connected UNIX domain sockets Paul Moore
2010-05-04 14:05 ` Stephen Smalley
2010-05-04 14:27 ` Eric Paris
2010-05-04 15:34 ` Paul Moore
2010-05-04 19:47 ` Stephen Smalley
2010-05-05 15:46 ` Paul Moore
2010-05-03 22:11 ` [RFC PATCH v1 3/6] selinux: Consolidate sockcreate_sid logic Paul Moore
2010-05-04 13:52 ` Stephen Smalley
2010-05-04 15:31 ` Paul Moore
2010-05-04 19:44 ` Stephen Smalley
2010-05-05 15:48 ` Paul Moore
2010-05-03 22:11 ` [RFC PATCH v1 4/6] selinux: Shuffle the sk_security_struct alloc and free routines Paul Moore
2010-05-03 22:11 ` [RFC PATCH v1 5/6] selinux: Convert socket related access controls to use socket labels Paul Moore
2010-05-04 14:30 ` Eric Paris
2010-05-04 15:38 ` Paul Moore [this message]
2010-05-03 22:11 ` [RFC PATCH v1 6/6] selinux: Use current_security() when possible 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=201005041138.17454.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=eparis@parisplace.org \
--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.