Conversation

Notices

1. Embed this notice
   :marseyloadingneon: m0xEE :marseyloading: (m0xee@breloma.m0xee.net)'s status on Sunday, 31-Mar-2024 02:47:05 JST :marseyloadingneon: m0xEE :marseyloading:

   • Johnny Peligro
   @mischievoustomato
   This is exactly what I'm talking about — most seem to only worry about sshd, but in fact so much more could be affected.
   Downgrading to liblzma5.4.x isn't panacea — it's just the most obvious quick fix.
   And of course it doesn't mean that only systemd-systems are affected, some lzma shit is in the kernel even — we don't know what could get in there when the project was basically taken over by hostile actors.
   We have to wait for the results of proper source audit to feel safe again.
   • Pleroma-tan likes this.
   • Embed this notice
     Pleroma-tan (kirby@lab.nyanide.com)'s status on Sunday, 31-Mar-2024 02:52:54 JST Pleroma-tan

     in reply to

     • Johnny Peligro
     @m0xEE @mischievoustomato lmao at least the infected xz is off my system