git-secrets VS dmca

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.

# macOS brew install git-secrets # Linux git clone https://github.com/awslabs/git-secrets.git cd git-secrets make install

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.

git-secrets

Install git-secrets. Go into each of your repos, scan for past mistakes, and add a git-commit hook:

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.

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.

https://github.com/awslabs/git-secrets

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.

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?

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.

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).

DMCA from GitHub: https://github.com/github/dmca/blob/master/2023/10/2023-10-10-mazda.md

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

> 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.

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...