From owner-freebsd-hackers  Mon Oct  6 11:52:53 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA19259
          for hackers-outgoing; Mon, 6 Oct 1997 11:52:53 -0700 (PDT)
          (envelope-from owner-freebsd-hackers)
Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA19248
          for <hackers@FreeBSD.ORG>; Mon, 6 Oct 1997 11:52:50 -0700 (PDT)
          (envelope-from tlambert@usr04.primenet.com)
Received: (from tlambert@localhost)
	by usr04.primenet.com (8.8.5/8.8.5) id LAA15966;
	Mon, 6 Oct 1997 11:52:20 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199710061852.LAA15966@usr04.primenet.com>
Subject: Re: Netscape 4.03b8 and Encryption:
To: patl@phoenix.volant.org
Date: Mon, 6 Oct 1997 18:52:19 +0000 (GMT)
Cc: tlambert@primenet.com, bradley@dunn.org, scrappy@hub.org,
        hackers@FreeBSD.ORG
In-Reply-To: <ML-3.3.876154044.7515.patl@asimov> from "patl@phoenix.volant.org" at Oct 6, 97 09:07:24 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
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.

EBones.

Any pluggable technology can be used to plug cryptography.  Would you
have me believe that pluggable technologies are prohibited?

What about the socket for the DES chip on Sun SPARC Machines?


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.