Saltar al contenido ForoHackers

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

CI/CDRespuesta a incidentesSeguridad de la cadena de suministro
#18569 · · Citar · Denunciar

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 · · Citar · Denunciar

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 · · Citar · Denunciar

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 · · Citar · Denunciar

¿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 · · Citar · Denunciar

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 · · Citar · Denunciar

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 · · Citar · Denunciar

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.

No has iniciado sesión, así que esto se publica como anónimo: no se guarda con ello ninguna cuenta, nombre ni dirección, y no puede llevar enlaces ni imágenes. Inicia sesión o únete para publicar con tu nombre. Los registros de nuestro servidor web guardan la dirección y la hora de cada petición hasta 14 días; para que la tuya no quede en ellos, usa Tor. Para escribir al equipo de forma confidencial, usa el buzón. Firmar como fuente habitual (una clave guardada solo en este navegador)

Enviar tarda unos segundos aquí: tu navegador resuelve antes una prueba de trabajo contra el spam.

Responder