News for hackers. Stuff that matters.
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by paradite on Friday October 14, 2022 @02:06AM (#33200147)
I have an idea:

What if companies using secret keys (not SaaS providers who generate secret keys) voluntarily send their secret keys (MD5 hashed or somehow encrypted) to GitHub and GitHub can then monitor their leakage and notify the company?

Is this useful or feasible?

Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by devcat on Friday October 14, 2022 @02:13AM (#33200174)
Github already has system to invalidate tokens without storing any hashes themselves https://docs.github.com/en/code-security/secret-scanning/sec...
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by paradite on Friday October 14, 2022 @02:17AM (#33200188)
Yes. This is dependent on some kind of agreement or understanding between SaaS provider and GitHub.

I'm thinking of a generic approach which is independent of where you got the secret key and its format.

Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by devcat on Friday October 14, 2022 @02:23AM (#33200222)
Same system can be applied for repo owner being pattern provider and getting notified with matches but if i had to guess only enterprise customers might get feature like this