From owner-freebsd-stable Thu Dec 7 3:18:12 2000 From owner-freebsd-stable@FreeBSD.ORG Thu Dec 7 03:18:10 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 7CC6C37B400 for ; Thu, 7 Dec 2000 03:18:09 -0800 (PST) Received: (from root@localhost) by plab.ku.dk (8.11.0/8.9.3) id eB7BI8407646 for freebsd-stable@freebsd.org.AVP; Thu, 7 Dec 2000 12:18:08 +0100 (CET) (envelope-from postmaster@plab.ku.dk) Received: from raven.plab.ku.dk (raven.plab.ku.dk [130.225.105.67]) by plab.ku.dk (8.11.0/8.9.3) with ESMTP id eB7BI8607638 for ; Thu, 7 Dec 2000 12:18:08 +0100 (CET) (envelope-from postmaster@plab.ku.dk) Subject: crypt() default behavior Content-Transfer-Encoding: 8bit To: freebsd-stable@freebsd.org From: Dmitry Karasik Content-Type: text/plain; charset="koi8-r" Lines: 19 Mime-Version: 1.0 Date: 07 Dec 2000 12:18:42 +0100 X-Mailer: Mail::Mailer[v1.18] Net::SMTP[v2.13] Message-Id: Sender: postmaster@plab.ku.dk Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I just bumped into problem that passwords encoded on 4.2-stable do not work on 3.2-stable. AFAIU, the problem is that crypt() default behaviour is not to use MD5 anymore, and passwords that are created though adduser are not recognized on older versions. I didn't follow changes into source tree, so I don't know what reasons were to change crypt(). From another hand, it's a hack to patch adduser in a way it calls crypt with MD5 salt, but maybe you have different opinion? What ( if it ever exists) should be most elegant way to tackle this problem? -- Sincerely, Dmitry --- www.karasik.eu.org --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message