cryptoanarchy.wiki

Arise, you have nothing to lose but your barbed wire fences!

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

Header Data

From: The Deviant <deviant@pooh-corner.com>
To: “Joshua E. Hill” <jehill@w6bhz.calpoly.edu>
Message Hash: 0bfeb5099f6a978149e746b526fa9b1fabb9baaed1e9ef038ab7ed8a3b415541
Message ID: <Pine.LNX.3.94.961117141454.2208A-100000@random.sp.org>
Reply To: <199611170451.UAA05059@hyperion.boxes.org>
UTC Datetime: 1996-11-17 14:21:58 UTC
Raw Date: Sun, 17 Nov 1996 06:21:58 -0800 (PST)

Raw message

From: The Deviant <deviant@pooh-corner.com>
Date: Sun, 17 Nov 1996 06:21:58 -0800 (PST)
To: "Joshua E. Hill" <jehill@w6bhz.calpoly.edu>
Subject: Re: RFC: A UNIX crypt(3) replacement
In-Reply-To: <199611170451.UAA05059@hyperion.boxes.org>
Message-ID: <Pine.LNX.3.94.961117141454.2208A-100000@random.sp.org>
MIME-Version: 1.0
Content-Type: text/plain


On Sat, 16 Nov 1996, Joshua E. Hill wrote:

> 
> 	I'm trying to think of a function to replace UNIX's crypt(3).  
> My design criteria are as follows:
> 

Why? UNIX passwords with password shadowing are as secure as any password
system is going to get.  If your security holes are with passwords, its
because your admin is to lazy to install needed security provissions, not
because the system of checking passwords is bad.

If you're worried about network sniffing and the like, get SSH.  Other
than that you're wasting your time.

 --Deviant
Without followers, evil cannot spread.
                -- Spock, "And The Children Shall Lead", stardate 5029.5

Thread