[huskerlug] A Cost Analysis of Windows Vista Content Protection
- From: GreyGeek <jkreps@xxxxxxxxxx>
- To: HuskerLug <huskerlug@xxxxxxxxxxxxx>
- Date: Sat, 27 Jan 2007 18:15:55 -0600
http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.html#oss
Elimination of Open-source Hardware Support
In order to prevent the creation of hardware emulators of protected output=
=20
devices, Vista requires a Hardware Functionality Scan (HFS) that can be use=
d=20
to uniquely fingerprint a hardware device to ensure that it's (probably)=20
genuine. In order to do this, the driver on the host PC performs an operati=
on=20
in the hardware (for example rendering 3D content in a graphics card) that=
=20
produces a result that's unique to that device type.
In order for this to work, the spec requires that the operational details o=
f=20
the device be kept confidential. Obviously anyone who knows enough about th=
e=20
workings of a device to operate it and to write a third-party driver for it=
=20
(for example one for an open-source OS, or in general just any non-Windows=
=20
OS) will also know enough to fake the HFS process. The only way to protect=
=20
the HFS process therefore is to not release any technical details on the=20
device beyond a minimum required for web site reviews and comparison with=20
other products.
This potential =E2=80=9Cclosing=E2=80=9D of the PC's historically open plat=
form is an=20
extremely worrying trend. A quarter of a century ago, IBM made the momentou=
s=20
decision to make their PC an open platform by publishing complete hardware=
=20
details and allowing anyone to compete on the open market. Many small=20
companies, the traditional garage startup, got their start through this. Th=
is=20
openness is what created the PC industry, and the reason why most homes=20
(rather than just a few offices, as had been the case until then) have one =
or=20
more PCs sitting in a corner somewhere. This seems to be a return to the ba=
d=20
old days of 25 years ago when only privileged insiders were able to=20
participate.
----
Husker Linux Users Group mailing list
To unsubscribe, send a message to huskerlug-request@xxxxxxxxxxxxx
with a subject of UNSUBSCRIBE
Other related posts:
