1995-07-31 - Re: building libraries

Header Data

From: Alex Tang <altitude@CIC.Net>
To: stewarts@ix.netcom.com (Bill Stewart)
Message Hash: 46c2c38e90884f5015f5de4499126a2bd8ef744f7cb18e95c6d4bafbb910e45e
Message ID: <199507311348.JAA04346@petrified.cic.net>
Reply To: <199507310521.WAA08413@ix4.ix.netcom.com>
UTC Datetime: 1995-07-31 13:48:30 UTC
Raw Date: Mon, 31 Jul 95 06:48:30 PDT

Raw message

From: Alex Tang <altitude@CIC.Net>
Date: Mon, 31 Jul 95 06:48:30 PDT
To: stewarts@ix.netcom.com (Bill Stewart)
Subject: Re: building libraries
In-Reply-To: <199507310521.WAA08413@ix4.ix.netcom.com>
Message-ID: <199507311348.JAA04346@petrified.cic.net>
MIME-Version: 1.0
Content-Type: text/plain


On Mon Jul 31 01:25:04 1995: you scribbled...
> 
> At 08:40 PM 7/28/95 -0400, Alex Tang wrote:
> >> The answer is to have some non-USA entity build shareable full fledged 
> >> full powered crypto libraries and provide them for free for the rest of 
> >> the world and for all machines.
> >Wouldn't there still be licensing issues to deal with (in the states at
> >least)??  I'm sure RSA would claim that the package would be in violation
> >of the licensing...
> 
> If you did everything in an RSAREF-compatible manner, that would help;
> I think somebody outside the US has written an RSAREF-clone.
> Some problems include building programs that have generic-callout hooks
> instead of crypto-specific hooks (so that they don't get bitten by ITAR),
> while still maintaining reasonable efficiency and convenience.

Yeah, this would work for everyone except commercial institutions within
the states.  They'd have to get a license agreement for RSA.

...alex...

     Alex Tang  altitude@cic.net   http://petrified.cic.net/~altitude
   CICNet: Unix Support / InfoSystems Services / WebMaster / Programmer
       Viz-It!: Software Developer (Check out http://vizit.cic.net)
  UM-ITD: TaX.500 Developer (Check out http://petrified.cic.net/tax500)
Unofficial SSL/HTTPD FAQ: http://petrified.cic.net/~altitude/ssl/ssl.saga.html




Thread