dmca
git-secrets
Our great sponsors
dmca | git-secrets | |
---|---|---|
182 | 32 | |
5,370 | 12,001 | |
0.8% | 0.8% | |
9.9 | 1.3 | |
2 days ago | 4 days ago | |
DIGITAL Command Language | Shell | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dmca
-
Why Don't I Like Git More?
Every DMCA takedown notice in https://github.com/github/dmca is a net win for git as a decentralized version control system, especially for repositories that require signed commits. Unfortunately, some people upload only a snapshot of their repository working directory instead of... using git like it is supposed to be used I guess?
-
Plex Asks GitHub to Take Down 'Reshare' Repository over Piracy Fears
I’m with you thus far, but I’m trying to parse the notice to see why GitHub is even complying (see https://github.com/github/dmca/blob/master/2024/03/2024-03-1... ) and I think Torrentfreak got it wrong. I think they’re trying to claim infringement on Plex Server, but the English in the takedown notice is barely legible (and it feels like a mixup between trademarks and copyright), to the point that I find GitHub’s compliance odd.
-
Team Fortress:Source 2 receives DMCA takedown from Valve
Text of tweet thread:
Hello everyone. We have some unfortunate news to share with you.
Today, we received a DMCA takedown from Valve on all our public GitHub repositories and all its forks made by the community.
https://github.com/github/dmca/blob/master/2024/01/2024-01-1...
While we were discussing the project's future internally recently, we already came to the conclusion to stop the development of the project due to the current state of the code being unusable anymore with s&box's recent major engine changes, and that we overall moved on from it.
Sadly, this means this DMCA takedown is the nail in the coffin. We cannot bring it back and we've hit Valve's attention, it seems like they definitely don't want us to use their IP (which is totally fair and legal from them).
-
No attempt at contact, just stabbing the customer in the back
DMCA from GitHub: https://github.com/github/dmca/blob/master/2023/10/2023-10-10-mazda.md
-
Mazda files false DMCA takedown notice to intimidate open source programmer
https://github.com/github/dmca/blob/master/2023/10/2023-10-10-mazda.md
https://www.thedrive.com/news/mazda-slaps-developer-with-cease-and-desist-for-diy-smart-home-integration
https://web.archive.org/web/20231014070536/https://old.reddit.com/r/homeassistant/comments/1771ywu/removal_of_mazda_connected_services_integration/
https://community.home-assistant.io/t/mazda-connected-service/354221
https://community.home-assistant.io/t/removal-of-mazda-connected-services-integration/625885/36
https://www.home-assistant.io/
https://youtu.be/l2qKEkG29gI
https://youtu.be/NfiIXooD77s
https://youtu.be/PrtbYu1OYhY
https://youtu.be/nigJMu0lUbM
https://youtu.be/qLlxOD5IHYc
-
Mazda's DMCA takedown kills a hobbyist's smart car API tool
> Is there anything that average folk can do against these notices when they're sent to companies like GitHub?
They can file a counter-notice, commit to accepting service of process if the other party wants to sue, and wait 10-14 days. There's a guide at https://docs.github.com/en/site-policy/content-removal-polic... and there are plenty of example counter-notices in the https://github.com/github/dmca repo.
-
Removal of Mazda Connected Services Integration
From the posted notice[1], they answered "No" to the question "Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure." Is that the same thing you are referencing?
[1] https://github.com/github/dmca/blob/master/2023/10/2023-10-1...
- DMCA takedown for pymazda and node-mymazda
-
Ask HN: Why did Microsoft, Meta, and PayPal update their ToS today?
I don't know why you're arguing with me when I'm literally giving you sources backing up that what I'm saying is a mere statement of fact: contracts are inherently subject to copyright law like any other text, although the individual violation may be hard to demonstrate and cases difficult to win.
If I understand your example correctly, you would take an existing SaaS's ToS (i.e. copy their copyrighted work), publish it as your own (i.e. lie) and then file a DMCA takedown request (i.e. commit perjury) to force them to remove their ToS? Yes, you could do that. But since you likely can't demonstrate that you're the original copyright holder (e.g. trivially their SaaS pre-dates your service and they probably have internal documents like e-mails surrounding the drafting of the ToS whereas you don't unless you forge those as well) and sending a DMCA takedown request for works you don't actually own is literally a felony crime, I don't think that's a winning strategy.
To be clear: yes, there are laws against abusing DMCA takedown requests, precisely because otherwise anyone could just send them out for fun. Specifically DMCA takedown requests include a statement under penalty of perjury from the copyright holder that they hold the copyright. So this isn't a special DMCA law but just a boring old felony crime involved in fraudulently filing illegitimate legal claims.
If you're wondering why you've never heard of this it's probably because you're thinking of sites like YouTube which don't actually receive DMCA takedown requests normally but instead provide an arbitration system to allow content owners to avoid messy legal back-and-forths over the back of Google and instead be trusted based on who they are (i.e. smaller creators will be stuck in appeals limbo trying to talk to a human whereas large corporations will usually be trusted by default). This does not however apply to e.g. GitHub, which is why there is a public collection of DMCA takedown requests hosted by them: https://github.com/github/dmca
To speed up this conversation: if you can think of another example where your conclusion is "but this is dumb" then it's likely because your example is, not the legal situation you're looking at. Also "but this is dumb" is not a counter-argument to "this is what the law is like". The law does not care if you think it is dumb and saying it is dumb is not a good defense if you end up in court.
-
Internet Archive Targets Book DRM Removal Tool with DMCA Takedown
Takedown notice: https://github.com/github/dmca/blob/master/2023/06/2023-06-2...
The tool is still available on GitLab: https://gitlab.com/bipinkrish/DeGourou
git-secrets
-
Fired for leaked credentials. How do I explain this?
Well, this doesn't really happen at places that don't suck. They had no least privilege access to critical secrets and no processes (like pre-commit hooks using git-secrets) to prevent them being committed.
-
Recovering from Accidentally Pushing Sensitive Information to a Remote Git Repository
# macOS brew install git-secrets # Linux git clone https://github.com/awslabs/git-secrets.git cd git-secrets make install
- Managing secrets like API keys in Python - Why are so many devs still hardcoding secrets?
-
If you pay for an API key depending on the amount of requests, is it safe to push your code to GitHub?
You could use Git hooks to prevent someone from being able to author a commit when you suspect there is a secret being committed. In addition to this, you could also perform this check server-side, in case someone did not run their Git hooks for whatever reason. For example, check out git-secrets.
-
Securing the software supply chain in the cloud
git-secrets
-
How to deal with unintended information leakage when using GitHub as your GIT?
Install git-secrets. Go into each of your repos, scan for past mistakes, and add a git-commit hook:
- GitHub Access Token Exposure
-
Security scanning
I agree that code scanning is really important, the best way to convince others is to identify high-risk threats in source code and present them to the decision-makers. For example, scanning Secrets is great for showing how repositories can be a massive vulnerability and identifying some low-hanging fruit, especially in the git history. Attackers are really after git repository access for this reason and there are plenty of open-source or free tools that you can use to illustrate the problem. Git-Secrets, Truffle Hog. These aren't great for a long-term commercial solution, something like GitGuardian is a better commercial tool but if the goal is just to illustrate the problem then finding some high-value secrets with free tools is a good way to convince the security personnel to invest in some solutions. Then the door is open to having more conversations as you have already proven the risk.
-
Toyota Accidently Exposed a Secret Key Publicly on GitHub for Five Years
I worked for a big startup last year and was on a contract deadline for integrating a vendor framework into a React Native app.
It was taking too long to get a new temp demo license key and GitHub search with clever filters helped me track down a demo key that was recently uploaded to a test repo.
This is also why I use git-secrets in my repos.
-
Marking findings as FPs in recurring scans
Under the covers, it is simply looking up an 'ignore' list stored in YML during each scan. If you are building your own, you might also want to see how AWS Labs is doing it in their solution git secrets.
What are some alternatives?
paimon-moe - Your best Genshin Impact companion! Help you plan what to farm with ascension calculator and database. Also track your progress with todo and wish counter.
trufflehog - Find and verify credentials
cloudstream - Android app for streaming and downloading media.
gitleaks - Protect and discover secrets using Gitleaks 🔑
btcrecover - An open source Bitcoin wallet password and seed recovery tool designed for the case where you already know most of your password/seed, but need assistance in trying different possible combinations.
secretlint - Pluggable linting tool to prevent committing credential.
tetris-os - An operating system, but it only plays Tetris. [UnavailableForLegalReasons - Repository access blocked]
shhgit - Ah shhgit! Find secrets in your code. Secrets detection for your GitHub, GitLab and Bitbucket repositories.
DeDRM_tools - DeDRM tools for ebooks
aws-vault - A vault for securely storing and accessing AWS credentials in development environments
re3 - GTA III, Vice City [UnavailableForLegalReasons - Repository access blocked]
SecretFinder - SecretFinder - A python script for find sensitive data (apikeys, accesstoken,jwt,..) and search anything on javascript files