1994-07-27 - RE: New Threat on the Horizon: Software Key Escrow

Header Data

From: wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)
To: cypherpunks@toad.com
Message Hash: 38826e5c43a93834d77458fddd26d3534ceb5aada4aaab8bada5fdac36dcd687
Message ID: <9407270710.AA24548@anchor.ho.att.com>
Reply To: N/A
UTC Datetime: 1994-07-27 07:12:39 UTC
Raw Date: Wed, 27 Jul 94 00:12:39 PDT

Raw message

From: wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)
Date: Wed, 27 Jul 94 00:12:39 PDT
To: cypherpunks@toad.com
Subject: RE: New Threat on the Horizon: Software Key Escrow
Message-ID: <9407270710.AA24548@anchor.ho.att.com>
MIME-Version: 1.0
Content-Type: text/plain


> From: Timothy C. May
> Putting Microsoft's feet to the fire, getting them to commit to *not*
> including any form of software-based key escrow in any future releases
> of Windows (Chicago or Daytona) could be a concrete step in the right
> direction. Ditto for Apple.
> ................................................

Does anybody have any experience doing stockholder resolutions?

Even though they seldom pass, they are one way of pressuring a company
to do things, and if well written can have a big impact (e.g. a
resolution that Microsoft/AT&T/Apple/Network23 "never compromise
the privacy of their customers data by using key escrow" puts management
in a position of either supporting the resolution (yay!) or
saying "no, sometimes we're willing to compromise our customer's privacy",
followed by weasel words about how it's Good For America and therefore
Good For General Motors or whatever.

			Thanks;  Bill
			





Thread