Subject: Re: Symlink ownership
To: Kenneth Stailey <firstname.lastname@example.org>
From: John F. Woods <email@example.com>
Date: 08/04/1995 10:43:36
> That means I should want to create links that I can't remove. Problem
> is I don't want to be able to make things I can't remove.
You can't (really) prevent this:
[Your terminal] [Root's terminal]
$ cd /var/tmp
$ ln /var/log/messages foo
# chmod a-w /var/tmp
$ rm foo
That's a more unusual kind of failure, but the same kind of argument could
apply: "Hey, it's MY link, I put it there, I should be able to remove it!
Changing the directory's write permission shouldn't affect *my* link!"
After all, if I open a file with creat() and leave it open in my process,
my permission to write the file cannot be taken away by changing the access
modes on the file. (Uh-oh, except for that foul excresence of a file system,
NFS: is the UFS going to have to be damaged to allow NFS not to feel like
a second-class citizen?)
I'm fond of neither symlinks-in-directories nor sticky directories, but I
don't hink the above problem is a convincing argument against either way.