git-secrets
YubiKey-Guide
git-secrets | YubiKey-Guide | |
---|---|---|
32 | 112 | |
12,026 | 10,748 | |
0.6% | - | |
1.0 | 8.3 | |
20 days ago | 3 days ago | |
Shell | HTML | |
Apache License 2.0 | MIT License |
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.
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.
YubiKey-Guide
-
Can I use Security Key C NFC as backup for 5C NFC if I use OpenPGP?
Instead, most people generate keypair(s) on an airgapped machine and write them to two Yubikeys. Or write subkeys to a single Yubikey and keep a backup in encrypted form. See https://github.com/drduh/YubiKey-Guide
-
Ask HN: Why does YubiCo need my private key?
I'd recommend using the Yubikey as a GPG smartcard[1]. The private key stays on the Yubikey. I also use it for ssh. But make sure you have a backup key or two, just in case the primary Yubikey gives out. FIDO2 and all other regular Yubikey functionality still works with it.
[1]: https://github.com/drduh/YubiKey-Guide
-
An Opinionated Yubikey Set-Up Guide
The excellent guide by drduh should be mentioned here: https://github.com/drduh/YubiKey-Guide — I've been using this approach for years to store my OpenPGP keys on Yubikeys and use them for SSH.
I don't generate my keys on devices. That lets me be flexible and keep backups, as well as use the same keys on multiple physical devices. Using a single yubikey is a bad idea, as you're bound to eventually lose it or break it. Hasn't happened to me yet in 5 years, but I expect it to happen.
-
How to use Yubikey to login into a server
I followed this guide to generate a master key and three subkey.
- Guide to Using Yubikey for GPG and SSH
-
GnuPG Private Key storage on YubiKey: Why are the private keys still present in my .gnupg/ folder?
See https://github.com/drduh/YubiKey-Guide . Also google for OpenPGP card specifications, they will answer your question
-
Got myself Yubikey and set it up for my password manager and email. What next?
Regarding GPG/SSH keys, there is a great howto: https://github.com/drduh/YubiKey-Guide
-
Some guidance from those who use their Yubikey to protect their SSH connections.
I'd be lying if I said I understood all of that. I'm definitely going to do some research ahaha. Someone else on this post sentence this like which they said was very good guide. https://github.com/drduh/YubiKey-Guide
-
When it comes to storing PGP keys what is the difference between a YubiKey and a standard USB key
When storing the key on a Yubikey, however, all you need is just the PIN in order to use the key. It can contain numbers, letters, symbols, etc. and can be quite long, so you can treat it as a passphrase for all intents and purposes. There are actually two PIN codes: one regular one, for a read access, and another administrative one, for write access for when you want to modify the gpg applet settings or the key on the Yubikey. There is also a limit to how many times in a row you can enter pins incorrectly, after which the gpg applet gets locked and the only thing you can do is reset it, erasing the PGP keys. See https://github.com/drduh/YubiKey-Guide for more information.
-
Issues moving OpenPGP encryption & authentication keys to YubiKey 5C
Try follow this guide from DrDuh https://github.com/drduh/YubiKey-Guide/blob/master/README.md
What are some alternatives?
trufflehog - Find and verify secrets
solo1 - Solo 1 firmware in C
gitleaks - Protect and discover secrets using Gitleaks 🔑
wsl2-ssh-pageant - bridge between windows pageant and wsl2
secretlint - Pluggable linting tool to prevent committing credential.
sops - Simple and flexible tool for managing secrets
shhgit - Ah shhgit! Find secrets in your code. Secrets detection for your GitHub, GitLab and Bitbucket repositories.
wsl-ssh-pageant - A Pageant -> TCP bridge for use with WSL, allowing for Pageant to be used as an ssh-ageant within the WSL environment.
aws-vault - A vault for securely storing and accessing AWS credentials in development environments
secretive - Store SSH keys in the Secure Enclave
SecretFinder - SecretFinder - A python script for find sensitive data (apikeys, accesstoken,jwt,..) and search anything on javascript files
IsoApplet - A Java Card PKI Applet aiming to be ISO 7816 compliant