From: DervishD <raul@pleyades.net>
To: "Lisa R. Nelson" <lisanels@cableone.net>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: File Permissions are incorrect. Security flaw in Linux
Date: Wed, 1 Oct 2003 16:21:25 +0200 [thread overview]
Message-ID: <20031001142125.GA14994@DervishD> (raw)
In-Reply-To: <1065012013.4078.2.camel@lisaserver>
Hi Lisa :)
* Lisa R. Nelson <lisanels@cableone.net> dixit:
> [1.] One line summary of the problem:
> A low level user can delete a file owned by root and belonging to group
> root even if the files permissions are 744. This is not in agreement
> with Unix, and is a major security issue.
You're not right here: all Unices I have knowledge about has this
same scheme. But really it doesn't matter, because the reason behind
this is that files are just links in a directory, so for deleting a
file, that is, *unlinking* it, you need to have write permission on
the *container*: the directory.
> Permissions on a file basis take precedence over directory
> permissions (for most cases), but in Linux they do not.
Just curiosity: which Unix behaves that way?
> In order to secure a file, you have to secure the directory which
> effects all files within it.
Not exactly, but you're true. You can use the sticky bit for
directories if you want them to be 'append only'. This way anybody
can read your files if you want, add files and remove them, *but*
they WON'T be able to delete YOUR files. This is used in /tmp, for
example.
> I verified this on a sun station today
I may be wrong here, for a long time has passed since I last used
a SparcStation or similar, but AFAIK SunOS behaves like Linux in this
issue. In fact, this is the common Unix behaviour.
> http://www.auburn.edu/oit/software/os/unix_files.html
Quote: "Permissions are divided into three types [...] Write
permission allows the user [...] For directories, write permission
allows the user to create new files or delete files within that
directory".
> http://www.dartmouth.edu/~rc/help/faq/permissions.html
The same: "w [...] file is writeable. On a directory, write
access means you can add or delete files".
> http://www.december.com/unix/tutor/permissions.html
Nothing relevant. A lame tutorial on Unix permissions, BTW.
> http://www.itc.virginia.edu/desktop/web/permissions/
"Write [...] create a new file in the directory". Incomplete, but
will do...
As you can see, even your sources say exactly the same...
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
next prev parent reply other threads:[~2003-10-01 14:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 12:40 File Permissions are incorrect. Security flaw in Linux Lisa R. Nelson
2003-10-01 13:08 ` Måns Rullgård
2003-10-01 13:08 ` Mathieu Chouquet-Stringer
2003-10-01 13:23 ` viro
[not found] ` <1065017722.2995.10.camel@localhost.localdomain>
2003-10-01 15:40 ` viro
2003-10-01 19:27 ` DervishD
2003-10-01 13:53 ` Jurjen Oskam
2003-10-01 14:09 ` Richard B. Johnson
2003-10-01 14:22 ` Andreas Schwab
2003-10-01 15:01 ` John Bradford
2003-10-01 13:58 ` Felipe Alfaro Solana
2003-10-01 14:21 ` DervishD [this message]
[not found] ` <1065044031.2158.23.camel@wynken.reefedge.com>
2003-10-01 14:37 ` Lisa R. Nelson
2003-10-01 15:11 ` Bas Mevissen
2003-10-01 15:12 ` Randy.Dunlap
2003-10-01 16:08 ` Richard B. Johnson
2003-10-01 19:21 ` DervishD
2003-10-01 20:30 ` viro
2003-10-01 17:23 ` Brett
2003-10-01 19:24 ` DervishD
2003-10-02 10:32 ` Christian
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=20031001142125.GA14994@DervishD \
--to=raul@pleyades.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lisanels@cableone.net \
/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