3 ms·
0% chance of validity. GitHub watch for those and notify the provider of the API key so it can be revoked, as well as emailing the owner(s) of the repo which c
by naikrovek 4y ago
0% chance of validity.
GitHub watch for those and notify the provider of the API key so it can be revoked, as well as emailing the owner(s) of the repo which contained the key.
if it was in enough places that it got reproduced exactly via neural network, then there is zero chance it escaped their secret-scanners.
they even have some GHAS feature that lets you define your own regexes for secrets and will notify you if any are found.
none of this makes it safe to store secrets in code, though, these things just help tell you when you've done it.
- jen20 4y ago[1] suggests otherwise, at least at launch. If you’re telling me there is NO WAY this could still happen (“zero chance”), that is absolutely a bet I’d place. [1]: https://fossbytes.com/github-copilot-generating-functional-api-keys/ https://fossbytes.com/github-copilot-generating-functional-a...
- deleted 4y ago[deleted]
- naikrovek 4y agoI'm talking about the present, not launch. if I argue that "cars in the US must be equipped with seat belts," would you say "not before 1968!" and believe that we were both talking about the same time period? I guess, as always, I should be absolutely specific about everything, lest someone fill in a gap incorrectly...
- jen20 4y agoI simply don’t believe that sufficient safeguards have been put in place to avoid violating licenses or leaking information. You can choose to, but a bet that there is “zero chance” is pretty foolish. I’ve bookmarked this comment for the inevitable.
- naikrovek 4y agoyour idea of inevitable is not really based in reality, I think. but ok. I'll have fun occupying a small portion of your brain for a while.
- jen20 4y agoThis didn’t take long… https://twitter.com/DocSparse/status/1581461734665367554 https://twitter.com/DocSparse/status/1581461734665367554