From owner-freebsd-current Sun Sep 27 14:37:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21586 for freebsd-current-outgoing; Sun, 27 Sep 1998 14:37:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21557 for ; Sun, 27 Sep 1998 14:37:28 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id FAA14538; Mon, 28 Sep 1998 05:35:27 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199809272135.FAA14538@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Enkhyl cc: Sascha Schumann , Edwin Culp , Manfred Antar , Glenn Johnson , current@FreeBSD.ORG Subject: Re: Netscape no longer works with ELF system In-reply-to: Your message of "Sun, 27 Sep 1998 12:04:49 MST." Date: Mon, 28 Sep 1998 05:35:26 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Enkhyl wrote: > On Sun, 27 Sep 1998, Sascha Schumann wrote: > > > On Fri, 25 Sep 1998, Enkhyl wrote: > > > > > On Fri, 25 Sep 1998, Edwin Culp wrote: > > > > > > > What's wrong with communicator-v45b2-export.x86-unknown-freebsd.tar.gz? I > > > > begining to almost like it:-) > > > > I haven't had any problems with my elf current. > > > > > > For the truly paranoid (like me), the problem is that it only has > > > export-grade crypto. > > > > You didn't miss Fortify, did you. It adds real crypto support to export > > restricted Navigator versions, and it's still legal. Homepage is > > http://www.fortify.net - for a list of supported platforms see > > http://www.fortify.net/README.html#versions > > netscape 4.5b2 isn't supported. Because 4.5b2 doesn't have the 128 bit code at all. Background.. The export versions of netscape have both 40 and 128 bit encryption. The 40 bit code is default, but if the server has a special key signed by the right people it means that the key is for a financial institution etc which were "approved" for export use of stronger crypto. So, when netscape sees one of these servers with the right keys, it turns on full 128 bit mode, even on export browsers. The fortify patches tweak this so that it will always try and use 128-bit crypto regardless of the server key. That's why the patches are so small. Netscape 4.5 betas do not have the 128 bit mode at all yet, so can't be used in 128 bit mode on financial institutions etc. > -- > Christopher Nielsen > Scient: The Art and Science of Electronic Business > cnielsen@scient.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm Netplex Consulting "No coffee, No workee!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message