Re: [suse-security] strange rm-behaviour
hi list (again), okay, i have learnt something...;-) last question: the "/tmp"-dir is "drwxrwxrwt". is this the reason that "wwwrun" CANNOT remove a "root"-touched and owned file?! regards, daniel -- Aufgepasst - jetzt viele 1&1 New WebHosting Pakete ohne Einrichtungsgebuehr + 1 Monat Grundgebuehrbefreiung! http://puretec.de/index.html?ac=OM.PU.PU003K00736T0492a
The reason is the "t" from "drwxrwxrwt". On Wed, 8 Aug 2001, Daniel Quappe wrote:
hi list (again),
okay, i have learnt something...;-)
last question: the "/tmp"-dir is "drwxrwxrwt". is this the reason that "wwwrun" CANNOT remove a "root"-touched and owned file?!
regards,
daniel
-- Bogdan Zapca Senior System Administrator Dynamic Network Technologies - Cluj, Romania Phone: +40-64-420006 http://www.dntcj.ro
On Wed, Aug 08, 2001 at 05:01:38PM +0200, Daniel Quappe wrote:
last question: the "/tmp"-dir is "drwxrwxrwt". is this the reason that "wwwrun" CANNOT remove a "root"-touched and owned file?!
The "t" at the end of the permission settings (called the sticky bit) deals with exactly the point discussed in the thread. Only the owner of a file may remove it. Important hint: this "sticky bit" behaviour is available on Linux and other UNIX-like operating systems, but not on all of them. E.g. on HP-UX (Hewlett-Packard's UNIX version), the sticky bit does not offer this protection. Best regards, Lutz -- Lutz Jaenicke Lutz.Jaenicke@aet.TU-Cottbus.DE BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/ Lehrstuhl Allgemeine Elektrotechnik Tel. +49 355 69-4129 Universitaetsplatz 3-4, D-03044 Cottbus Fax. +49 355 69-4153
participants (3)
-
Bogdan Zapca -
Daniel Quappe -
Lutz Jaenicke