From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: Chris Wright <chrisw@osdl.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Filesystem linking protections
Date: Mon, 07 Feb 2005 20:40:43 +0100 [thread overview]
Message-ID: <1107805243.3754.240.camel@localhost.localdomain> (raw)
In-Reply-To: <20050207111235.Y24171@build.pdx.osdl.net>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
El lun, 07-02-2005 a las 11:12 -0800, Chris Wright escribió:
> * Lorenzo Hernández García-Hierro (lorenzo@gnu.org) wrote:
> > This patch adds two checks to do_follow_link() and sys_link(), for
> > prevent users to follow (untrusted) symlinks owned by other users in
> > world-writable +t directories (i.e. /tmp), unless the owner of the
> > symlink is the owner of the directory, users will also not be able to
> > hardlink to files they do not own.
> >
> > The direct advantage of this pretty simple patch is that /tmp races will
> > be prevented.
>
> The disadvantage is that it can break things and places policy in the
> kernel.
It's just like DAC then, because it never applies any policy than a
simple check relying on kernel's DAC, and standard capabilities &
permissions.DAC-related checks are placed all over the place, but maybe
the place is lacking of some ones that may be important.
About what things it can break, I haven't noticed any issue on it (at
least regarding grSecurity or OpenWall), but of course I would
appreciate a lot any information on them, so, I could report to the
developers that are currently using this in their own solutions.
Thanks in advance,
Cheers.
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org>
[1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-07 19:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 18:57 [PATCH] Filesystem linking protections Lorenzo Hernández García-Hierro
2005-02-07 19:12 ` Chris Wright
2005-02-07 19:40 ` Lorenzo Hernández García-Hierro [this message]
2005-02-07 20:00 ` Chris Wright
2005-02-07 19:43 ` John Richard Moser
2005-02-07 20:05 ` Chris Wright
2005-02-07 22:29 ` John Richard Moser
2005-02-07 22:47 ` Chris Wright
2005-02-08 2:10 ` John Richard Moser
2005-02-07 19:14 ` Valdis.Kletnieks
2005-02-07 19:34 ` Lorenzo Hernández García-Hierro
2005-02-07 21:45 ` Valdis.Kletnieks
2005-02-07 22:00 ` Lorenzo Hernández García-Hierro
2005-02-07 22:13 ` Valdis.Kletnieks
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=1107805243.3754.240.camel@localhost.localdomain \
--to=lorenzo@gnu.org \
--cc=chrisw@osdl.org \
--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.