rcm
git-secrets
Our great sponsors
rcm | git-secrets | |
---|---|---|
19 | 32 | |
3,074 | 12,013 | |
0.6% | 1.0% | |
4.4 | 1.0 | |
about 1 month ago | 15 days ago | |
Perl | Shell | |
BSD 3-clause "New" or "Revised" License | 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.
rcm
-
Rotz: Cross platform dotfile manager written in Rust
Are your per-machine branches mostly distinct, or do they share a lot?
I use https://github.com/thoughtbot/rcm and I find my dotfiles share _quite a bit_ in some respects (e.g. neovim config) but are drastically different in others (SSH config as one example) -- keeping things synced _across_ branches sounds very difficult. rcm handles this well, without branches, IMO.
-
Fulfilling a reader's request for my “dot files”
I use https://github.com/thoughtbot/rcm, which works smoothly and includes support for host-specific files
-
Guide me through!
I use thoughtbot/rcm to handle my github dotfiles. Super short version after installing, mkdir ~/.dotfiles Then go through your home directory (ie. ~/ ) and mkrc .bashrc and then do the same for any other files you plan on tweaking or have custom settings for. Most of these with be in ~/.config/ but some will be in ~/ . (ie. mkrc ~/.bashrc for your bash settings and aliases)
-
Don't Let Messy Dotfiles Ruin Your Coding Life! Try dotstow and Simplify Your Workflow Today!
Prior to catching the Nix brainworms and switching to home-manager, I mostly used thoughtbot/rcm.
-
Dotfiles Management
Personally I like (and use) rcm. Everything is still in a git repository, but has more features that work well for sharing across multiple machines.
-
Automatic setup
Check out https://github.com/thoughtbot/rcm
-
Ask HN: What are you using to organize dotfiles / dotconfig files?
I use rcm. It assumes you keep a separate (potentially version-controlled) folder at ~/.dotfiles or similar, and it provides a suite of tools for managing the symlinks.
https://github.com/thoughtbot/rcm
-
Thoughts on chezmoi
currently I am managing my dotfiles with rcm (ran by ansible). This approach served me well over the years but recently I stumpled over chezmoi.
-
Endevour OS with i3
Setup a Github/Gitlab account and find a dotfile manager you like (I'm using RCM - it can do more than I actually use it for).
- is there an ansible like tool in tcl?
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.
https://github.com/awslabs/git-secrets
-
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?
GNU Stow - GNU Stow - mirror of savannah git repository occasionally with more bleeding-edge branches
trufflehog - Find and verify secrets
yadm - Yet Another Dotfiles Manager
gitleaks - Protect and discover secrets using Gitleaks 🔑
chezmoi - Manage your dotfiles across multiple diverse machines, securely.
secretlint - Pluggable linting tool to prevent committing credential.
homesick - Your home directory is your castle. Don't leave your dotfiles behind.
shhgit - Ah shhgit! Find secrets in your code. Secrets detection for your GitHub, GitLab and Bitbucket repositories.
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
aws-vault - A vault for securely storing and accessing AWS credentials in development environments
Chef - Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across any environment, at any scale
SecretFinder - SecretFinder - A python script for find sensitive data (apikeys, accesstoken,jwt,..) and search anything on javascript files