Re: Symlinks and Cryogenic Sleep

[Casper Dik]

>>When
>>the application reaches the critical section of code between the
>>lstat and the open, you stop it by sending it a SIGSTOP. You record
>>the device and inode number of your /tmp file, remove it, and wait.

The ploy should fail right here: as far as I'm aware, this protection
only works on sticky directories.  In that case, it's not possible to
remove it.

>Maybe I'm just naive, but it's my understanding that you cannot send signals
>to a process you don't own unless you are root.


You can, but only from a terminal. (I.e., if you start su/passwd/rsh,
etc, you can ^Z them)

Casper