public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian <evil@g-house.de>
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: Thu, 02 Oct 2003 12:32:00 +0200	[thread overview]
Message-ID: <3F7BFEA0.8080503@g-house.de> (raw)
In-Reply-To: <1065012013.4078.2.camel@lisaserver>

Lisa R. Nelson wrote:

> [root@localhost root]# cd /
> [root@localhost /]# mkdir junk
> [root@localhost /]# chmod 777 junk

therefore is the sticky bit: users can still create files in the 
directory, but only remove files they are owning:

chmod 1777 /junk

(as your /tmp should be).

do you mean the behaviour has changed for some kernel version? did you 
notice another behaviour with kernel version x.y.?

Thanks,
Christian.



      parent reply	other threads:[~2003-10-02 10:33 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
2003-10-01 17:23     ` Brett
2003-10-01 19:24       ` DervishD
2003-10-02 10:32 ` Christian [this message]

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=3F7BFEA0.8080503@g-house.de \
    --to=evil@g-house.de \
    --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