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:
parent
cd903d75a0
commit
4201059b8c
93
2024/11/2024-11-04-virtualhere.md
Normal file
93
2024/11/2024-11-04-virtualhere.md
Normal file
@ -0,0 +1,93 @@
|
||||
Before disabling any content in relation to this takedown notice, GitHub
|
||||
- contacted the owners of some or all 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).
|
||||
|
||||
---
|
||||
|
||||
While GitHub did not find sufficient information to determine a valid anti-circumvention claim, we determined that this takedown notice contains other valid copyright claim(s).
|
||||
|
||||
---
|
||||
|
||||
One or more repositories in this DMCA takedown notice has been processed in accordance with GitHub's prohibition on sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, and/or software for bypassing checks for product licensing keys.
|
||||
|
||||
You can learn more in [GitHub's Acceptable Use Policies](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies).
|
||||
|
||||
---
|
||||
|
||||
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
|
||||
|
||||
Yes, I am the copyright holder.
|
||||
|
||||
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
|
||||
|
||||
No
|
||||
|
||||
**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.**
|
||||
|
||||
I am the [private] and copyright owner of the VirtualHere software including VirtualHere USB Server
|
||||
|
||||
**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.**
|
||||
|
||||
https://www.virtualhere.com/usb_server_software
|
||||
|
||||
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
|
||||
|
||||
https://github.com/Bebooo43/openwrt-packages-1-new/tree/master/luci-app-virtualhere
|
||||
https://github.com/zhangziran/openwrt-packages1/tree/master/luci-app-virtualhere
|
||||
|
||||
**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?**
|
||||
|
||||
When the customer purchases virtualhere server software they will receive a license key to unlock all features of the software.
|
||||
|
||||
**How is the accused project designed to circumvent your technological protection measures?**
|
||||
|
||||
They basically have changed the binary files so that the license key is circumvented and they checked-in the hacked binaries so that it will accept the default dummy license key they posted on that archive in the README file. This license key allows the user to use all the features of the software without paying.
|
||||
|
||||
Have you searched for any forks
|
||||
|
||||
**<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.**
|
||||
|
||||
https://github.com/Bebooo43/openwrt-packages-1-new/tree/master/luci-app-virtualhere
|
||||
https://github.com/zhangziran/openwrt-packages1/tree/master/luci-app-virtualhere
|
||||
|
||||
**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.**
|
||||
|
||||
No i assume they are in [private] because the README is in [private]
|
||||
|
||||
**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]
|
||||
[private]
|
||||
[private]
|
||||
[private]
|
||||
[private]
|
||||
|
||||
**Please type your full legal name below to sign this request.**
|
||||
|
||||
[private]
|
Loading…
Reference in New Issue
Block a user