Hardware functionality scan: Difference between revisions

Content deleted Content added
re-categorisation per speedy CFD, Replaced: Category:Digital Rights Management → Category:Digital rights management using AWB
m Problems: made sentences instead of bullet points
Line 6:
 
==Problems==
*In '''trustedorder 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.
* '''open-source drivers''': In order support open-source drivers, a hardware manufacturer has to reveal some details about their product, but HFS requires these information to be kept secret.
* '''generic drivers''': The HFS requires indiviudal drivers for each variant of a product, to make them distinguishable: drivers have to account for implementation details instead of using abstract functionality models.
* '''trusted hardware''': 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.
 
==External links==