*BSD News Article 38058


Return to BSD News archive

Xref: sserve comp.os.386bsd.bugs:2623 comp.os.386bsd.questions:14533
Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!ix.netcom.com!netcomsv!calcite!vjs
From: vjs@calcite.rhyolite.com (Vernon Schryver)
Subject: Re: chroot() in FreeBSD 1.1.5.1
Message-ID: <CzHnM3.A38@calcite.rhyolite.com>
Organization: Rhyolite Software
Date: Sat, 19 Nov 1994 00:20:27 GMT
References: <3a06kq$9bs@dagny.galt.com> <Cz48o2.4KB@twwells.com> <3a95ui$anu@news.cc.utah.edu>
Lines: 21

In article <3a95ui$anu@news.cc.utah.edu> terry@cs.weber.edu (Terry Lambert) writes:
>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-).

Make your own /etc/passwd, and then `chown root foo; chmod u+s foo`
and then return to the real world to utilize that handy little foo.
Editors can be handy starting places for foo.


Vernon Schryver    vjs@rhyolite.com