That’s not how it worked. Secured secrets were read from the context where they are used and printed to logs (albeit run through base64 twice). E.g. here’s the API key for the automation to use the API but it’s not just used, it’s also printed.
The prevention to this situation has nothing to do with secrets and everything to do with pinning 3rd party actions to specific commits. Release versions are not immutable.
I’m very glad that the compromise didn’t reach out with the secrets, so private repos got hit with a switch and not a 2x4.
That’s not how it worked. Secured secrets were read from the context where they are used and printed to logs (albeit run through base64 twice). E.g. here’s the API key for the automation to use the API but it’s not just used, it’s also printed.
The prevention to this situation has nothing to do with secrets and everything to do with pinning 3rd party actions to specific commits. Release versions are not immutable.
I’m very glad that the compromise didn’t reach out with the secrets, so private repos got hit with a switch and not a 2x4.
Thank you for the clarification.