1996-10-11 - Re: Microsoft CAPI

Header Data

From: Mike McNally <m5@tivoli.com>
To: “James A. Donald” <jamesd@echeque.com>
Message Hash: 0e094d80ef306c964e9ec96c803d98ea47cd65bbbee5d740eaff5bb2b1bdaf90
Message ID: <325E4DFD.45A9@tivoli.com>
Reply To: <199610110558.WAA24031@mail1.best.com>
UTC Datetime: 1996-10-11 13:41:36 UTC
Raw Date: Fri, 11 Oct 1996 06:41:36 -0700 (PDT)

Raw message

From: Mike McNally <m5@tivoli.com>
Date: Fri, 11 Oct 1996 06:41:36 -0700 (PDT)
To: "James A. Donald" <jamesd@echeque.com>
Subject: Re: Microsoft CAPI
In-Reply-To: <199610110558.WAA24031@mail1.best.com>
Message-ID: <325E4DFD.45A9@tivoli.com>
MIME-Version: 1.0
Content-Type: text/plain


James A. Donald wrote:
> 
> Mike McNally writes:
> >>  And so what happens when the Microsoft key is compromised?
> 
> At 03:13 PM 10/9/96 -0500, Andrew Loewenstern wrote:
> > I ask:  "Who Cares?" ...

> Better than disabling, would be to give the user the choice ...

Agreed, agreed, but my point was to wonder out loud whether such 
"breakages" of the CAPI safety net that gets it the nod for export
would cause the State/Commerce/Spook department to rescind that
permission.

Maybe since the whole export control thing is just an enormous 
government-inflated cloud of FUD it doesn't really matter.

______c_________________________________________________________________
Mike M Nally * IBM % Tivoli * Austin TX  * How quickly we forget that
mailto:m5@tivoli.com mailto:m101@io.com  * "deer processing" and "data
http://www.io.com/~m101/                 * processing" are different!





Thread