←back to thread

I scanned all of GitHub's "oops commits" for leaked secrets

(trufflesecurity.com)
199 points elza_1111 | 1 comments | 03 Jul 25 06:44 UTC | HN request time: 0.204s | source
Show context
ggm ◴[03 Jul 25 07:13 UTC] No.44452457[source]▶
Maybe a default secure delete option could be made a lower bar event?

Checkout to event, commit in clean state with prior log history, overlay the state after the elision and replace git repo?

When I had to retain log and elide state I did things like this in RCS. Getting date/time info right was tricky.

replies(3): >>44452527 #>>44452528 #>>44452799 #
volemo ◴[03 Jul 25 07:27 UTC] No.44452528[source]▶
If something got out to the internet, you won't get it back. There is little point in rewriting repo history if you have already made a secret public. Just change the secret as soon as you can.
replies(2): >>44452555 #>>44452635 #
jbverschoor ◴[03 Jul 25 07:46 UTC] No.44452635[source]▶
Yet people complain that Netflix/Youtube pull certain content ;)
replies(1): >>44452807 #
1. tobyhinloopen ◴[03 Jul 25 08:15 UTC] No.44452807[source]▶
Yes, because paying customers will have the content removed but it will continue to be available for pirates.