Jump to content

Hardware functionality scan

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Fuhghettaboutit (talk | contribs) at 00:36, 22 August 2012 (Fuhghettaboutit moved page Hardware Functionality Scan to Hardware functionality scan: Requested at Wikipedia:Requested moves as uncontroversial (//en.wikipedia.org/w/index.php?title=Wikipedia:Requested_moves&oldid=508538316#movereq-Hardwar...). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

A hardware functionality scan (HFS) is conducted in order to verify that a certain device is really what it claims to be. It's patented by Microsoft.

Some operating systems only send copy protected content, such as movies, to an output device, such as the screen, if that device is able to protect the content from being tapped in an unprotected format. This mechanism can be circumvented by letting fake hardware claiming to be a trusted device. HFS prevents this by letting the device perform certain tasks which are hard to emulate.

Problems

In order to support open-source drivers, a hardware manufacturer has to reveal some details about their product, but HFS requires this information to be kept secret. The problem with generic drivers is that the HFS requires individual drivers for each variant of a product to make them distinguishable, drivers have to account for implementation details instead of using abstract functionality models.

A hardware manufacturer has to have his product's HFS fingerprint listed in the database of trusted hardware in order to make it work under newer Windows operating systems. Thus, Microsoft dictates the conditions under which a device is accepted. The manufacturer may be required to implement certain DRM-features, for which he has to pay a royalty to its respective inventor.

Sources