WineHQ Bugzilla – Bug 31881 – Silverlight 5.x can't individualize on some websites (needs Certified Output Protection Protocol interface)

Bugzilla

Last modified: 2016-12-09 11:10:04 CST

Silverlight 5.x can't individualize on some websites (needs Certified Output Protection Protocol interface)

Bug 31881 - Silverlight 5.x can't individualize on some websites (needs Certified Output Protection Protocol interface)


Summary:	Silverlight 5.x can't individualize on some websites (needs Certified Output ...

Status:	NEW

AppDB:	Show Apps affected by this bug
Product:	Wine
Classification:	Unclassified
Component:	-unknown
Version:	1.5.14
Hardware:	x86 Linux

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Mr. Bugs

URL:
Keywords:

Depends on:	31589
Blocks:
	Show dependency tree

Reported:	2012-10-03 20:52 CDT by Erich E. Hoover
Modified:	2016-12-09 11:10 CST (History)
CC List:	6 users (show)

See Also:	https://launchpad.net/bugs/1235918
Regression SHA1:
Fixed by SHA1:
Distribution:	---
Staged patchset:

Attachments
Add an attachment (back traces, logs, proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Erich E. Hoover 2012-10-03 20:52:45 CDT

After working around Bug #31589 (attachment 41923 [details]) Silverlight 4.x is able to individualize; however, Silverlight 5.x still has problems.  It appears to create the individualization files and then delete them after it fails to connect to a named pipe:
0059:KERNEL32.CreateFileA(020ab990 "\\\\.\\pipe\\lrpc\\keysvc",c0000000,00000000,00000000,00000003,00000000,00000000) ret=7e87340e
0059:Ret  KERNEL32.CreateFileA() retval=ffffffff ret=7e87340e

This named pipe business is not attempted with Silverlight 4.x, so creating this pipe would probably do the trick.  A little googling finds this documentation:
http://www.hsc.fr/ressources/articles/win_net_srv/msrpc_cryptsvc.html

Comment 1 Erich E. Hoover 2013-08-11 12:35:18 CDT

This issue appears to only occur with one of the PlayReady test sites:
http://web.sldrm.video.msn.com/d1/sldrm.html

Other sites can successfully work if GPU acceleration is disabled (Bug #34252).

Comment 2 Erich E. Hoover 2014-02-27 11:33:51 CST

It's been a while since I've done an update to this, and it's worth noting that we found out the real source of the problem.  The actual issue here is that the COPP interface is not implemented and some websites require this interface even if they don't require HDCP.  We've collected a lot more information about this issue at https://bugs.launchpad.net/pipelight/+bug/1235918 .

Comment 3 joaopa 2015-01-28 23:55:22 CST

Still a bug in current wine?

Comment 4 Sebastian Lackner 2015-01-29 00:40:03 CST

Yes, the issue is still present in Wine 1.7.35. It is worth noting that not all websites are affected. See the bug report https://bugs.launchpad.net/pipelight/+bug/1235918 for more information. There are no technical problems to fix this bug, but it is a legal problem.

The Software Freedom Conservancy initially planned to take a look, but then after half a year changed their mind because this is a Pipelight issue, and "Pipelight is not a conservancy member". They can't help us with this "Pipelight-specific code" we're proposing to research and write. (Don't get confused by this answer, it is indeed a Wine bug, to be more precise the missing COPP implementation. No reactions on our attempts to explain the situation.) We contacted other organizations but didn't receive any clear answer so far, so we can't proceed with fixing this issue.
[ see https://bugs.launchpad.net/pipelight/+bug/1235918/comments/26 ]

If someone can help to ensure that the legal situation allows implementing this stuff, then we'll continue working on it. Otherwise (and much more likely) this bug will stay open forever. The bug should probably be renamed to describe the problem a bit better though:

Silverlight 5.x can't individualize on some websites (missing implementation for Certified Output Protection Protocol interface)

Comment 5 Rosanne DiMesio 2015-01-29 09:16:14 CST

Revising summary based on comment 4.

Should this bug also (like the Pipelight bug) be closed as WONTFIX due to the legal issues?

Comment 6 Erich E. Hoover 2015-01-29 13:50:16 CST

(In reply to Rosanne DiMesio from comment #5)
> Revising summary based on comment 4.
> 
> Should this bug also (like the Pipelight bug) be closed as WONTFIX due to
> the legal issues?

I honestly don't know.  I have a fully function patchset for this that I've tested using a key we scrounged off the Internet.  The problem that I have is that I don't know if it's legal for me to post it to wine-patches, even if it doesn't include a key (which is necessary to get it work).  It would be really great if I could get some professional advice on what to do here, but nobody that we've contacted has been willing to give us a recommendation.

Comment 7 Rosanne DiMesio 2015-01-30 08:56:00 CST

The impression I got from Michael's post in the launchpad bug is that you have gotten a clear recommendation:

-------
We spent most of them time talking to organizations like the Free Software Foundation Europe and asked them whether one of these creative ways may not violate any laws. The result is sadly that all these ideas are at least in some gray area and they don't know any similar cases and therefore highly suggest us not to do any of them. 
-------

Comment 8 Alexandre Julliard 2015-02-01 23:25:07 CST

I also discussed this with the SFLC, but we don't see any way that we could support signed drivers. Requiring a Microsoft private key is not an option. If there are other approaches you would like to discuss, feel free to contact me privately.