> 
> >Number:         2634
> >Category:       misc
> >Synopsis:       /usr/sbin/chroot is doomed
> >Confidential:   no
> >Severity:       critical
> >Priority:       medium
> >Responsible:    misc-bug-people (Misc Bug People)
> >State:          open
> >Class:          sw-bug
> >Submitter-Id:   net
> >Arrival-Date:   Tue Jul 16 02:35:00 1996
> >Last-Modified:
> >Originator:     Daniel G. Pouzzner
> >Organization:
> just me
> >Release:        1.2A
> >Environment:
> >Description:
>      hey guys, /usr/sbin/chroot can not possibly work out.
> if it ever leaves experimental status and goes setuid in a release,
> here is what will happen:
> 
> -hacker would find a setuid-root program on a partition he has write
> on.

Why would it go suid? In all the other OS's I checked chroot is NOT suid
and it makes no sense to do so. chroot is for use by root privleged
programs, if a hacker could use it effectively then they already have root
and all is lost anyhow!

-Rob