(trufflesecurity.com)

199 points elza_1111 | 1 comments | 03 Jul 25 06:44 UTC | HN request time: 0.206s | 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.

1. tobyhinloopen ◴[03 Jul 25 08:15 UTC] No.44452799[source]▶

Anything pushed is to be considered leaked. You might as well leave the commit in and invalidate the secret.

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