4 ms·
Why did they do this then? https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning https://docs.github.com/en/code-security/secret-scanni
by belter 5y ago
Why did they do this then?
https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning https://docs.github.com/en/code-security/secret-scanning/abo...
- SahAssar 5y agoThey have a way to deal with this, considering the original article either it is the fault of mozilla to not have a signature to submit to this list or it is the fault of users committing secrets to public repos. Either way it is not the fault of github IMO. In my mind it is mostly the fault of users.
- psanford 5y agoSecret scanning is done in partnership with third parties to detect and revoke api credentials. It is based on regexp matching and involves making a call to a webhook owned by the third party to revoke the secret. That doesn't work for arbitrary cookies.