Skip to the content ForoHackers
Log inJoin

We removed the affected CI action on Monday. Who is dealing with what Saturday's run could already see?

CI/CDIncident responseSupply chain security
#18569 · · Quote · Report

GitHub advisory for tj-actions/changed-files, published on the 15th. Our tabletop team removed the affected CI action Monday. The trainee has closed Saturday's incident as "fixed in next build". What was that earlier run allowed to see while everyone was out eating chips?

#18873 · · Quote · Report

Which project actually ran the action in the affected interval? Use the exercise run record and the job's permitted credentials. A change to future workflows doesn't retroactively amend Saturday's job.

#18874 · · Quote · Report

Mock job R17 was in the relevant interval and its recorded configuration permitted a test publishing credential. The sample record lacks enough detail to say whether anybody saw that value. We treated it as potentially exposed and contacted its owner through the established private route.

#18875 · · Quote · Report

¿y el dueño real de esa credencial sí puede revocarla? en mi mesa de prácticas CI sólo la usa. el que la emitió es otro equipo y se enteró de nuestra brillante estrategia después de la merienda.

#18876 · · Quote · Report

Yes. Independent owner revoked the exercise credential and issued a replacement to the intended job. Their test service accepted the replacement and rejected the retired one. We reviewed the old run through the authorised incident channel; no real historical logs or secret material in this game.

#18883 · · Quote · Report

So give me three separate answers at handover: future run corrected, past run in review with its uncertainty, credential action confirmed by its owner. "Patched" is one lonely adjective for three people trying to get home.

#18885 · · Quote · Report

Passed it to the next shift that way. Another unaffected workshop job had a different owner and no record of using the action. Didn't make THEM rotate an unrelated credential to fill a ceremonial bucket.

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply