Jump to content

Protected Media Path: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
m Also, whoops
m caps. use acro defd
 
(20 intermediate revisions by 17 users not shown)
Line 1: Line 1:
{{short description|Set of technologies}}
⚫
The '''Protected Media Path''' is a set of technologies creating a "Protected Environment," first included in [[Microsoft]]'s [[Windows Vista]] [[operating system]], that is used to enforce [[digital rights management]] (or DRM) protections on content.

⚫
Its subsets are ''Protected Video Path (PVP)'' and ''Protected User Mode Audio (PUMA)''.
⚫
The '''Protected Media Path''' is a set of technologies creating a "Protected Environment," first included in [[Microsoft]]'s [[Windows Vista]] [[operating system]], that is used to enforce [[digital rights management]] (DRM) protections on content.
⚫
Its subsets are ''Protected Video Path (PVP)'' and ''Protected User Mode Audio (PUMA)''. Any application that uses Protected Media Path in Windows uses [[Media Foundation]].


==Overview==
==Overview==
Line 7: Line 9:
In order to prevent users from copying DRM content, Windows Vista provides process isolation and continually monitors what kernel-mode software is loaded. If an unverified component is detected, then Vista will stop playing DRM content, rather than risk having the content copied. The protected environment is implemented completely in software, so software-based attacks such as patching the Windows kernel are possible.<ref name="DPinPurr">Ionescu, Alex. "[http://www.alex-ionescu.com/?p=35 Introducing D-Pin Purr v1.0 - 32bit Edition]." Retrieved on April 11, 2007.</ref>
In order to prevent users from copying DRM content, Windows Vista provides process isolation and continually monitors what kernel-mode software is loaded. If an unverified component is detected, then Vista will stop playing DRM content, rather than risk having the content copied. The protected environment is implemented completely in software, so software-based attacks such as patching the Windows kernel are possible.<ref name="DPinPurr">Ionescu, Alex. "[http://www.alex-ionescu.com/?p=35 Introducing D-Pin Purr v1.0 - 32bit Edition]." Retrieved on April 11, 2007.</ref>


