From: James Morris <jmorris@intercode.com.au>
To: Greg KH <greg@kroah.com>
Cc: Olaf Dietsche <olaf.dietsche--list.linux-kernel@exmail.de>,
<linux-kernel@vger.kernel.org>, <linux-security-module@wirex.com>
Subject: Re: [PATCH] accessfs v0.6 ported to 2.5.35-lsm1 - 1/2
Date: Sun, 29 Sep 2002 22:56:33 +1000 (EST) [thread overview]
Message-ID: <Mutt.LNX.4.44.0209292236200.27145-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <20020927214642.GS12909@kroah.com>
On Fri, 27 Sep 2002, Greg KH wrote:
> On Fri, Sep 27, 2002 at 08:55:52PM +0200, Olaf Dietsche wrote:
> >
> > +static int cap_ip_prot_sock (int port)
> > +{
> > + if (port && port < PROT_SOCK && !capable(CAP_NET_BIND_SERVICE))
> > + return -EACCES;
> > +
> > + return 0;
> > +}
> > +
>
> Do we really want to force all of the security modules to implement this
> logic (yes, it's the same discussion again...)
>
> As for the ip_prot_sock hook in general, does it look ok to the other
> developers?
>
This hook is not necessary: any related access control decision can be
made via the more generic and flexible socket_bind() hook (like SELinux).
- James
--
James Morris
<jmorris@intercode.com.au>
next prev parent reply other threads:[~2002-09-29 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 15:39 [PATCH] accessfs v0.5 ported to LSM " Olaf Dietsche
2002-09-26 20:37 ` Greg KH
2002-09-27 18:55 ` [PATCH] accessfs v0.6 ported to 2.5.35-lsm1 " Olaf Dietsche
2002-09-27 21:46 ` Greg KH
2002-09-27 23:02 ` Olaf Dietsche
2002-09-29 12:56 ` James Morris [this message]
2002-09-29 14:49 ` Olaf Dietsche
2002-09-30 13:14 ` Olaf Dietsche
2002-09-30 8:22 ` Chris Wright
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=Mutt.LNX.4.44.0209292236200.27145-100000@blackbird.intercode.com.au \
--to=jmorris@intercode.com.au \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=olaf.dietsche--list.linux-kernel@exmail.de \
/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
all inboxes | Powered by JetHome®