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 a day ago | parent | next [-]

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 a day ago | parent [-]

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 a day ago \| parent [-]
		That doesn't help if revocation, without renewal means immediate outage.

▲

jbverschoor a day ago | parent | prev [-]

Yet people complain that Netflix/Youtube pull certain content ;)

	▲	tobyhinloopen a day ago \| parent [-]
		Yes, because paying customers will have the content removed but it will continue to be available for pirates.