From owner-freebsd-questions Fri Apr 17 15:03:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11750 for freebsd-questions-outgoing; Fri, 17 Apr 1998 15:03:14 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11710 for ; Fri, 17 Apr 1998 22:02:54 GMT (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id PAA01741; Fri, 17 Apr 1998 15:02:40 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Fri, 17 Apr 1998 15:02:40 -0700 (PDT) From: Doug White Reply-To: Doug White To: "Ian O'Friel" cc: freebsd-questions@FreeBSD.ORG Subject: Re: Potential Problem.... In-Reply-To: <000101bd6a49$44e5a720$41f14ac2@metallica> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Apr 1998, Ian O'Friel wrote: > I am setting up a system for friends and family to dial-up my PC running > FreeBSD 2.2.5. The machine has Advanced power Management so I edited rc.conf > so that the APM line read "YES" instead of "NO" but I mistakenly pur in "YES > with only one speech mark. I had set my machine up with several groups and > lots of users... but I found that after rebooting this problem caused an > error in the startup procedure and automatically logged in as root. I think > this could be a pontential problem if someone got access to the rc.conf file > diliberately removed a few characters and rebooted the would be logged in as > root which would allow them to create hell...... > > Any comments ? Actually, this is intentional. You were dropped to `single user mode', which activates only the console with root privs so you can fix what's broken. You can access this mode on bootup by typing `-s' at the Boot: prompt or by running `shutdown now'. If you ran the commands: mount -u / mount -a you could then edit rc.conf to fix your blunder, then `exit' the shell to continue booting. If you require security with your system, make sure the system and the console are locked up in a secure place. This way people can't bypass your password mechanisms without breaking into the room. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message