NEVER, EVER commit the vault/ directory to Git!
vault/
βββ GOOGLE/
β βββ YOUR_ACTUAL_API_KEYS_HERE
βββ GITHUB/
β βββ YOUR_ACTUAL_TOKENS_HERE
βββ [OTHER_SERVICES]/
βββ YOUR_ACTUAL_SECRETS_HERE
This directory contains YOUR REAL API KEYS. If you accidentally commit it:
- Your keys will be compromised
- Bad actors could use your API quotas
- You might get charged money
- Your accounts could be hijacked
- Opens browser tabs to official API pages
- Provides step-by-step guides
- Stores keys locally on YOUR machine
- Looks incredibly cool while doing it
- Hack anything
- Bypass security
- Generate fake API keys
- Share your keys anywhere
- Connect to any external servers
-
Check .gitignore is working
git status # Make sure no vault/ files appear! -
If you see vault files in git status:
# DO NOT COMMIT! git rm --cached -r vault/ git commit -m "Remove vault from tracking"
-
Rotate keys regularly
- GitHub tokens: Every 90 days
- API keys: Follow service recommendations
- Passwords: Use a password manager
-
Never share your vault
- Don't zip and email it
- Don't screenshot keys
- Don't commit to ANY repository
If you accidentally committed API keys:
-
Immediately revoke the exposed keys
- GitHub: Settings β Developer settings β Personal access tokens
- Google: Cloud Console β Credentials
- OpenAI: Account β API keys
- [Other services: check their security settings]
-
Remove from Git history
# Use BFG Repo-Cleaner (easier) bfg --delete-files "*.key" --delete-folders "vault" # Or git filter-branch (harder) git filter-branch --force --index-filter \ 'git rm -r --cached --ignore-unmatch vault/' \ --prune-empty --tag-name-filter cat -- --all
-
Force push to update remote
git push --force --all git push --force --tags
-
Generate new keys for all services
Found a security issue with this tool? Please:
- Do NOT post it publicly
- Email: [your-email@example.com]
- Allow 48 hours for response
- Be radical, but responsible
Before sharing or publishing:
- Vault directory is in .gitignore
- No keys in any .bat files
- No keys in README or docs
- Git history is clean
- Test files don't contain real keys
- Screenshots don't show real keys
Remember: Looking like a hacker is cool. Being secure is cooler.
[SECURITY PROTOCOLS: ENGAGED]
[ENCRYPTION: MAXIMUM]
[PARANOIA LEVEL: APPROPRIATE]