http://bugs.winehq.org/show_bug.cgi?id=31881
Bug #: 31881 Summary: Silverlight 5.x can't individualize Product: Wine Version: 1.5.14 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: ehoover@mines.edu Depends on: 31589 Classification: Unclassified
After working around Bug #31589 (attachment 41923) 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
http://bugs.winehq.org/show_bug.cgi?id=31881
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=31881
Bug 31881 depends on bug 31589, which changed state.
Bug 31589 Summary: Netflix on Firefox fails with DRM error when loading bar is at 98% http://bugs.winehq.org/show_bug.cgi?id=31589
What |Old Value |New Value ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
http://bugs.winehq.org/show_bug.cgi?id=31881
Andrew Riker andrew.thomas.riker@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew.thomas.riker@gmail.c | |om
http://bugs.winehq.org/show_bug.cgi?id=31881
Mike Ellery mellery@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mellery@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=31881
Gary garysbox@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |garysbox@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=31881
Ben Klopfenstein benklop@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |benklop@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=31881
--- Comment #1 from Erich Hoover erich.e.hoover@gmail.com 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).
http://bugs.winehq.org/show_bug.cgi?id=31881
--- Comment #2 from Erich Hoover erich.e.hoover@gmail.com --- 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 .
https://bugs.winehq.org/show_bug.cgi?id=31881
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #3 from joaopa jeremielapuree@yahoo.fr --- Still a bug in current wine?
https://bugs.winehq.org/show_bug.cgi?id=31881
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
https://bugs.winehq.org/show_bug.cgi?id=31881
--- Comment #4 from Sebastian Lackner sebastian@fds-team.de --- 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)
https://bugs.winehq.org/show_bug.cgi?id=31881
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Silverlight 5.x can't |Silverlight 5.x can't |individualize |individualize on some | |websites (needs Certified | |Output Protection Protocol | |interface)
--- Comment #5 from Rosanne DiMesio dimesio@earthlink.net --- Revising summary based on comment 4.
Should this bug also (like the Pipelight bug) be closed as WONTFIX due to the legal issues?
https://bugs.winehq.org/show_bug.cgi?id=31881
--- Comment #6 from Erich Hoover erich.e.hoover@gmail.com --- (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.
https://bugs.winehq.org/show_bug.cgi?id=31881
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://launchpad.net/bugs/ | |1235918
--- Comment #7 from Rosanne DiMesio dimesio@earthlink.net --- 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. -------
https://bugs.winehq.org/show_bug.cgi?id=31881
--- Comment #8 from Alexandre Julliard julliard@winehq.org --- 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.
https://bugs.winehq.org/show_bug.cgi?id=31881
Mike Ellery mellery@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|mellery@gmail.com |
https://bugs.winehq.org/show_bug.cgi?id=31881
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://web.archive.org/web | |/20140820091154/http://silv | |erlight.dlservice.microsoft | |.com/download/F/8/C/F8C0EAC | |B-92D0-4722-9B18-965DD2A681 | |E9/30514.00/Silverlight.exe Keywords| |download, obfuscation CC| |focht@gmx.net
--- Comment #9 from Anastasius Focht focht@gmx.net --- Hello folks,
five years have passed since the last discussion. If there is no legal way to support this feature in Wine then I guess there is no point to keep this bug report open -> WONTFIX?
Another point to consider: How does Silverlight 5.x integrate with the current incarnation of 'PlayReady' client/server technology?
* https://www.microsoft.com/PlayReady
* https://docs.microsoft.com/en-us/playready/overview/developing-applications
--- quote --- Developing Applications using PlayReady on Windows 7
Some PlayReady Partners provide SDKs to run PlayReady on Windows 7 and Mac OS, based on Electron, Xamarin, or other technologies. You can contact these PlayReady Partners directly for more information.
Silverlight is a deprecated application framework running on Windows 7 and Mac OS that includes a fully functional PlayReady Client. It runs in browsers with limitations, and can also run out of browsers to provide standalone apps on Windows 7 and Mac OS. --- quote ---
Silverlight 5.x is still mentioned but it's more like a dead horse.
$ sha1sum Silverlight.exe 91ca5fcf9fd82f2059401514a2ba66fee471af5f Silverlight.exe
$ du -sh Silverlight.exe 6.7M Silverlight.exe
$ wine --version wine-6.0-202-gc7de9f2daa8
Regards
https://bugs.winehq.org/show_bug.cgi?id=31881
--- Comment #10 from Erich E. Hoover erich.e.hoover@gmail.com --- (In reply to Anastasius Focht from comment #9)
Hello folks,
five years have passed since the last discussion. If there is no legal way to support this feature in Wine then I guess there is no point to keep this bug report open -> WONTFIX?
I'm not sure what we should do here, I have code to implement the COPP interface that I can conceivably submit - but it's useless without a private key that Silverlight/PlayReady accepts. I know that this code works because we found such a key online, back when Google still made it easy to search for such things, and have tested that most PlayReady websites work if you report the monitor as using an unsecured interface (VGA). I would guess that the powers that be would say to declare it WONTFIX, but that makes me sad - so I'm inclined to let someone else make the decision.
Another point to consider: How does Silverlight 5.x integrate with the current incarnation of 'PlayReady' client/server technology? ...
I haven't looked into it, but I would guess that since PlayReady is old that it still uses COPP. It's possible that they've updated to the new interface (OPM), but I really don't know for sure.