/dev/full
Darin Johnson (darin@connectnet.com)
Wed, 10 Sep 1997 20:34:04 -0700 (PDT)
Ah, I see now. Too much stress at work. The problem is the
crackers exploiting an *existing* setuid program by making them read
/dev/full, not in them writing their own setuid program. I can see
major problems now...