These restrictions concern the various outputs from the PC. For DRM content, digital outputs such as [[Digital Visual Interface]] (DVI) and High Definition Multimedia Interface ([[HDMI]]) will have [[High-bandwidth Digital Content Protection]] (HDCP) enabled, to prevent someone from recording the digital stream. Even analog TV-style outputs typically require some restrictions, provided by mechanisms such as [[Macrovision]] and [[CGMS-A]]. These restrictions only apply to DRM-restricted content, such as [[HD DVD]] or [[Blu-ray]] that are encrypted with [[Advanced Access Content System|AACS]], and also apply in Windows XP using supported playback applications.<ref>[http://www.cyberlink.com/multi/support/answerbox_productfaq.jsp?FID=2579&nProdId=31 CyberLink Customer Support - FAQ - What operating system should I have installed on my computer when playing Blu-ray Disc or HD DVD titles?<!-- Bot generated title -->]</ref><ref>[http://www.cyberlink.com/multi/support/answerbox_productfaq.jsp?FID=2600&nProdId=31&ProdVerId=175&nCateId=4 CyberLink Customer Support - FAQ - PowerDVD displays an error message "The playback of this content is not allowed with an digital output device. Please use an analog output device."<!-- Bot generated title -->]</ref> Users' standard unprotected content will not have these restrictions. Some output types such as [[S/PDIF]] (Sony/Philips Digital Interchange Format) typically don’t have a suitable DRM scheme available, so these need to be turned off reliably if the content so specifies.
These restrictions concern the various outputs from the PC. For DRM content, digital outputs such as [[Digital Visual Interface]] (DVI) and High Definition Multimedia Interface ([[HDMI]]) will have [[High-bandwidth Digital Content Protection]] (HDCP) enabled, to prevent someone from recording the digital stream. Even analog TV-style outputs typically require some restrictions, provided by mechanisms such as [[Macrovision]] and [[CGMS-A]]. These restrictions only apply to DRM-restricted content, such as [[HD DVD]] or [[Blu-ray]] that are encrypted with [[Advanced Access Content System|AACS]], and also apply in Windows XP using supported playback applications.<ref>[http://www.cyberlink.com/multi/support/answerbox_productfaq.jsp?FID=2579&nProdId=31 CyberLink Customer Support - FAQ - What operating system should I have installed on my computer when playing Blu-ray Disc or HD DVD titles?<!-- Bot generated title -->]</ref><ref>[http://www.cyberlink.com/multi/support/answerbox_productfaq.jsp?FID=2600&nProdId=31&ProdVerId=175&nCateId=4 CyberLink Customer Support - FAQ - PowerDVD displays an error message "The playback of this content is not allowed with a digital output device. Please use an analog output device."<!-- Bot generated title -->]</ref> Users' standard unprotected content will not have these restrictions. Some output types such as [[S/PDIF]] (Sony/Philips Digital Interchange Format) typically don't have a suitable DRM scheme available, so these need to be turned off reliably if the content so specifies.


In Vista, the control of PC video outputs is provided by PVP-OPM, which is essentially the next generation of [[Certified Output Protection Protocol]] (COPP) introduced in [[Windows XP]]. However, rather than being a software [[application programming interface]], PVP-OPM operates with the Windows media components in the protected environment.
In Vista, the control of PC video outputs is provided by PVP-OPM, which is essentially the next generation of [[Certified Output Protection Protocol]] (COPP) introduced in [[Windows XP]]. However, rather than being a software [[application programming interface]], PVP-OPM operates with the Windows media components in the protected environment.
Line 16: Line 18:
In January 2007 the developer [[Alex Ionescu]] announced that he had found a method that allows end users to bypass Vista's Protected Media Path.
In January 2007 the developer [[Alex Ionescu]] announced that he had found a method that allows end users to bypass Vista's Protected Media Path.
This would allow digital content to be played on equipment that does not implement DRM restriction measures (like rescaling of video resolutions and disabling analog audio outputs).
This would allow digital content to be played on equipment that does not implement DRM restriction measures (like rescaling of video resolutions and disabling analog audio outputs).
However, he did not release any source code in fear of a Microsoft lawsuit regarding possible violation of the [[DMCA]].<ref>[http://www.alex-ionescu.com/?p=24 Alex Ionescu’s Blog » Update on Driver Signing Bypass<!-- Bot generated title -->]</ref> On 6 March 2007, Microsoft responded after internal testing, that the described method would not work.<ref>[http://www.alex-ionescu.com/?p=31 Alex Ionescu’s Blog » Vista DRM Issue Aftermath<!-- Bot generated title -->]</ref>
However, he did not release any source code in fear of a Microsoft lawsuit regarding possible violation of the [[Digital Millennium Copyright Act|DMCA]].<ref>{{Cite web |url=http://www.alex-ionescu.com/?p=24 |title=Alex Ionescu’s Blog » Update on Driver Signing Bypass<!-- Bot generated title --> |access-date=2007-10-28 |archive-url=https://web.archive.org/web/20070928022036/http://www.alex-ionescu.com/?p=24 |archive-date=2007-09-28 |url-status=dead }}</ref> On 6 March 2007, Microsoft responded after internal testing that the described method would not work.<ref>{{Cite web |url=http://www.alex-ionescu.com/?p=31 |title=Alex Ionescu’s Blog » Vista DRM Issue Aftermath<!-- Bot generated title --> |access-date=2007-10-28 |archive-url=https://web.archive.org/web/20070928022021/http://www.alex-ionescu.com/?p=31 |archive-date=2007-09-28 |url-status=dead }}</ref>


==Criticism==
==Criticism==
In addition to common criticisms against [[Digital Rights Management]] schemes, there has been speculation that this scheme has been motivated by the fact that it would affect official [[graphics hardware and FOSS|free/open source graphics driver]] support by manufacturers. The scheme relies on the internals of [[graphics card]]s to tell whether the hardware is trustworthy (permitted to play copy-protected content). This could be subverted if an attacker knows certain details about the hardware's operation, which could be disclosed by hardware [[documentation]] or open source [[device driver]]s.<!-- section "Elimination of Open-source Hardware Support" --><ref name=vista-cost>{{cite journal |author=[[Peter Gutmann (computer scientist)|Peter Gutmann]] |date=2006-12-26 |title=A Cost Analysis of Windows Vista Content Protection |url=http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.html |accessdate=2007-01-28 }}</ref> However, this will not affect platform independency, as the scheme is provided with no charge.<ref>[http://msdn.microsoft.com/en-us/library/ms700168(VS.85).aspx How to Play Protected Media Files (Windows)]</ref>
In addition to common criticisms against DRM schemes, there has been speculation that this scheme has been motivated by the fact that it would affect official [[graphics hardware and FOSS|free/open source graphics driver]] support by manufacturers. The scheme relies on the internals of [[graphics card]]s to tell whether the hardware is trustworthy (permitted to play copy-protected content). This could be subverted if an attacker knows certain details about the hardware's operation, which could be disclosed by hardware [[documentation]] or open source [[device driver]]s.<!-- section "Elimination of Open-source Hardware Support" --><ref name=vista-cost>{{cite journal |author=Peter Gutmann |author-link=Peter Gutmann (computer scientist) |date=2006-12-26 |title=A Cost Analysis of Windows Vista Content Protection |url=http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.html |access-date=2007-01-28 }}</ref> However, this will not affect platform independency, as the scheme is provided with no charge.<ref>[http://msdn.microsoft.com/en-us/library/ms700168(VS.85).aspx How to Play Protected Media Files (Windows)]</ref>
Microsoft has frequently been accused of adding the Protected Media Path feature to Vista to block customers from copying rightfully owned media content<ref>[http://blogs.cnet.com/8301-13506_1-9785337-17.html?tag=blg.orig Why Microsoft must abandon Vista to save itself | The Digital Home - Don Reisinger's take on the tech closest to home - CNET Blogs<!-- Bot generated title -->]</ref> (a practice believed to be protected by Fair Use provisions of the Copyright Act), and the feature is widely quoted as an example of Microsoft's uncompromising adherence to DRM.
Microsoft has frequently been accused of adding the Protected Media Path feature to Vista to block customers from copying rightfully owned media content<ref>[http://blogs.cnet.com/8301-13506_1-9785337-17.html?tag=blg.orig Why Microsoft must abandon Vista to save itself | The Digital Home – Don Reisinger's take on the tech closest to home – CNET Blogs<!-- Bot generated title -->]{{Dead link|date=May 2020 |bot=InternetArchiveBot |fix-attempted=yes }}</ref> (a practice believed to be protected by Fair Use provisions of the Copyright Act), and the feature is widely quoted as an example of Microsoft's uncompromising adherence to DRM.


These accusations have never gained much traction{{cn}} largely because Vista treats non-DRM media exactly the same as previous versions of Windows, and that following Vista's release there has been no change in the availability of free/open source drivers from graphics hardware manufacturers.{{cn}}
These accusations have never gained much traction{{citation needed|date=May 2013}} largely because Vista treats non-DRM media exactly the same as previous versions of Windows, and that following Vista's release there has been no change in the availability of free/open source drivers from graphics hardware manufacturers.{{citation needed|date=May 2013}}


==See also==
==See also==
* [[Bus encryption]]
* [[Features new to Windows Vista]]
* [[Features new to Windows Vista]]
* [[Windows Vista I/O technologies]]
* [[Windows Vista I/O technologies]]
* [[Trusted Computing]]
* [[Trusted Computing]]
* [[Image Constraint Token]]


==References==
==References==
{{Reflist}}
{{Reflist}}

* http://www.microsoft.com/whdc/device/stream/output_protect.mspx
==External links==
* http://msdn2.microsoft.com/en-gb/library/aa376846.aspx
* http://www.microsoft.com/whdc/system/vista/process_Vista.mspx
* [http://msdn2.microsoft.com/en-gb/library/aa376846.aspx Protected Media Path]
* http://windows7sins.org
* [http://windows7sins.org windows7sins.org]


{{Windows Components}}
{{Windows Components}}

Latest revision as of 02:33, 18 August 2024

The Protected Media Path is a set of technologies creating a "Protected Environment," first included in Microsoft's Windows Vista operating system, that is used to enforce digital rights management (DRM) protections on content. Its subsets are Protected Video Path (PVP) and Protected User Mode Audio (PUMA). Any application that uses Protected Media Path in Windows uses Media Foundation.

Overview

[edit]

The protected environment in which DRM content is played contains the media components that play DRM content, so the application only needs to provide remote control (play, rewind, pause, and so on), rather than having to handle unprotected content data. The protected environment also provides all the necessary support for Microsoft-approved (signed) third-party software modules to be added. It provides a "wall" against outside copying, where within the walls, content can be processed without making the content available to unapproved software.

In order to prevent users from copying DRM content, Windows Vista provides process isolation and continually monitors what kernel-mode software is loaded. If an unverified component is detected, then Vista will stop playing DRM content, rather than risk having the content copied. The protected environment is implemented completely in software, so software-based attacks such as patching the Windows kernel are possible.[1]

These restrictions concern the various outputs from the PC. For DRM content, digital outputs such as Digital Visual Interface (DVI) and High Definition Multimedia Interface (HDMI) will have High-bandwidth Digital Content Protection (HDCP) enabled, to prevent someone from recording the digital stream. Even analog TV-style outputs typically require some restrictions, provided by mechanisms such as Macrovision and CGMS-A. These restrictions only apply to DRM-restricted content, such as HD DVD or Blu-ray that are encrypted with AACS, and also apply in Windows XP using supported playback applications.[2][3] Users' standard unprotected content will not have these restrictions. Some output types such as S/PDIF (Sony/Philips Digital Interchange Format) typically don't have a suitable DRM scheme available, so these need to be turned off reliably if the content so specifies.

In Vista, the control of PC video outputs is provided by PVP-OPM, which is essentially the next generation of Certified Output Protection Protocol (COPP) introduced in Windows XP. However, rather than being a software application programming interface, PVP-OPM operates with the Windows media components in the protected environment.

Additionally, PVP-UAB (Protected Video Path - User-Accessible Bus) is used to encrypt video and audio data as it passes over the PCI-Express bus, to prevent it from being intercepted and copied on the way to the graphics card. It is complementary to PVP Output Protection Management.

Possible bypass

[edit]

In January 2007 the developer Alex Ionescu announced that he had found a method that allows end users to bypass Vista's Protected Media Path. This would allow digital content to be played on equipment that does not implement DRM restriction measures (like rescaling of video resolutions and disabling analog audio outputs). However, he did not release any source code in fear of a Microsoft lawsuit regarding possible violation of the DMCA.[4] On 6 March 2007, Microsoft responded after internal testing that the described method would not work.[5]

Criticism

[edit]

In addition to common criticisms against DRM schemes, there has been speculation that this scheme has been motivated by the fact that it would affect official free/open source graphics driver support by manufacturers. The scheme relies on the internals of graphics cards to tell whether the hardware is trustworthy (permitted to play copy-protected content). This could be subverted if an attacker knows certain details about the hardware's operation, which could be disclosed by hardware documentation or open source device drivers.[6] However, this will not affect platform independency, as the scheme is provided with no charge.[7]

Microsoft has frequently been accused of adding the Protected Media Path feature to Vista to block customers from copying rightfully owned media content[8] (a practice believed to be protected by Fair Use provisions of the Copyright Act), and the feature is widely quoted as an example of Microsoft's uncompromising adherence to DRM.

These accusations have never gained much traction[citation needed] largely because Vista treats non-DRM media exactly the same as previous versions of Windows, and that following Vista's release there has been no change in the availability of free/open source drivers from graphics hardware manufacturers.[citation needed]

See also

[edit]

References

[edit]
  1. ^ Ionescu, Alex. "Introducing D-Pin Purr v1.0 - 32bit Edition." Retrieved on April 11, 2007.
  2. ^ CyberLink Customer Support - FAQ - What operating system should I have installed on my computer when playing Blu-ray Disc or HD DVD titles?
  3. ^ CyberLink Customer Support - FAQ - PowerDVD displays an error message "The playback of this content is not allowed with a digital output device. Please use an analog output device."
  4. ^ "Alex Ionescu's Blog » Update on Driver Signing Bypass". Archived from the original on 2007-09-28. Retrieved 2007-10-28.
  5. ^ "Alex Ionescu's Blog » Vista DRM Issue Aftermath". Archived from the original on 2007-09-28. Retrieved 2007-10-28.
  6. ^ Peter Gutmann (2006-12-26). "A Cost Analysis of Windows Vista Content Protection". Retrieved 2007-01-28. {{cite journal}}: Cite journal requires |journal= (help)
  7. ^ How to Play Protected Media Files (Windows)
  8. ^ Why Microsoft must abandon Vista to save itself | The Digital Home – Don Reisinger's take on the tech closest to home – CNET Blogs[permanent dead link‍]
[edit]
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Protected_Media_Path&oldid=1240894619"