If you run random .pdf.something-files pm‘d to you on LinkedIn you probably shouldn’t use a computer anyway, no matter if it runs Linux or Windows…
post
Joke’s on them, I don’t use bash.
Seriously though, Linux will probably get targeted more frequently now that it is becoming more popular as a desktop OS.
But you probably have Bash? In this case, #!/bin/bash still runs it.
Yeah but according to the article it installs itself in .bash_profile.
So doesn't the user have to add +x to run this?
It never occurred to me before reading this comment that there actually is a use case for the execute permission. To me it was always just this annoying thing I have to do whenever I download an executable which I didn't have to do on Windows.
Hm, maybe there should be an option to always disable the executable permission when extracting
Zip too? I thought only on Windows, while tar retains unix permissions.
how someone working on software and tech opens a file called "HSBC job offer.pdf.zip" is beyond me...
Still the exploit is easier to avoid compared to windows viruses and stuff. Even with the linux popularity increasing there is already out there good solutions to prevent this kinda stuff like have SELinux installed, use firejail to run suspicious files, use proxies to visit weird sites (you can use proxychains + tor, a bit overkill but works if you don't have a local proxy), etc.
Not to mention that one of the attack vectors of this exploit requires using a systemd feature which is the sysnetd which isnt going to work on other init systems. Reason why a lot of times minimalism can be superior to just having all the features + unnecessary ones out of the box.
I’m not gonna lie. I want any job, no matter how fake, that uses a reddened North Korean “Hotel of Doom” in its literature.
Wouldn't it show the icon of an executable file and ask if you want to open it or execute it?
all 31 comments