From owner-freebsd-hackers Mon Oct 6 09:07:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA07646 for hackers-outgoing; Mon, 6 Oct 1997 09:07:46 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA07637 for ; Mon, 6 Oct 1997 09:07:38 -0700 (PDT) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org [205.179.79.65] by phoenix.volant.org with smtp (Exim 1.62 #1) id 0xIFh2-0001gd-00; Mon, 6 Oct 1997 09:07:36 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id JAA12730; Mon, 6 Oct 1997 09:07:24 -0700 Date: Mon, 6 Oct 1997 09:07:24 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: Re: Netscape 4.03b8 and Encryption: To: Terry Lambert cc: Bradley Dunn , scrappy@hub.org, hackers@freebsd.org In-Reply-To: <199710052326.QAA23497@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 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