From: xystrus <xystrus@haxm.com>
To: linux-kernel@vger.kernel.org
Subject: Re: link() security
Date: Sat, 13 Apr 2002 13:02:33 -0400 [thread overview]
Message-ID: <20020413130233.A4743@pizzashack.org> (raw)
In-Reply-To: <20020411181524.A1463@figure1.int.wirex.com> <E16wQsU-0000cb-00@the-village.bc.nu>
On Sat, Apr 13, 2002 at 05:59:54PM +0100, Alan Cox wrote:
> > http://openwall.com. Work based on Solar Designer's Openwall patch has
> > been brought forward to more recent 2.4 and 2.5 kernels. Both the
> > following projects implement the Openwall secure link feature:
> >
> > http://grsecurity.net
> > http://lsm.immunix.org
> >
> > This can break some applications that make assumptions wrt. link(2)
> > (Courier MTA for example).
>
> How practical is it to make this a mount option and to do so cleanly ?
Perhaps two options: one to allow creation of the link only when the
UIDs match; and the other to allow the link when GIDs match, to keep
Courier happy?
next prev parent reply other threads:[~2002-04-13 17:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 23:21 link() security xystrus
2002-04-12 1:15 ` Chris Wright
2002-04-13 16:59 ` Alan Cox
2002-04-13 17:02 ` xystrus [this message]
2002-04-14 1:49 ` Chris Wright
2002-04-15 14:44 ` Patrick J. LoPresti
2002-04-15 19:25 ` H. Peter Anvin
2002-04-15 22:48 ` Alan Cox
2002-04-15 23:05 ` H. Peter Anvin
2002-04-15 23:28 ` Alan Cox
2002-04-15 23:14 ` H. Peter Anvin
2002-04-16 0:01 ` Kurt Wall
2002-04-15 21:41 ` xystrus
2002-05-06 5:00 ` Albert D. Cahalan
-- strict thread matches above, loose matches on Subject: below --
2002-04-13 17:48 Hank Leininger
2002-04-15 19:36 Chris Adams
2002-04-15 19:55 ` H. Peter Anvin
2002-04-15 20:36 ` Patrick J. LoPresti
2002-04-16 1:37 ` H. Peter Anvin
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=20020413130233.A4743@pizzashack.org \
--to=xystrus@haxm.com \
--cc=linux-kernel@vger.kernel.org \
/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.