search for: varlinks

...: a user process shouldn''t be able to set the policy on expansion of a varlink which a root process is going to use, and secondly back to the basics, it doesn''t stop filesystem races. > Your private namespace is specifically geared towards this one > problem. Once you have varlinks you''ll find that they are quite a > useful feature, which not only works for /tmp .... You seem to like these varlinks a lot. I don''t have any problem with the idea of varlinks. I don''t see them as a security fix though. Varlinks could be quite useful for unprivileged...

Hi everyone, Thanks all for your feedback. Here is a reply to most of your comments.... Roger. Chris Evans wrote: > On Mon, 9 Mar 1998, Rogier Wolff wrote: > > not to give those rights away. A non-setuid program should not have to > > worry about buffer overruns (you can crash the program, wow!). It > Just a reminder, that in some cases, it _should_ worry. As a

Introduction. ------------ Every now and then a new "exploit" turns up of some program that uses tmp files. The first solution was "sticky bits", but since links exist (that''s a LONG time), that solution is inadequate. Discussion. ---------- The problem is that you put an object (link/pipe) in the place where you expect a program to put its tempfile, and wait for