mirror of
https://github.com/github/dmca.git
synced 2025-06-18 17:05:41 -04:00
Process DMCA request
This commit is contained in:
dmca-sync-bot
parent
d8325c0d80
commit
c9ddf97731
167
2025/03/2025-03-31-microsoft.md
Normal file
167
2025/03/2025-03-31-microsoft.md
Normal file
@ -0,0 +1,167 @@
|
||||
Before disabling any content in relation to this takedown notice, GitHub
|
||||
- contacted the owners of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work).
|
||||
- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
|
||||
|
||||
To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice).
|
||||
|
||||
---
|
||||
|
||||
Note: Because the parent repository was actively being forked when this DMCA takedown notice was received, and the submitter had identified all known forks at the time they submitted the takedown notice, GitHub processed the takedown notice against the entire network of 87 repositories, inclusive of the parent repository.
|
||||
|
||||
---
|
||||
|
||||
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
|
||||
|
||||
Yes, I am authorized to act on the copyright owner's behalf.
|
||||
|
||||
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
|
||||
|
||||
Yes
|
||||
|
||||
**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.**
|
||||
|
||||
3199881
|
||||
|
||||
**Does your claim involve content on GitHub or npm.js?**
|
||||
|
||||
GitHub
|
||||
|
||||
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
|
||||
|
||||
Microsoft [private] for the Microsoft PlayReady DRM product.
|
||||
|
||||
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
|
||||
|
||||
The hosted materials are part of our PlayReady product and allow bad actors to pirate PlayReady protected content.
|
||||
|
||||
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
|
||||
|
||||
https://github.com/ready-dl/pyplayready.git
|
||||
https://github.com/smilodon/pyplayready.git
|
||||
https://github.com/lossui011/pyplayready.git
|
||||
https://github.com/Konseru/pyplayready.git
|
||||
https://github.com/hispaniaestable/pyplayready.git
|
||||
https://github.com/LuieJr2024/pyplayready.git
|
||||
https://github.com/openkampus/pyplayready.git
|
||||
https://github.com/chengshi2017/pyplayready.git
|
||||
https://github.com/aryanchaudhary449/pyplayready.git
|
||||
https://github.com/Aryan89909/pyplayready.git
|
||||
https://github.com/Newwayhome/pyplayready.git
|
||||
https://github.com/cash2one/pyplayready.git
|
||||
https://github.com/pigscanflyyy/pyplayready.git
|
||||
https://github.com/fawyrad/pyplayready.git
|
||||
https://github.com/wsy667/pyplayready.git
|
||||
https://github.com/CodeFanaticX/pyplayready.git
|
||||
https://github.com/pardocch/pyplayready.git
|
||||
https://github.com/Dreamer269/pyplayready.git
|
||||
https://github.com/astravaganza/pyplayready.git
|
||||
https://github.com/CriminalMAD/pyplayready.git
|
||||
https://github.com/chu23465/pyplayready.git
|
||||
https://github.com/DRM-Lab/pyplayready.git
|
||||
https://github.com/IzukuDeku01/pyplayready.git
|
||||
https://github.com/baxi10/pyplayready.git
|
||||
https://github.com/n0stal6ic/pyplayready.git
|
||||
https://github.com/austreams/pyplayready.git
|
||||
https://github.com/weixiaowo/pyplayready.git
|
||||
https://github.com/AdiEcho/pyplayready.git
|
||||
https://github.com/fidodone/pyplayready.git
|
||||
https://github.com/nxhda/pyplayready.git
|
||||
https://github.com/TANZ-lab/pyplayready.git
|
||||
https://github.com/limangox/pyplayready.git
|
||||
https://github.com/nilaoda/pyplayready.git
|
||||
https://github.com/mazpaijo/pyplayready.git
|
||||
https://github.com/ninjajiraiyadev/pyplayready.git
|
||||
https://github.com/tonebiclas/pyplayready.git
|
||||
https://github.com/Arsenicss/pyplayready.git
|
||||
https://github.com/kx2000xx/pyplayready.git
|
||||
https://github.com/DecosSoft/pyplayready.git
|
||||
https://github.com/pandamoon21/pyplayready.git
|
||||
https://github.com/kartik1986x/pyplayready-.git
|
||||
https://github.com/imrsaleh/pyplayready.git
|
||||
https://github.com/Theamitkumarsaini/pyplayready.git
|
||||
https://github.com/Mouse753/pyplayready.git
|
||||
https://github.com/afbota/pyplayready.git
|
||||
https://github.com/Erevoc/pyplayready.git
|
||||
https://github.com/65887166/pyplayready.git
|
||||
https://github.com/devine-dl/pyplayready.git
|
||||
https://github.com/Shporterator/pyplayready.git
|
||||
https://github.com/juesus/pyplayready.git
|
||||
https://github.com/monat78/pyplayready.git
|
||||
https://github.com/gounau/pyplayready.git
|
||||
https://github.com/kereminggat/pyplayready.git
|
||||
https://github.com/HeyMaverick/pyplayready.git
|
||||
https://github.com/PlayreadySeller/pyplayready.git
|
||||
https://github.com/fox0618/pyplayready.git
|
||||
https://github.com/Ncw3qvm/pyplayready.git
|
||||
https://github.com/Alexiss02/pyplayready.git
|
||||
https://github.com/nicaicaii/pyplayready.git
|
||||
https://github.com/nmv587/pyplayready.git
|
||||
https://github.com/imorot/pyplayready.git
|
||||
https://github.com/Nosoba/pyplayready.git
|
||||
https://github.com/DevataDev/pyplayready.git
|
||||
https://github.com/son01420309/pyplayready.git
|
||||
https://github.com/mk386/ready-dl_pyplayready.git
|
||||
https://github.com/NitroFuN/pyplayready.git
|
||||
https://github.com/kendywetalk/pyplayready.git
|
||||
https://github.com/alienmaster9/pyplayready.git
|
||||
https://github.com/zhaarey/pyplayready.git
|
||||
https://github.com/vishansh/pyplayready.git
|
||||
https://github.com/albao666/pyplayready.git
|
||||
https://github.com/weapon121/pyplayready.git
|
||||
|
||||
**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**
|
||||
|
||||
Yes
|
||||
|
||||
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
|
||||
|
||||
Microsoft PlayReady is built upon a sophisticated, multi-layered digital rights management framework that employs proprietary cryptographic techniques and controlled distribution channels. Key technical measures include:
|
||||
|
||||
• Secure Key and Certificate Distribution: PlayReady secrets—including Group Keys and device-specific certificates—are generated within and protected by secure hardware and software ecosystems. They are disseminated exclusively to authorized partners through legally binding licensing agreements, ensuring that only entities that have met strict compliance and security standards can access the protected material.
|
||||
|
||||
• Encryption and Authentication: Our DRM framework uses industry-leading encryption protocols and secure authentication mechanisms. This prevents unauthorized entities from reconstructing valid licenses or decrypting protected content. Hardware Security Modules (HSMs) and secure key storage further mitigate risks by safeguarding critical cryptographic ingredients against extraction or tampering.
|
||||
|
||||
• Policy Enforcement and Integrity Checks: PlayReady incorporates runtime integrity verification and secure challenge–response protocols. These measures validate that the operational environment is authentic and has not been compromised or reverse-engineered. Our robust revocation mechanisms ensure that any unauthorized use or distribution of cryptographic material can be curtailed quickly through certificate revocation and system updates.
|
||||
|
||||
Collectively, these measures create a closed ecosystem where access to our proprietary secrets is tightly controlled and monitored, ensuring that only authorized operations under valid licensing agreements are permitted.
|
||||
|
||||
|
||||
**How is the accused project designed to circumvent your technological protection measures?**
|
||||
|
||||
The accused GitHub repositories are engineered in a manner that subverts the core technological protections embedded in PlayReady:
|
||||
|
||||
• Reverse-Engineering of Proprietary Components: The project explicitly builds upon the “mspr_toolkit” – a tool that was originally designed under controlled conditions. By reverse-engineering, manipulating, and repackaging parts of this tool, the project provides users with instructions and code to recreate functionality that replicates sensitive aspects of our DRM ecosystem.
|
||||
|
||||
• Extraction and Reconstruction Methods: The project contains functionality and guidance aimed at extracting and reconstructing keys or certificates from sources that should be controlled. For instance, it describes methods to retrieve cryptographic elements from legacy devices or encrypted firmware binaries—actions that directly circumvent our secure key distribution and licensing processes.
|
||||
|
||||
• Bypassing Secure Licensing Protocols: By distributing code that enables users to generate “PlayReady Device (.prd)” files outside of our authorized system, the project undermines the exclusive process of device provisioning and license issuance. This bypass effectively negates the integrity checks and cryptographic protections that we have employed to enforce usage under a valid licensing regime.
|
||||
|
||||
**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
|
||||
|
||||
Yes
|
||||
|
||||
**Is the work licensed under an open source license?**
|
||||
|
||||
No
|
||||
|
||||
**What would be the best solution for the alleged infringement?**
|
||||
|
||||
Reported content must be removed
|
||||
|
||||
**Do you have the alleged infringer’s contact information? If so, please provide it.**
|
||||
|
||||
**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.**
|
||||
|
||||
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
|
||||
|
||||
**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.**
|
||||
|
||||
**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**
|
||||
|
||||
**So that we can get back to you, please provide either your telephone number or physical address.**
|
||||
|
||||
[private]
|
||||
|
||||
**Please type your full legal name below to sign this request.**
|
||||
|
||||
[private]
|
||||
Loading…
Reference in New Issue
Block a user