5 ms·
>following new repos and scanning them for leaked credentials could be a negative People do this. GitHub started doing it too so now you get a nice email from
by colechristensen 1y ago
>following new repos and scanning them for leaked credentials could be a negative
People do this. GitHub started doing it too so now you get a nice email from them first instead of another kind of surprise.
- mdaniel 1y agoEmail, bleh, I'm sure I'm not the only one who basically /dev/null's emails from github about pearl-clutching "security" but I wanted to point out that for quite a few providers they actually have an integration to revoke them if found in a public repo, which I think is way more handy https://docs.github.com/en/code-security/secret-scanning/secret-scanning-partnership-program/secret-scanning-partner-program#the-secret-scanning-process https://docs.github.com/en/code-security/secret-scanning/sec... and the list is way bigger than I recalled: https://docs.github.com/en/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#default-patterns https://docs.github.com/en/code-security/secret-scanning/int...
- colechristensen 1y agoYou can turn those GitHub security warnings off if you don't want them. >quite a few providers they actually have an integration to revoke them if found in a public repo, which I think is way more handy Yes I've also gotten an email from Amazon saying they revoked a key someone inadvertently leaked (but so long ago I only remember that it happened). I read my AWS emails at least.