From owner-freebsd-questions Thu Mar 16 09:23:23 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA13615 for questions-outgoing; Thu, 16 Mar 1995 09:23:23 -0800 Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA13607 for ; Thu, 16 Mar 1995 09:23:11 -0800 Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA17185 for questions@freebsd.org; Thu, 16 Mar 1995 18:19:38 +0100 From: Luigi Rizzo Message-Id: <199503161719.SAA17185@labinfo.iet.unipi.it> Subject: cern_httpd and passwords To: questions@FreeBSD.org Date: Thu, 16 Mar 1995 18:19:38 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1199 Sender: questions-owner@FreeBSD.org Precedence: bulk Hi, we have had a few problems in using the password-related functions of cern-httpd. We have solved the problem by modifying the calls to crypt(), but it is not very clear how it works. We have 950210 snapshot *without* DES (I guess). The problem is, crypt in the snapshot behaves differently from what the manpage says: it always return a string longer than 13 chars, with the format $1$_saltxxx$encryptedchars and this happens even when the original salt is two-chars (as in the old versions of crypt). I remember somebody (Poul ?) discussed the subject when password encription was changed, but this hasn't percolated into the documentation. Are there problems in reverting crypt to behave as usual when a two-char salt is specified *and* no DES is present ? Anyways, could somebody modify the crypt manpage appropriately ? Thanks Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 ====================================================================