From owner-freebsd-questions Mon Oct 27 22:23:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA00159 for questions-outgoing; Mon, 27 Oct 1997 22:23:10 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from citytel1.citytel.net (root@citytel1.citytel.net [204.244.99.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA00154 for ; Mon, 27 Oct 1997 22:23:08 -0800 (PST) (envelope-from kwoody@citytel.net) Received: from mybsd.net (citytelprct48.citytel.net [204.244.99.124]) by citytel1.citytel.net (8.8.4/8.7.3) with SMTP id WAA28755; Mon, 27 Oct 1997 22:32:00 -0800 (PST) Date: Mon, 27 Oct 1997 21:52:31 -0800 (PST) From: Kwoody X-Sender: kwoody@mybsd.net To: ringlord@bbs.dcoisp.net cc: freebsd-questions@FreeBSD.ORG Subject: Re: login as root remotely not possible? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 Oct 1997 ringlord@bbs.dcoisp.net wrote: > I was able to login as root from main console and my remote terminal on > the serial port, ttyd0 > However, when I try either telnetting into my freebsd box, or rlogging > into my freebsd box from a remote network. The passwd for root doesn't > work. That is to say, when I try to login to my freebsd box either > rlogin or telnet, I am unable to login as root. However, I was able to > create another user account and place that account into the proper > groups to su to root, so all is working well. I was just wondering if > this was a natural thing, not being able to login as root when either > telnetting or rlogging into my machine? If I may take a stab at this...in your /etc/ttys under pseudo terminals add the word secure after network. # Pseudo terminals ttyp0 none network secure ttyp1 none network secure ttyp2 none network ttyp3 none network ttyp4 none network secure ttyp5 none network secure This will allow you to log in as root, but the way you are doing it now is a better way. Login as yourself, but su to root. At least this is how I have used it in the past on my machines so if I'm wrong someone will certainly point you in the right direction. Keith