Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!ima!haddock!wolfgang
From: wolfgang@haddock.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: 4.3BSD login - logging in as root
Message-ID: <434@haddock.UUCP>
Date: Sat, 11-Apr-87 22:26:45 EST
Article-I.D.: haddock.434
Posted: Sat Apr 11 22:26:45 1987
Date-Received: Sun, 12-Apr-87 19:46:41 EST
References: <274@quacky.mips.UUCP>
Reply-To: wolfgang@haddock.ISC.COM.UUCP (Wolfgang Rupprecht)
Distribution: world
Organization: Home for Wayward Programmers
Lines: 17

In article <274@quacky.mips.UUCP> dce@quacky.UUCP (David Elliott) writes:
>In 4.3BSD, one can only login as root on a port if the port is marked
>"secure" in /etc/ttys. If you try to login as root on a port not marked
>as such, the message "Login incorrect." is printed and you get a new
>login prompt.
>Is there a good reason that login shouldn't go ahead and prompt for a
>password in this case just for the sake of consistency?

Yea, I'll bet that login never gets called. Getty probably reads
/etc/ttys, prompts you with "Login: ", gets your login name, notices
that its root, and *never* calls login. Hence it can't easily fake the
pasword prompt and encryption delay. Remember, it's only the second
"login: " prompt that comes from login (if you screw up the first
time).
-- 
using a freind's account, please reply to:
Alison Chaiken 			mirror!mit-mgm!alison