From: Olaf Dietsche <olaf.dietsche--list.linux-security-module@exmail.de>
To: James Morris <jmorris@intercode.com.au>
Cc: Greg KH <greg@kroah.com>, <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 16:49:12 +0200 [thread overview]
Message-ID: <87it0o4zrr.fsf@goat.bogus.local> (raw)
In-Reply-To: Mutt.LNX.4.44.0209292236200.27145-100000@blackbird.intercode.com.au
James Morris <jmorris@intercode.com.au> writes:
> On Fri, 27 Sep 2002, Greg KH wrote:
>
>> 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).
AFAICS, it looks like you can make _additional_ checks only. You still
have to grant CAP_NET_BIND_SERVICE for binding to ports below PROT_SOCK.
So, this doesn't look like a viable solution for me.
Anyway, thanks for this pointer, I'll look into socket_bind().
Regards, Olaf.
next prev parent reply other threads:[~2002-09-29 14:44 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 - 1/2 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
2002-09-29 14:49 ` Olaf Dietsche [this message]
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=87it0o4zrr.fsf@goat.bogus.local \
--to=olaf.dietsche--list.linux-security-module@exmail.de \
--cc=greg@kroah.com \
--cc=jmorris@intercode.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.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