From owner-freebsd-stable  Tue Feb 20 14:39:57 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA11444
          for stable-outgoing; Tue, 20 Feb 1996 14:39:57 -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 OAA11387
          Tue, 20 Feb 1996 14:39:48 -0800 (PST)
Received: from goliath.spirit.net.au by pod.spirit.com.au (8.7.3/1.01SP)
	id JAA01605; Wed, 21 Feb 1996 09:42:50 +1100 (EST)
Received: (from rich@localhost) by goliath.spirit.net.au (8.7.3/8.7.3-SPclient) id JAA04935; Wed, 21 Feb 1996 09:43:30 +1100 (EST)
From: Rich Siggs <rich@goliath.spirit.net.au>
Message-Id: <199602202243.JAA04935@goliath.spirit.net.au>
Subject: Re: Q: exportable DES library ...
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Wed, 21 Feb 1996 09:43:29 +1100 (EST)
Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org
In-Reply-To: <24113.824814381@time.cdrom.com> from "Jordan K. Hubbard" at Feb 20, 96 03:06:21 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

'morning Jordan,
  
>  The default password "encryption" with 1.x
> was a simple scrambler and about as difficult to break as a Captain
> Midnight decoder ring, fresh from a box of cereal.

	Cute - yet more motivation to solve this.. :/
  
> That might actually work to your advantage, however.  Nate - what was
> the algorithm you used?  I don't have any 1.x sources around to check.

	From the 1.1 srcdist I've got, it appears that 1.1 libcrypt sources
call MD5 routines, yet there are references to the need for DES routines in
the libc crypt.. Confusion reigns, could someone help me identify the actual
default/original passwd encryption routines used by 1.1.5.1-RELEASE, with what
src distrib they're in, etc?

> It may well be that you can write a perl script to descramble the
> puppies and then re-DES or MD5 encrypt them.

	Now _that_ would be fantastic! If such a script already exists, then
I'm sure there's more than myself who could use it. But if not, then the info
above will help me track down the actual routines & I'll see what reverse
engineering can be done to unscramble these puppies ;)

Thanks,
Rich.