Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:2602 comp.os.386bsd.questions:14450 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!uwm.edu!news.moneng.mei.com!hookup!swrinde!cs.utexas.edu!news.cs.utah.edu!news.cc.utah.edu!cs.weber.edu!terry From: terry@cs.weber.edu (Terry Lambert) Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions Subject: Re: chroot() in FreeBSD 1.1.5.1 Date: 15 Nov 1994 02:21:06 GMT Organization: Weber State University, Ogden, UT Lines: 20 Message-ID: <3a95ui$anu@news.cc.utah.edu> References: <39vvl6$90m@clavin.uprc.com> <3a06kq$9bs@dagny.galt.com> <Cz48o2.4KB@twwells.com> NNTP-Posting-Host: cs.weber.edu In article <Cz48o2.4KB@twwells.com> bill@twwells.com (T. William Wells) writes: ] : I'm not sure why its implemented this way. I thought I would find an ] : answer in Leffler, et al, but I just checked and it didn't say. The source ] : code for the system call doesn't say either. ] ] Sigh. What do you think happens when you make a shiny new ] directory hierarchy with an edited copy of /etc/passwd, chroot to ] it, and then run su? Uh... you get to be root, trapped in your own little world and unable to affect other files on the system? Unless you write the raw devices, that is. 8-). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.