1994-07-30 - Re: FW: No SKE in Daytona and other goodies

Header Data

From: Blanc Weber <blancw@microsoft.com>
To: paul@poboy.b17c.ingr.com
Message Hash: 460bb3dd79cd3049d26ca5a80e81273eaac19f42391f340944527cbb12288f9e
Message ID: <9407300059.AA08692@netmail2.microsoft.com>
Reply To: N/A
UTC Datetime: 1994-07-30 00:59:15 UTC
Raw Date: Fri, 29 Jul 94 17:59:15 PDT

Raw message

From: Blanc Weber <blancw@microsoft.com>
Date: Fri, 29 Jul 94 17:59:15 PDT
To: paul@poboy.b17c.ingr.com
Subject: Re: FW: No SKE in Daytona and other goodies
Message-ID: <9407300059.AA08692@netmail2.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain


From: Paul Robichaux

...... the road to key escrow is paved with good intentions.
IMHO the developers who might actually be working on
implementations of this scheme either
	a) don't know that it _could easily_ "become part of
	   a nationally-mandated open avenue to spying,"
	b) know but don't think such developments are likely, or
	c) know and don't care.

Clearly education is a powerful antidote to cases a) and b)
...................................................................... 
...................................

You're right:
How would you make clear the connection between key escrow (per se), 
the large context of liberty to pursue software strategies to solve 
customer problems, the and the individuals who find themselves in the middle?

What would you say is the critical, key focal point between the 
existence of a system of operation, and the way it is intended to be used?

And how would you get the educational message out to those involved?

Blanc

[Job-related Disclaimer:  Microsoft won't let me make "official" 
statements,  but they will allow for Superior Arguments.]


 





Thread