Someone tries to post a helpful PSA type message and predictably the comments section is immediately flooded with people who have nothing of any value to say, but can't help but be assholes and make some kind of stupid "Windoze $ux!" type comment. We're all happy that Linux, macOS, or whatever the fuck else you might be using works for you, now kindly take your insecurities back to Linux or Mac forums where you can blissfully live out the rest of your days in a happy echo chamber where no one will ever chal
by Anonymous Coward writes:
on Friday June 29, 2018 @01:08AM (#56863580)
I don't think the posts have been entirely unfair. If removal of the malware can be done manually, I don't see why it couldn't also be automated. That's a bit confusing to me. I think it's fair to criticize Windows because for far too long, security on that OS was a joke. Admittedly, Microsoft has improved things, but there are also a lot of users who are far too gullible.
With respect to this specific story, the summary is very light on technical details. It reads like something that's written for the general public rather than for nerds who generally have a technical background. The announcement may well be useful, but it could be written in a way that's much more in line with what we generally expect on Slashdot. If this requires manual removal, I'd like to see what it is about this particular threat that prevents it from being handled automatically. It is also useful to specify the OS because there are plenty of rootkits for *nix systems. A remote hole in a daemon providing network services and a privilege escalation vulnerability could allow rootkits to be installed through remote holes. Compromised software packages installed through otherwise legitimate sources is probably a simpler way to deliver a rootkit. Specifying the OS matters, especially on a site where a large percentage of people don't run Windows. That's not an excuse to bash Microsoft, but about providing helpful information to the readers of this site.
Look at IOCs. Random file names, random services, and rootkits. Makes it hard to create an automated script that anyone can download and use.
Look at smart service for example. Malware devs changed that constantly to the point that antivirus just gave up on it. Malwarebytes used to do a good job and no longer have too to automate its removal.
Some of this stuff is not as easy as you think.
Of course ultimately anything could be automated with enough man power to keep up, but I donâ(TM)t think that was th
This is why we can't have nice things (Score:1)
Someone tries to post a helpful PSA type message and predictably the comments section is immediately flooded with people who have nothing of any value to say, but can't help but be assholes and make some kind of stupid "Windoze $ux!" type comment. We're all happy that Linux, macOS, or whatever the fuck else you might be using works for you, now kindly take your insecurities back to Linux or Mac forums where you can blissfully live out the rest of your days in a happy echo chamber where no one will ever chal
Re:This is why we can't have nice things (Score:0)
I don't think the posts have been entirely unfair. If removal of the malware can be done manually, I don't see why it couldn't also be automated. That's a bit confusing to me. I think it's fair to criticize Windows because for far too long, security on that OS was a joke. Admittedly, Microsoft has improved things, but there are also a lot of users who are far too gullible.
With respect to this specific story, the summary is very light on technical details. It reads like something that's written for the general public rather than for nerds who generally have a technical background. The announcement may well be useful, but it could be written in a way that's much more in line with what we generally expect on Slashdot. If this requires manual removal, I'd like to see what it is about this particular threat that prevents it from being handled automatically. It is also useful to specify the OS because there are plenty of rootkits for *nix systems. A remote hole in a daemon providing network services and a privilege escalation vulnerability could allow rootkits to be installed through remote holes. Compromised software packages installed through otherwise legitimate sources is probably a simpler way to deliver a rootkit. Specifying the OS matters, especially on a site where a large percentage of people don't run Windows. That's not an excuse to bash Microsoft, but about providing helpful information to the readers of this site.
Re: This is why we can't have nice things (Score:0)
Look at IOCs. Random file names, random services, and rootkits. Makes it hard to create an automated script that anyone can download and use.
Look at smart service for example. Malware devs changed that constantly to the point that antivirus just gave up on it. Malwarebytes used to do a good job and no longer have too to automate its removal.
Some of this stuff is not as easy as you think.
Of course ultimately anything could be automated with enough man power to keep up, but I donâ(TM)t think that was th