It actually is a thing, although indirectly in a hacky way! If you push keys from GitHub secret scanning partners to a public repo or a gist, they get sent to the partner who (usually) instantly revoke them. So if you want to help someone, just make a public gist with the key and delete it like 15 seconds later, it'll be enough.
replyhttps://docs.github.com/en/code-security/reference/secret-se... has a table with the active partners
Only responsible thing in this case would have been for OpenCode people to invalidate all keys. But I guess it is not that straightforward if Anthropic/OpenAI etc don't have endpoint for it.
replyThere's no self-serve endpoint, but OpenCode could send the inference providers the leaked keys and ask for them to be revoked, which is a thing the inference providers can do. It's possible that this'll happen, apparently remediation is still in progress.
replyThat just turns a credential leak into a denial of service - one that can be triggered from anywhere.
replyIn this case you'd probably prefer your key to be disabled rather than spending $$$ on tokens for everyone else
replyThink that through - the person who stole the key has the decision to use it or revoke it through this hypothetical system.
replyIf they are acting maliciously, they will take the choice that most hurts you and/or benefits them.
If the key is useless to them and revoking it hurts you, then they would do that.
If the key wasn’t useless to them, then… they would just use it and not revoke it?
It for whitehat third parties who discover unprotected keys obviously people intentionally stealing keys will not revoke them generally.
replyAnd the whitehack hackers finding keys should do what, exactly?
replyUnilaterally decide they should be revoked, without contacting the owner?
And that’s not malicious?
Not any more than any other public endpoint service exposes.
This revocation endpoint can be protected by auth too. Use API key that you're revoking in auth.
replyHow does that make any sense?
replyI see now from another comment you thought about denial of service for service that leaked key. And I thought about mass leak resulting in DDOS onto API provider. Wrong guess from me.
replyYes. Is this a bad thing?
replyOf course it is? A key for some weather API getting leaked isn’t the end of the world, but having it revoked and breaking your weather app is.
reply