From owner-freebsd-isp Fri Jan 10 01:03:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA01053 for isp-outgoing; Fri, 10 Jan 1997 01:03:39 -0800 (PST) Received: from earth.infinetconsulting.com (earth.infinetconsulting.com [207.23.43.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA01042; Fri, 10 Jan 1997 01:03:33 -0800 (PST) Received: (from lenc@localhost) by earth.infinetconsulting.com (8.6.12/8.6.12) id BAA06406; Fri, 10 Jan 1997 01:16:57 -0800 Date: Fri, 10 Jan 1997 01:16:57 -0800 (PST) From: Leonard Chua To: freebsd-hackares@freebsd.org, freebsd-isp@freebsd.org Subject: pppd and the login option Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. I've been working on setting up a ppp dialup server. I've gotten it to work with PAP via pap-secrets, and I'm now experimenting with it doing PAP authentication through the system password database (by the 'login' option). I've found that pppd keeps dying at login verification. On going through the source code, I've managed to pinpoint the problem to the crypt() call in login(): (file auth.c somewhere about line 500:) epasswd = (char *) crypt(passwd, pw->pw_passwd); if (strcmp(epasswd, pw->pw_passwd)) { syslog(LOG_WARNING,"FAILED crypt validation."); return (UPAP_AUTHNAK); } It core dumps with a segmentation fault at the crypt() call. To make sure that crypt() is not at fault, I made a similar copy of the login function in a separate test file, and it works there. I can put up the test file if anyone likes to take a look. Anyone have any ideas? The mailing lists show quite a few people with problems with the login option. Maybe this is the reason. Thanks. Len. PS> why do I want to use the system database? Simple - I don't like having a unencrypted password file anywhere (even if it's supposedly group and world unreadable).