From owner-freebsd-java Mon Jan 18 11:44:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27286 for freebsd-java-outgoing; Mon, 18 Jan 1999 11:44:45 -0800 (PST) (envelope-from owner-freebsd-java@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA27271 for ; Mon, 18 Jan 1999 11:44:40 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with esmtp (Exim 1.82 #3) id 102JcO-0000al-00; Mon, 18 Jan 1999 10:41:44 -0800 Date: Mon, 18 Jan 1999 10:41:43 -0800 (PST) From: Tom To: Ian Grigg cc: freebsd-java@FreeBSD.ORG Subject: Re: crypt() equiv? In-Reply-To: <199901181149.HAA25357@systemics.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 18 Jan 1999, Ian Grigg wrote: > > Is there a crypt() equiv in the Java class libs? I'm trying to re-code > > a perl adduser script in Java, and I'm hung up on what to do about > > crypt(), and I'd like to avoid re-implementing something. > > Unlikely. Java doesn't know about Unix systems stuff, and > crypto stuff is hard to export. By default, crypt() on FreeBSD is MD5, and is exportable. I'm more interested in the standard Unix DES crypt() though. The strange thing is that standard DES crypt() is much easier to brute force than MD5 crypt(), but the DES crypt() is export controlled... > In Cryptix 3.0.3 there is a crypt program, which implements > the DES variant (from memory). It doesn't do the hash > variant of crypt, but that is probably implemented with > MD5 and that is also included if you fancy hacking around. Ugh... rewriting crypt() from scratch seems faster... > iang > > PS: http://www.cryptix.org/ Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message