From owner-freebsd-bugs Thu Apr 18 14:59:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA11866 for bugs-outgoing; Thu, 18 Apr 1996 14:59:04 -0700 (PDT) Received: from idiom.com (idiom.com [140.174.82.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA11830 Thu, 18 Apr 1996 14:58:08 -0700 (PDT) Received: (from muir@localhost) by idiom.com (8.6.12/8.6.12) id OAA20242; Thu, 18 Apr 1996 14:57:44 -0700 Date: Thu, 18 Apr 1996 14:57:44 -0700 From: David Muir Sharnoff Message-Id: <199604182157.OAA20242@idiom.com> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) Cc: joerg_wunsch@uriah.heep.sax.de, scrappy@freefall.freebsd.org, freebsd-bugs@freefall.freebsd.org, core@freebsd.org, muir@idiom.com Subject: Re: Re: bin/1019 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * > dialer?), but the reason that some PPP packages don't understand a * > regular Unix login sequence but wanna use PAP or CHAP instead doesn't * > sound totally unreasonable. At least, everything is hidden inside a * * If you use PAP/CHAP only, don't even start getty over this line, * just start pppd on it directly. That works fine if it is an outgoing line or a dedicated line. There are many PPP packages that are simpler to setup if they do not have to go through a login process. There is one very important PPP package that cannot handle any sort of login process. * Can somebody please review this PR, and send me their opinions. * * I'm not tempted to accept it (we neither try to make getty smart about * detecting SLIP or UUCP sessions, so why should we care about a Netcrap * dialer?), but the reason that some PPP packages don't understand a * regular Unix login sequence but wanna use PAP or CHAP instead doesn't * sound totally unreasonable. At least, everything is hidden inside a * gettytab option, and off by default. I don't think it's practical to try to recognize SLIP sessions because SLIP does not have an authentication protocol layered over it. UUCP can always handle logging in so there is no need for something special. The only other protocol that would be nice to detect is FAX. Detecting fax is hard because the most reliable way to do it is to noice rings and then answer the line by interatively. As an ISP, there is a competative advantage to having a simpler login proceedure. By accepting this patch (and the related pppd patch) you give FreeBSD-based ISPs a technical advantage. I'm going to continue using it no matter what you decide, but it would be nice if it were standard because it's a useful feature that many ISPs could use. -Dave