All of lore.kernel.org
 help / color / mirror / Atom feed
From: viro@parcelfarce.linux.theplanet.co.uk
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:40:40 +0100	[thread overview]
Message-ID: <20031001154040.GU7665@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1065017722.2995.10.camel@localhost.localdomain>

On Wed, Oct 01, 2003 at 08:15:23AM -0600, Lisa R. Nelson wrote:
> Excuse me? Have you even read about permissions on Unix?  I tried this
> on a Sun Unix system, and the Sun functions correctly.  What you are
> saying is stupid; If all directories are wide open, NO files are
> protected in any way, even if they are read only and owned by root?  Get
> real.  

What, create a world-writable directory without sticky bit and then wonder
why everyone can remove files from there?

Would you mind posting the list of systems (with versions, preferably)
where that behaviour would *not* match v7, 2.xBSD, 4.xBSD and derivatives
(including SunOS 4), SunOS 5.5, SunOS 5.6, SunOS 5.7,  SunOS 5.8, Linux,
OSF/1, etc.?

In particular, I'm most curious about the exact version of "Sun Unix"
you claim to have tried that on.  That, and output of ls -ld on the
directory in question.

> I've worked on more OS's than you can imagine, and for many years.  This

The sad thing being, that's one claim I do *not* doubt.  Lusers' ability
to avoid learning for years had stopped amazing me a long time ago...

  parent reply	other threads:[~2003-10-01 15:40 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 [this message]
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
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=20031001154040.GU7665@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --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 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.