[50839] in North American Network Operators' Group
Re: Microslosh vision of the future
daemon@ATHENA.MIT.EDU (gg)
Sun Aug 11 19:49:46 2002
From: "gg" <ggregory@affinitas.net>
To: <nanog@nanog.org>, "blitz" <blitz@macronet.net>
Date: Sun, 11 Aug 2002 18:51:53 -0500
Errors-To: owner-nanog-outgoing@merit.edu
This is a multi-part message in MIME format.
------=_NextPart_000_0053_01C24168.28EBA010
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset="iso-8859-1"
Guess my home P.C. will no longer be an intel platform......hello mighty =
SPARC
Gerardo Gregory
----- Original Message -----=20
From: blitz=20
To: nanog@nanog.org=20
Sent: Sunday, August 11, 2002 5:50 PM
Subject: Microslosh vision of the future
So read about Palladianism, and tell me the different between =
Palladium and Server 2000........
=20
Windows Palladium, the end of privacy as we know it.=20
This taken from various sources encluding UHA and deviantart, the =
register and slashdot., Disturbing news..=20
Earlier this week, Microsoft outlined their plans for their next =
generation of operating systems, codenamed Longhorn/Palladium. Among the =
features touted was the "secure networking" functions that OS would =
offer.=20
Firstly:=20
Microsoft plans to implement Palladium DRM (digital rights =
management) in a hardware chip, initially implanted on the mobo, but =
later on embedded in the CPU, and employing hardwired encryption =
throughout. The purpose of this is to flag every file on the computer =
with a digital signature telling a remote server what it is. If it's an =
unauthorized file, the remote server will tell your computer not to let =
you execute it.=20
This is basically an attempt to stop the trading of mp3's and/or =
warez.=20
Secondly:=20
Before an application can run, it too must have a digital =
signature remotely verified by another server. If the program binary =
doesn't match with any of the authenticated binaries, your computer =
won't run it. This, again, is meant to stop your computer running =
"unauthorized" software - which might be warez, or it might just be a =
nifty freeware program that the authors can't afford to have certified. =
Microsoft will be able to control exactly what your computer can and =
can't run.=20
Thirdly:=20
As most of you know, Microsoft employ a strategy of making their =
software deliberately obsolete - they make it forward compatible, but =
not backward compatible. With the laws of the DMCA, it will soon be =
illegal to try to make a software product that is compatible with =
another programs file types (for example, take the many office =
applications there are for Linux which have had some success in =
translating their arcane file formats).=20
This has the effect of killing any competition in the water - =
since you're not allowed to make your new product compatible with any of =
the others, no-one will use it. And eventually people will give up using =
any of the others instead, since no-one else can read their documents. =
So the entire world will be left with one choice only for software - =
Microsoft.=20
Fourthly (I don't know if that's a word, but it should be):=20
Palladium will effectively ban free software, not just free stuff =
for Windows platforms, but free stuff for Linux, Mac, in fact every OS =
that runs on a Palladium enabled motherboard/processor. Why?=20
In order to get the program to run on a palladium platform, you =
will need to pay to have your binary certified as "safe" by Microsoft's =
software authentification branch. And who in their right mind is going =
to pay for a piece of software they spent hours working on? It just =
wouldn't be worth it.=20
It gets worse when it comes to open source projects, such as Linux =
and BSD. Those of you who know about these things will know that open =
source projects are created by freelance coders all over the world who =
create programs in their spare time and then give them to the rest of =
the world for free. Many of them also release the source code for free =
too, so that if you wish you can alter the program (such as to fix bugs, =
add features etc).=20
Now, it would be bad enough if the owner has to pay a =
certification fee. But EVERY CHANGE that is made to the source code will =
require a new, separate certificate to be created. Those of you who use =
Linux will know that so many things get updated so quickly, that this =
just isn't practical, and would cost the open source development people =
millions of dollars. This is money they just don't have, and Microsoft =
knows it.=20
Fifthly:=20
The "secure network". This is the real clincher for Palladium. At =
first, they're going to make it so that it is possible to turn Palladium =
off at the hardware level. But it is created in such a way so that, if =
you try to connect to a Palladium web server, you won't be allowed to. =
Palladium machines will only be able to talk to other Palladium =
machines, and non-Palladium machines won't be able to talk to any =
Palladium machines.=20
Hence, if Palladium reaches critical mass, there will be thousands =
of people the world over who won't be able to access the internet or =
even work on a network with Palladium machines, so by extension they =
will be forced to "upgrade" to Palladium machines.=20
Sixthly:=20
At first I thought: what the hell, this is only going to apply to =
x86 architecture (namely Athlon and Pentium chips, since it's only AMD =
and Intel who are involved at the moment). So, I could try another =
hardware architecture: such as the Mac/PPC, or the Sun Sparc, or an ARM, =
or any other kind of processor.=20
But then I realside that even if I did, I wouldn't be able to =
access the "Palladium network" which could encompass the entire internet =
if this concept goes far enough. So all you Mac users would be =
effectively locked out; you too would have adopt a Palladium machine if =
you wanted your computer to actually do anything.=20
Seventhly:=20
Palladium will enable all your documents to be controlled =
remotely. No, this is not a joke. If Microsoft find you are using an =
outdated version of Office, all they need to do is send a message to =
your computer and it will no longer let you read any of your documents =
that were created with that application.=20
Even more sinister is that if Microsoft take offence at any of the =
documents on your machine (this could be porn, it could be a simple =
document containing DeCSS information or anti-Palladium information) =
then they can delete or alter it not just from your PC but from every =
other Palladium PC on the network.=20
This has a remarkable similarity to the "Ministry of Truth" in =
George Orwell's "1984" where the government continually faked =
information, both new and old, the entire country over to make =
themsleves appear "correct" all the time.=20
If Palladium ever becomes widespread enough, the internet as we =
know it today will be dead. Instead of being controlled by us, it will =
be controlled by Microsoft, and you will have no choice to do exactly =
what they say.=20
Hence why I want to tell as many people about this atrocious idea =
before it become spopular, and M$ administer their miraculous spin to it =
to make it sound like the best thing since sliced bread.=20
Darn, I forgot to post the links explaining about it. I'll also =
put up a few emails from some mailing lists me and my friends are =
members of.=20
Initial outline of Palladium [link]=20
Analysis on how Palladium is solely designed to protect IT =
businesses such as Microsoft [link]=20
The Palladium FAQ [link]=20
How Palladium has the potential to eradicate Linux [link]=20
=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
The following is an excerpt from an email by "Lucky Green" one of =
the worlds most renowned cryptography hackers:=20
[Minor plug: I am scheduled to give a talk on TCPA at this year's =
DEF CON security conference. I promise it will be an interesting talk. =
[link] ]=20
Below are two more additional TCPA plays that I am in a position =
to mention:=20
1) Permanently lock out competitors from your file formats.=20
- From Steven Levy's article:=20
"A more interesting possibility is that Palladium could help =
introduce DRM to business and just plain people. It's a funny thing," =
says Bill Gates. "We came at this thinking about music, but then we =
realized that e-mail and documents were far more interesting domains."=20
Here it is why it is a more interesting possibility to Microsoft =
for Palladium to help introduce DRM to business and "just plain people" =
than to solely utilize DRM to prevent copying of digital entertainment =
content:=20
It is true that Microsoft, Intel, and other key TCPA members =
consider DRM an enabler of the PC as the hub of the future home =
entertainment network. As Ross pointed out, by adding DRM to the =
platform, Microsoft=20
and Intel, are able to grow the market for the platform.=20
However, this alone does little to enhance Microsoft's already =
sizable existing core business. As Bill Gates stated, Microsoft plans to =
wrap their entire set of file formats with DRM. How does this help =
Microsoft's core business? Very simple: enabling DRM for MS Word=20
documents makes it illegal under the DMCA to create competing =
software that can read or otherwise process the application's file =
format without the application vendor's permission.=20
Future maintainers of open source office suites will be faced with =
a very simple choice: don't enable the software to read Microsoft's file =
formats or go to jail. Anyone who doubts that such a thing could happen=20
is encouraged to familiarize themselves with the case of Dmitry =
Skylarov, who was arrested after last year's DEF CON conference for =
creating software that permitted processing of a DRM- wrapped document=20
file format.=20
Permanently locking out competition is a feature that of course =
does not just appeal to Microsoft alone. A great many dominant =
application vendors are looking forward to locking out their =
competition. The beauty of this play is that the application vendors =
themselves never need to make that call to the FBI themselves and incur =
the resultant backlash from the public that Adobe experienced in the =
Skylarov case. The content=20
providers or some of those utilizing the ubiquitously supported =
DRM features will eagerly make that call instead.=20
In one fell swoop, application vendors, such as Microsoft and many =
others, create a situation in which the full force of the U.S. judicial =
system can be brought to bear on anyone attempting to compete with a=20
dominant application vendor. This is one of the several ways in =
which TCPA enables stifling competition.=20
The above is one of the near to medium objectives the TCPA helps =
meet. [The short-term core application objective is of course to ensure =
payment for any and all copies of your application out there]. Below is =
a mid to long term objective:=20
2) Lock documents to application licensing=20
As the Levy article mentions, Palladium will permit the creation =
of documents with a given lifetime. This feature by necessity requires a =
secure clock, not just at the desktop of the creator of the document, =
but also on the desktops of all parties that might in the future read=20
such documents. Since PC's do not ship with secure clocks that the =
owner of the PC is unable to alter and since the TCPA's specs do not =
mandate such an expensive hardware solution, any implementation of =
limited lifetime documents must by necessity obtain the time elsewhere. =
The obvious source for secure time is a TPM authenticated time server =
that distributes the time over the Internet.=20
In other words, Palladium and other TCPA-based applications will =
require at least occasional Internet access to operate. It is during =
such mandatory Internet access that licensing-related information will =
be pushed to the desktop. One such set of information would be =
blacklists of widely-distributed pirated copies of application software =
(you don't need TCPA for this feature if the user downloads and installs =
periodic software updates, but the user may choose to live with=20
application bugs that are fixed in the update rather than see her =
unpaid software disabled).=20
With TCPA and DRM on all documents, the application vendor's =
powers increase vastly: the application vendor can now not just =
invalidate copies of applications for failure to pay ongoing licensing =
fees, but can invalidate all documents that were ever created with the =
help of=20
this application. Regardless how widely the documents may have =
been distributed or on who's computer the documents may reside at =
present.=20
Furthermore, this feature enables world-wide remote invalidation =
of a document file for reasons other than failure to pay ongoing =
licensing fees to the application vendor. To give just one example, =
documents can=20
be remotely invalidated pursuant to a court order, as might be =
given if the author of the document were to distribute DeCSS v3 or =
Scientology scriptures in the future DRM protected format. All that is =
required to=20
perform such an administrative invalidation of a document is =
either a sample copy of the document from which one can obtain its =
globally unique ID, the serial number of the application that created =
the document, or the public key of the person who licensed the =
application. (Other ways to exist but are omitted in the interest of =
brevity).
------=_NextPart_000_0053_01C24168.28EBA010
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Guess my home P.C. will no longer be an =
intel=20
platform......hello mighty SPARC</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Gerardo Gregory</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A href=3D"mailto:blitz@macronet.net" =
title=3Dblitz@macronet.net>blitz</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:nanog@nanog.org"=20
title=3Dnanog@nanog.org>nanog@nanog.org</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Sunday, August 11, 2002 =
5:50=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Microslosh vision of =
the=20
future</DIV>
<DIV><BR></DIV>
<BLOCKQUOTE class=3Dcite cite type=3D"cite"><BR><BR>
<BLOCKQUOTE class=3Dcite cite type=3D"cite"><BR><FONT face=3Darial =
size=3D2>So=20
read about Palladianism, and tell me the different between =
Palladium and=20
Server 2000........</FONT><BR> <BR><FONT face=3Dverdana=20
size=3D1><B>Windows Palladium, the end of privacy as we know=20
it.</B></FONT><FONT face=3D"Times New Roman, Times"> </FONT><FONT =
face=3Darial=20
size=3D2><BR><BR></FONT><FONT face=3Dverdana size=3D2>This taken =
from various=20
sources encluding UHA and deviantart, the register and slashdot.,=20
Disturbing news.. <BR><BR>Earlier this week, Microsoft outlined =
their=20
plans for their next generation of operating systems, codenamed=20
Longhorn/Palladium. Among the features touted was the "secure =
networking"=20
functions that OS would offer. <BR><BR>Firstly: <BR>Microsoft =
plans to=20
implement Palladium DRM (digital rights management) in a hardware =
chip,=20
initially implanted on the mobo, but later on embedded in the CPU, =
and=20
employing hardwired encryption throughout. The purpose of this is =
to flag=20
every file on the computer with a digital signature telling a =
remote=20
server what it is. If it's an unauthorized file, the remote server =
will=20
tell your computer not to let you execute it. <BR><BR>This is =
basically an=20
attempt to stop the trading of mp3's and/or warez. =
<BR><BR>Secondly:=20
<BR>Before an application can run, it too must have a digital =
signature=20
remotely verified by another server. If the program binary doesn't =
match=20
with any of the authenticated binaries, your computer won't run =
it. This,=20
again, is meant to stop your computer running "unauthorized" =
software -=20
which might be warez, or it might just be a nifty freeware program =
that=20
the authors can't afford to have certified. Microsoft will be able =
to=20
control exactly what your computer can and can't run. =
<BR><BR>Thirdly:=20
<BR>As most of you know, Microsoft employ a strategy of making =
their=20
software deliberately obsolete - they make it forward compatible, =
but not=20
backward compatible. With the laws of the DMCA, it will soon be =
illegal to=20
try to make a software product that is compatible with another =
programs=20
file types (for example, take the many office applications there =
are for=20
Linux which have had some success in translating their arcane file =
formats). <BR>This has the effect of killing any competition in =
the water=20
- since you're not allowed to make your new product compatible =
with any of=20
the others, no-one will use it. And eventually people will give up =
using=20
any of the others instead, since no-one else can read their =
documents. So=20
the entire world will be left with one choice only for software -=20
Microsoft. <BR><BR>Fourthly (I don't know if that's a word, but it =
should=20
be): <BR>Palladium will effectively ban free software, not just =
free stuff=20
for Windows platforms, but free stuff for Linux, Mac, in fact =
every OS=20
that runs on a Palladium enabled motherboard/processor. Why? =
<BR>In order=20
to get the program to run on a palladium platform, you will need =
to pay to=20
have your binary certified as "safe" by Microsoft's software=20
authentification branch. And who in their right mind is going to =
pay for a=20
piece of software they spent hours working on? It just wouldn't be =
worth=20
it. <BR><BR>It gets worse when it comes to open source projects, =
such as=20
Linux and BSD. Those of you who know about these things will know =
that=20
open source projects are created by freelance coders all over the =
world=20
who create programs in their spare time and then give them to the =
rest of=20
the world for free. Many of them also release the source code for =
free=20
too, so that if you wish you can alter the program (such as to fix =
bugs,=20
add features etc). <BR>Now, it would be bad enough if the owner =
has to pay=20
a certification fee. But EVERY CHANGE that is made to the source =
code will=20
require a new, separate certificate to be created. Those of you =
who use=20
Linux will know that so many things get updated so quickly, that =
this just=20
isn't practical, and would cost the open source development people =
millions of dollars. This is money they just don't have, and =
Microsoft=20
knows it. <BR><BR>Fifthly: <BR>The "secure network". This is the =
real=20
clincher for Palladium. At first, they're going to make it so that =
it is=20
possible to turn Palladium off at the hardware level. But it is =
created in=20
such a way so that, if you try to connect to a Palladium web =
server, you=20
won't be allowed to. Palladium machines will only be able to talk =
to other=20
Palladium machines, and non-Palladium machines won't be able to =
talk to=20
any Palladium machines. <BR>Hence, if Palladium reaches critical =
mass,=20
there will be thousands of people the world over who won't be able =
to=20
access the internet or even work on a network with Palladium =
machines, so=20
by extension they will be forced to "upgrade" to Palladium =
machines.=20
<BR><BR>Sixthly: <BR>At first I thought: what the hell, this is =
only going=20
to apply to x86 architecture (namely Athlon and Pentium chips, =
since it's=20
only AMD and Intel who are involved at the moment). So, I could =
try=20
another hardware architecture: such as the Mac/PPC, or the Sun =
Sparc, or=20
an ARM, or any other kind of processor. <BR>But then I realside =
that even=20
if I did, I wouldn't be able to access the "Palladium network" =
which could=20
encompass the entire internet if this concept goes far enough. So =
all you=20
Mac users would be effectively locked out; you too would have =
adopt a=20
Palladium machine if you wanted your computer to actually do =
anything.=20
<BR><BR>Seventhly: <BR>Palladium will enable all your documents to =
be=20
controlled remotely. No, this is not a joke. If Microsoft find you =
are=20
using an outdated version of Office, all they need to do is send a =
message=20
to your computer and it will no longer let you read any of your =
documents=20
that were created with that application. <BR>Even more sinister is =
that if=20
Microsoft take offence at any of the documents on your machine =
(this could=20
be porn, it could be a simple document containing DeCSS =
information or=20
anti-Palladium information) then they can delete or alter it not =
just from=20
your PC but from every other Palladium PC on the network. <BR>This =
has a=20
remarkable similarity to the "Ministry of Truth" in George =
Orwell's "1984"=20
where the government continually faked information, both new and =
old, the=20
entire country over to make themsleves appear "correct" all the =
time.=20
<BR><BR><BR>If Palladium ever becomes widespread enough, the =
internet as=20
we know it today will be dead. Instead of being controlled by us, =
it will=20
be controlled by Microsoft, and you will have no choice to do =
exactly what=20
they say. <BR><BR>Hence why I want to tell as many people about =
this=20
atrocious idea before it become spopular, and M$ administer their=20
miraculous spin to it to make it sound like the best thing since =
sliced=20
bread. <BR><BR><BR>Darn, I forgot to post the links explaining =
about it.=20
I'll also put up a few emails from some mailing lists me and my =
friends=20
are members of. <BR><BR>Initial outline of Palladium [link]=20
<BR><BR>Analysis on how Palladium is solely designed to protect IT =
businesses such as Microsoft [link] <BR><BR>The Palladium FAQ =
[link]=20
<BR><BR>How Palladium has the potential to eradicate Linux [link]=20
=
<BR><BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D <BR><BR>The following =
is an=20
excerpt from an email by "Lucky Green" one of the worlds most =
renowned=20
cryptography hackers: <BR><BR>[Minor plug: I am scheduled to give =
a talk=20
on TCPA at this year's DEF CON security conference. I promise it =
will be=20
an interesting talk. [link] ] <BR><BR>Below are two more =
additional TCPA=20
plays that I am in a position to mention: <BR><BR>1) Permanently =
lock out=20
competitors from your file formats. <BR><BR>- From Steven Levy's =
article:=20
<BR>"A more interesting possibility is that Palladium could help =
introduce=20
DRM to business and just plain people. It's a funny thing," says =
Bill=20
Gates. "We came at this thinking about music, but then we realized =
that=20
e-mail and documents were far more interesting domains." =
<BR><BR>Here it=20
is why it is a more interesting possibility to Microsoft for =
Palladium to=20
help introduce DRM to business and "just plain people" than to =
solely=20
utilize DRM to prevent copying of digital entertainment content:=20
<BR><BR>It is true that Microsoft, Intel, and other key TCPA =
members=20
consider DRM an enabler of the PC as the hub of the future home=20
entertainment network. As Ross pointed out, by adding DRM to the =
platform,=20
Microsoft <BR>and Intel, are able to grow the market for the =
platform.=20
<BR><BR>However, this alone does little to enhance Microsoft's =
already=20
sizable existing core business. As Bill Gates stated, Microsoft =
plans to=20
wrap their entire set of file formats with DRM. How does this help =
Microsoft's core business? Very simple: enabling DRM for MS Word=20
<BR>documents makes it illegal under the DMCA to create competing =
software=20
that can read or otherwise process the application's file format =
without=20
the application vendor's permission. <BR><BR>Future maintainers of =
open=20
source office suites will be faced with a very simple choice: =
don't enable=20
the software to read Microsoft's file formats or go to jail. =
Anyone who=20
doubts that such a thing could happen <BR>is encouraged to =
familiarize=20
themselves with the case of Dmitry Skylarov, who was arrested =
after last=20
year's DEF CON conference for creating software that permitted =
processing=20
of a DRM- wrapped document <BR>file format. <BR><BR>Permanently =
locking=20
out competition is a feature that of course does not just appeal =
to=20
Microsoft alone. A great many dominant application vendors are =
looking=20
forward to locking out their competition. The beauty of this play =
is that=20
the application vendors themselves never need to make that call to =
the FBI=20
themselves and incur the resultant backlash from the public that =
Adobe=20
experienced in the Skylarov case. The content <BR>providers or =
some of=20
those utilizing the ubiquitously supported DRM features will =
eagerly make=20
that call instead. <BR><BR>In one fell swoop, application vendors, =
such as=20
Microsoft and many others, create a situation in which the full =
force of=20
the U.S. judicial system can be brought to bear on anyone =
attempting to=20
compete with a <BR>dominant application vendor. This is one of the =
several=20
ways in which TCPA enables stifling competition. <BR><BR>The above =
is one=20
of the near to medium objectives the TCPA helps meet. [The =
short-term core=20
application objective is of course to ensure payment for any and =
all=20
copies of your application out there]. Below is a mid to long term =
objective: <BR><BR>2) Lock documents to application licensing =
<BR><BR>As=20
the Levy article mentions, Palladium will permit the creation of =
documents=20
with a given lifetime. This feature by necessity requires a secure =
clock,=20
not just at the desktop of the creator of the document, but also =
on the=20
desktops of all parties that might in the future read <BR>such =
documents.=20
Since PC's do not ship with secure clocks that the owner of the PC =
is=20
unable to alter and since the TCPA's specs do not mandate such an=20
expensive hardware solution, any implementation of limited =
lifetime=20
documents must by necessity obtain the time elsewhere. The obvious =
source=20
for secure time is a TPM authenticated time server that =
distributes the=20
time over the Internet. <BR><BR>In other words, Palladium and =
other=20
TCPA-based applications will require at least occasional Internet =
access=20
to operate. It is during such mandatory Internet access that=20
licensing-related information will be pushed to the desktop. One =
such set=20
of information would be blacklists of widely-distributed pirated =
copies of=20
application software (you don't need TCPA for this feature if the =
user=20
downloads and installs periodic software updates, but the user may =
choose=20
to live with <BR>application bugs that are fixed in the update =
rather than=20
see her unpaid software disabled). <BR><BR>With TCPA and DRM on =
all=20
documents, the application vendor's powers increase vastly: the=20
application vendor can now not just invalidate copies of =
applications for=20
failure to pay ongoing licensing fees, but can invalidate all =
documents=20
that were ever created with the help of <BR>this application. =
Regardless=20
how widely the documents may have been distributed or on who's =
computer=20
the documents may reside at present. <BR><BR>Furthermore, this =
feature=20
enables world-wide remote invalidation of a document file for =
reasons=20
other than failure to pay ongoing licensing fees to the =
application=20
vendor. To give just one example, documents can <BR>be remotely=20
invalidated pursuant to a court order, as might be given if the =
author of=20
the document were to distribute DeCSS v3 or Scientology scriptures =
in the=20
future DRM protected format. All that is required to <BR>perform =
such an=20
administrative invalidation of a document is either a sample copy =
of the=20
document from which one can obtain its globally unique ID, the =
serial=20
number of the application that created the document, or the public =
key of=20
the person who licensed the application. (Other ways to exist but =
are=20
omitted in the interest of=20
brevity).<BR></FONT></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>=
------=_NextPart_000_0053_01C24168.28EBA010--
