3 ms·

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

by ggm 1y ago

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.

Sayrus 1y ago
If you push a secret publicly, you should consider it leaked. On GitHub, you have 5 minutes on a non-watched repository (due to the delay) and less than 30 seconds on a watched repository to revoke it before it's been cloned and archived by a third-party. Whether that party is malicious or not, rewriting the Git history will not change anything that the secret is leaked. And you can already rewrite the Git History and garbage collect commits that aren't part of the tree anymore on most providers.
- ggm 1y ago
  Yes I can see my off-line experience doesn't apply. Thanks.
volemo 1y ago
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.
- gghffguhvc 1y ago
  The person who leaked it and the person/team that can rotate it might be in different silos or timezones etc. Rewriting the history is prudent but not sufficient.
  - orthoxerox 1y ago
    That's why key revocation, like credit card blocking, should be a separate service that is available 24x7. Like, if you know the value of an AWS token, this should be sufficient data for you to call an AWS API that revokes it.
    - badmintonbaseba 1y ago
      That doesn't help if revocation, without renewal means immediate outage.
- jbverschoor 1y ago
  Yet people complain that Netflix/Youtube pull certain content ;)
  - tobyhinloopen 1y ago
    Yes, because paying customers will have the content removed but it will continue to be available for pirates.
tobyhinloopen 1y ago
Anything pushed is to be considered leaked. You might as well leave the commit in and invalidate the secret.

by ggm 1y ago

Sayrus 1y ago

If you push a secret publicly, you should consider it leaked. On GitHub, you have 5 minutes on a non-watched repository (due to the delay) and less than 30 seconds on a watched repository to revoke it before it's been cloned and archived by a third-party. Whether that party is malicious or not, rewriting the Git history will not change anything that the secret is leaked. And you can already rewrite the Git History and garbage collect commits that aren't part of the tree anymore on most providers.

ggm 1y ago
Yes I can see my off-line experience doesn't apply. Thanks.

volemo 1y ago

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.

gghffguhvc 1y ago
The person who leaked it and the person/team that can rotate it might be in different silos or timezones etc. Rewriting the history is prudent but not sufficient.
- orthoxerox 1y ago
  That's why key revocation, like credit card blocking, should be a separate service that is available 24x7. Like, if you know the value of an AWS token, this should be sufficient data for you to call an AWS API that revokes it.
  - badmintonbaseba 1y ago
    That doesn't help if revocation, without renewal means immediate outage.
jbverschoor 1y ago
Yet people complain that Netflix/Youtube pull certain content ;)
- tobyhinloopen 1y ago
  Yes, because paying customers will have the content removed but it will continue to be available for pirates.

tobyhinloopen 1y ago

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