From: Andreas Schwab <schwab@suse.de>
To: root@chaos.analogic.com
Cc: Jurjen Oskam <jurjen@stupendous.org>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: File Permissions are incorrect. Security flaw in Linux
Date: Wed, 01 Oct 2003 16:22:15 +0200 [thread overview]
Message-ID: <jer81x82co.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0310011004570.3612@chaos> (Richard B. Johnson's message of "Wed, 1 Oct 2003 10:09:51 -0400 (EDT)")
"Richard B. Johnson" <root@chaos.analogic.com> writes:
> ...So anything you put into "/tmp", for instance, can be deleted
> by anybody. This is the Unix way.
...Unless your /tmp is marked properly with +t (sticky bit), so that you
can only delete your own files.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-10-01 14:22 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 [this message]
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=jer81x82co.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=jurjen@stupendous.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.