From: viro@parcelfarce.linux.theplanet.co.uk
To: DervishD <raul@pleyades.net>
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
"Lisa R. Nelson" <lisanels@cableone.net>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: File Permissions are incorrect. Security flaw in Linux
Date: Wed, 1 Oct 2003 21:30:20 +0100 [thread overview]
Message-ID: <20031001203019.GX7665@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20031001192126.GB22367@DervishD>
On Wed, Oct 01, 2003 at 09:21:26PM +0200, DervishD wrote:
> If someone answers me something like "you are much of a dumb for
> understanding the answer, so I'll just tell you that you're wrong"
> (and believe me, that 'joke' about a well earned F in Unix 101 falls
> in this category IMHO), I wouldn't bother to thank...
You know, it's really not a joke. Permissions model and meanings of
individual permission bits *is* Unix 101 material and not knowing it
(let alone claiming behaviour contrary to reality) will, indeed, earn
you F.
To be completely blunt, original posting contained a lie. Given sequence
of operations had not been tried on "Sun Unix". At all. Everything else
would not get a reaction harsher than "you are thinking about behaviour
of directories with sticky bit set; without it write permissions on directory
are sufficient to remove files in it". Probably with reference to Unix FAQ
(and maybe a nitpick to the above - append-only and immutable files are
not removable).
9:1 says that all original poster had actually tried was rm /tmp/<something>
on Solaris, which, of course, resulted in "permission denied". The rest was
extrapolation. Which is not particulary endearing, to put it mildly.
The way original poster had reacted to replies ("You are all wrong,
I Know(tm)") + reference to Great Experience(tm)(r) had warranted the
rest, IMO.
And yes, we all screw up from time to time. Which is OK, provided that
when said screwup is noticed you admit it instead of throwing a temper
tantrum.
next prev parent reply other threads:[~2003-10-01 20:30 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
[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 [this message]
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=20031001203019.GX7665@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lisanels@cableone.net \
--cc=raul@pleyades.net \
--cc=root@chaos.analogic.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