From owner-freebsd-hackers Mon Oct 6 10:52:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14520 for hackers-outgoing; Mon, 6 Oct 1997 10:52:04 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA14497 for ; Mon, 6 Oct 1997 10:52:01 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id KAA14072; Mon, 6 Oct 1997 10:51:42 -0700 (PDT) Message-Id: <199710061751.KAA14072@rah.star-gate.com> To: patl@phoenix.volant.org cc: Terry Lambert , Bradley Dunn , scrappy@hub.org, hackers@FreeBSD.ORG Subject: Re: Netscape 4.03b8 and Encryption: Date: Mon, 06 Oct 1997 10:51:42 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In-reply-to: Your message of "Mon, 06 Oct 1997 09:07:24 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii -------- Nope. Amancio >From The Desk Of patl@phoenix.volant.org : > > Better yet, ask them to make encryption pluggable, and ask them for sample > > code for a 40 bit encryption, and make a 128 bit module for yourself. > > > > If you can get someone in S.A. (or elsewhere) to do it, then NetScape > > can work around the export restrictions (and Microsoft can't). This > > should be very desirable for them, actually. > > Great idea; but I believe that the export restrictions prohibit > pluggable cryptography. > > > > -Pat > >