1996-11-17 - Re: RFC: A UNIX crypt(3) replacement

Header Data

From: stewarts@ix.netcom.com
To: “Joshua E. Hill” <jehill@w6bhz.calpoly.edu>
Message Hash: 41d04c34d240872d50fe2b2687626352c97f0e07be58b9020967776645c7c70c
Message ID: <1.5.4.32.19961117112455.003ac9d4@popd.ix.netcom.com>
Reply To: N/A
UTC Datetime: 1996-11-17 08:25:06 UTC
Raw Date: Sun, 17 Nov 1996 00:25:06 -0800 (PST)

Raw message

From: stewarts@ix.netcom.com
Date: Sun, 17 Nov 1996 00:25:06 -0800 (PST)
To: "Joshua E. Hill" <jehill@w6bhz.calpoly.edu>
Subject: Re: RFC: A UNIX crypt(3) replacement
Message-ID: <1.5.4.32.19961117112455.003ac9d4@popd.ix.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain


At 08:51 PM 11/16/96 -0800, "Joshua E. Hill" <jehill@w6bhz.calpoly.edu> wrote:
>	I'm trying to think of a function to replace UNIX's crypt(3).  
>My design criteria are as follows:
...
>NMAC(k, m) = H(k1, H(k2, m))
....
>Would (n . P . n ) be better?

NMAC is probably a bit stronger, but the real question is why
you want to reinvent crypt(3).  It was fine for logging in from a
hardwired or dialup dumb terminal, but in a network environment you
really need some sort of one-time password system.  S/Key, for instance.

#			Thanks;  Bill
# Bill Stewart, +1-415-442-2215 stewarts@ix.netcom.com
# You can get PGP outside the US at ftp.ox.ac.uk






Thread