Date: Mon, 22 Dec 1997 22:21:13 -0800 (PST) From: Javier Henderson <javier@kjsl.com> To: Ben Hockenhull <benh@jpj.net> Cc: Javier Henderson <javier@kjsl.com>, freebsd-questions@freebsd.org Subject: Re: Shooting yourself in the foot Message-ID: <199712230621.WAA01429@kjsl.com> In-Reply-To: <v03102803b0c4f421fbf1@[192.168.10.1]> References: <Pine.BSF.3.96.971222214741.11353C-100000@shell.futuresouth.com> <Pine.SGI.3.96.971222170622.14913A-100000@ocala.cs.miami.edu> <199712230350.TAA00998@kjsl.com> <v03102803b0c4f421fbf1@[192.168.10.1]>
next in thread | previous in thread | raw e-mail | index | archive | help
Ben Hockenhull writes: > >Matthew D. Fuller writes: > > > On Mon, 22 Dec 1997, Joe "Marcus" Clarke wrote: > > > > > > > The way I fixed this when I did something similar was to take the system > > > > down to single user mode, `shutdown now`, then remount / as read/write, > > > > mount -u /, then edit /etc/shells to allow for /bin/false as a valid > > > > shell. Bring the system back up to multi-user and login as a user > > > > allowed to su to root. Then su to root using su -m, you should be able > > > > to issue a chsh root then. If you have no ther users in wheel, then > > > > instaed of editing /etc/shells, use vipw to edit the password file and > > > > change roots shell back to something else. > > > No need to shutdown. > > > Just do a su -m, then use vipw to set root's shell back to sh (or csh if > > > you're REALLY perverse ;). > > > > Well... > > > >bash-2.01$ su -m > >su: kerberos: not in root's ACL. > >Password: > >su: permission denied (shell). > > Well, IIRC, you need to specify the path to a shell with an su -m. > > like so: > > bash-2.01$ su -m /bin/sh Still not quite: bash-2.01$ su -m /bin/sh su: unknown login: /bin/sh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712230621.WAA01429>