Possibly linux@lemmy.zip to linuxmemes@lemmy.worldEnglish · 2 months agoIt is called 🍷lemmy.zipexternal-linkmessage-square74fedilinkarrow-up1548arrow-down118
arrow-up1530arrow-down1external-linkIt is called 🍷lemmy.zipPossibly linux@lemmy.zip to linuxmemes@lemmy.worldEnglish · 2 months agomessage-square74fedilink
minus-squareacockworkorange@mander.xyzlinkfedilinkarrow-up2·2 months agoHow so? Is there a way for malicious code to start injecting itself into calls to 127.0.0.1?
minus-squarePetter1@lemm.eelinkfedilinkarrow-up3·edit-22 months agoSorry, I am not an expert myself, but I think there are some recourses about that in the internet Or, this file on x.org: “But the X protocol is still unsecure by design…” https://www.x.org/wiki/Events/XDC2014/XDC2014DodierPeresSecurity/xorg-talk.pdf
minus-squareacockworkorange@mander.xyzlinkfedilinkarrow-up4·2 months agoYeah, to send it naked over the wire would be nuts, which is why everybody uses SSH. But unless there’s insecurity within the computer, that’s a moot point.
How so? Is there a way for malicious code to start injecting itself into calls to 127.0.0.1?
Sorry, I am not an expert myself, but I think there are some recourses about that in the internet
Or, this file on x.org:
https://www.x.org/wiki/Events/XDC2014/XDC2014DodierPeresSecurity/xorg-talk.pdf
Yeah, to send it naked over the wire would be nuts, which is why everybody uses SSH. But unless there’s insecurity within the computer, that’s a moot point.