From owner-freebsd-stable Wed Nov 22 22:24:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 94D8837B4CF for ; Wed, 22 Nov 2000 22:24:40 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.11.1/8.11.1) with ESMTP id eAN6Mjw13783; Thu, 23 Nov 2000 12:23:02 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 23 Nov 2000 12:22:44 +0600 (NS) From: Max Khon To: Chris Knight Cc: freebsd-stable@FreeBSD.ORG Subject: RE: Hmm..passwords. In-Reply-To: <002f01c054d2$86ec6ac0$020aa8c0@aims.private> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Thu, 23 Nov 2000, Chris Knight wrote: > > NODESCRYPTLINKS was always intended as a temporary workaround. The > > solution is to use passwd_format=des in your default login class. > > > It's a solution for login. It's not a solution for any application that > dynamically links to libcrypt, and then expects the hash algorithm to remain > the same - which is a fair assumption to make. I'm exceptionally happy with > NODESCRYPTLINKS, so my opinion is to leave it alone. from this point of view default format should always be 'des' with passwd_format=md5 in /etc/login.conf (most applications expect crypt to be des-crypt) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message