From owner-freebsd-current Wed Nov 29 14:12:14 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA25167 for current-outgoing; Wed, 29 Nov 1995 14:12:14 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA25057 for ; Wed, 29 Nov 1995 14:12:03 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA28759; Wed, 29 Nov 1995 15:07:01 -0700 From: Terry Lambert Message-Id: <199511292207.PAA28759@phaeton.artisoft.com> Subject: Re: schg flag on make world in -CURRENT To: nate@rocky.sri.MT.net (Nate Williams) Date: Wed, 29 Nov 1995 15:07:00 -0700 (MST) Cc: terry@lambert.org, nate@rocky.sri.MT.net, freebsd-current@FreeBSD.org In-Reply-To: <199511290517.WAA19065@rocky.sri.MT.net> from "Nate Williams" at Nov 28, 95 10:17:45 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 748 Sender: owner-current@FreeBSD.org Precedence: bulk > > Only if they need to su to root after they come in. What normal user > > comes in from outside the firewall and su's anyway? > > All of the folks who do root work on freefall, and David's work on > wcarchive. Hopefully, these folks use encrypted telnet/rlogin. > > Setting pty's secure is a silly thing to do in any situation unless, as > > is allowing user's to su from unsecure lines. > > You can 'su' on insecure lines. You can't directly login as root on > insecure lines. Paraphrased: "You can use a root password on insecure lines. You can't directly use a root password on insecure lines." Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.