From owner-freebsd-questions  Wed Jun  4 02:55:21 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA11962
          for questions-outgoing; Wed, 4 Jun 1997 02:55:21 -0700 (PDT)
Received: from main.gbdata.com (USR1-1.detnet.com [207.113.12.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA11953
          for <freebsd-questions@FreeBSD.ORG>; Wed, 4 Jun 1997 02:55:16 -0700 (PDT)
Received: (from gclarkii@localhost)
	by main.gbdata.com (8.8.5/8.8.5) id FAA01369;
	Tue, 3 Jun 1997 05:20:01 -0500 (CDT)
From: Gary Clark II <gclarkii@main.gbdata.com>
Message-Id: <199706031020.FAA01369@main.gbdata.com>
Subject: Re: WTH!? vipw/pwd_mkdb does not encrypt
To: are@communique.no (Are Bryne)
Date: Tue, 3 Jun 1997 05:20:00 -0500 (CDT)
Cc: freebsd-questions@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.96.970530153117.24037H-100000@rune.communique.no> from Are Bryne at "May 30, 97 04:07:37 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Are Bryne wrote:
> Hi,
> 
> Suddenly, I found out that vipw didn't encrypt password entries in new
> additions.
> I tried using pwd_mkdb by hand, which gives no error messages, but still
> does not do the encryption part.
> I tried using the adduser perl script, which does encrypt. But that uses
> the perl crypt() (which is compiled in statically/isn't a system fnct?).
> 
It is using the system crypt.  Works just fine...

> I've checked the /usr/sbin/pwd_mkdb binary and the /usr/lib/libc.so.3.0,
> which both are unchanged (datewise) since the installation.
> /usr/lib/libcrypt* are linked to /usr/lib/libscrypt*, where the libcrypt*
> are from the installation, and the links somewhat newer.
> 
Yes, this normal unless you have des installed, in which case the crypt
has the ablility to do both MD5 and DES crypts.

> The system is a 2.2.1-RELEASE installed (fresh) from ftp. It's been
> working wonderfully since Mar 25. Custom kernel, but no obvious changes
> the last weeks to account for the problem.
> 
> Any brilliant ideas?
enter no password using vipw and then use passwd to enter the new password..:)

> 
> Thank you in advance...
> 
> Are Bryne
Gary

-- 
Gary Clark II   (N5VMF) |    I speak only for myself and "maybe" my company 
gclarkii@GBData.COM     |          Member of the FreeBSD Doc Team 
  Providing Internet and ISP startups - http://WWW.GBData.com for information
       FreeBSD FAQ at ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/FAQ.latin1