From owner-freebsd-stable Tue Feb 20 02:27:47 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA04993 for stable-outgoing; Tue, 20 Feb 1996 02:27:47 -0800 (PST) Received: from pod.spirit.com.au (root@pod.spirit.com.au [203.8.218.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA04973 Tue, 20 Feb 1996 02:27:29 -0800 (PST) Received: from goliath.spirit.net.au by pod.spirit.com.au (8.7.3/1.01SP) id VAA23890; Tue, 20 Feb 1996 21:30:19 +1100 (EST) Received: (from rich@localhost) by goliath.spirit.net.au (8.7.3/8.7.3-SPclient) id VAA01774; Tue, 20 Feb 1996 21:30:59 +1100 (EST) From: Rich Siggs Message-Id: <199602201030.VAA01774@goliath.spirit.net.au> Subject: Re: Q: exportable DES library & "DES How To" for 2.1-STABLE To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 20 Feb 1996 21:30:58 +1100 (EST) Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org In-Reply-To: <23594.824809311@time.cdrom.com> from "Jordan K. Hubbard" at Feb 20, 96 01:41:51 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org Precedence: bulk Hello again Jordan, > > What does 1.1 use then? Would there be _any_ chance of moving a 1.1 passwd > > entry to 2.1, even perhaps pulling in the 1.1 encryption code? > > Sure. Again, if you're talking about a purely DES or MD5 password file > you can migrate now. Since 1.1 didn't use MD5, that's pretty straight- > forward! Indeed - but it was mentioned earlier that 1.1 _didn't_ use DES (that's new on me, as I was assuming 1.1 did use a DES algorithm). In that case, though 1.1 didn't use MD5, but also (supposedly) didn't use DES, then I really am hosed here then. As far as I know, I'm using the default passwd file format/encryption that came with 1.1.5.1-RELEASE & I guess there's little alternative if DES wasn't in use with 1.1 to attempt the port of 1.1's algorithm to my 2.1 Servers (hihohiho - off to hackers I go.. - or do the unfathomable & get my clients to go through the rigors of passwd changes (ohmigod ;) .. or just stay on 1.1. Are there any other alternatives?? Thanks again, Rich.