Messages in this thread | | | Date | Tue, 23 Mar 1999 11:17:32 -0500 | From | Arvind Sankar <> | Subject | Re: [RFC] Rights for hardlinks |
| |
On Tue, Mar 23, 1999 at 10:11:08AM -0500, Alexander Viro wrote: > > Access != write permissions.
I think he has a point, though. You can hardlink even to a file with 0 perms. Such files are immune to the open trick you mention below, but the only way to get around the linking would be to first create a 700 directory in /tmp and export TMPDIR=/tmp/foo. This requires trickery in your .profile to find a suitable foo.
> IMO it's madness. If you are in hostile environment (malicious > local users) you can (and should) make your homedir accessible only for > you. The only other place you could care of is /tmp. Needs regular > cleanups on any box. > Notice that malicious user can simply *open* the files and there > is nothing you can do with them. Even if you unlink them they'll stay > around until the attacker will want to close them. Your point being? > Uptimes up to hundreds of days are *good* thing on a multi-user box.
see above...
-- arvind
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |