zlacker

[return to "Firefox engineers discover a Windows Defender bug that causes high CPU usage"]
1. ravens+Df[view] [source] 2023-04-05 20:06:47
>>mconle+(OP)
Windows Defender is a long standing bug in the Windows operating system. ;)

My impression is that its invention was for the sole purpose of eradicating the idea that Windows is insecure and prone to viruses, which explains why it can be overzealous and CPU hungry.

I would only enable it for family members who don't know what they are doing. For some reason, I haven't needed any form of active virus scanning in something like 15 years. If it turns out I've been infected this entire time, the criminals sure are taking their time stealing my money, etc.

◧◩
2. thewat+si[view] [source] 2023-04-05 20:25:24
>>ravens+Df
There's a misconception that you need to do something "stupid" to get a virus which is simply not the case. 0 days exist, and worms are still a thing (looking at you samba).

A great example is Pytorch just recently had a supply chain attack, and installing the nightly version between December 25th and December 30th, 2022 - would result in your home directory getting uploaded including ssh keys.

Chrome also just had a 0 day 2022 - CVE-2022-3075

Pytorch supply chain attack via Triton 2022/2023 - https://www.bleepingcomputer.com/news/security/pytorch-discl...

EDIT: Also there's a misconception that linux somehow doesn't get viruses - however the Pytorch attack affected linux users. Making a virus for windows gives you far more targets then linux, which is why they're far more common.

◧◩◪
3. lionko+Xk[view] [source] 2023-04-05 20:37:53
>>thewat+si
windows users will also happily "run as administrator", while a lot of linux users know not to do that in my experience
◧◩◪◨
4. 0x457+Q21[view] [source] 2023-04-06 01:07:48
>>lionko+Xk
Honestly...I'm far for afraid of my $HOME being uploaded somewhere. You don't need "run as administrator" for that.
◧◩◪◨⬒
5. thewat+hg2[view] [source] 2023-04-06 12:28:55
>>0x457+Q21
> You don't need "run as administrator" for that.

This is what makes it so doable since you don't need any privilege escalation.

The reason why this is a big deal for a lot of people is your ssh keys will give you access to your git repos and other servers unless you have them password protected or use gpg/sk ssh keys which I think a lot of people don't do.

And of course if you can see the known hosts file/bash_history you'll likely have access to more servers to propagate to.

Also things like your browser cache is stored there.

◧◩◪◨⬒⬓
6. 0x457+r84[view] [source] 2023-04-06 21:20:52
>>thewat+hg2
Plenty of dangerous things stored in `~/`, they don't even need password for ssh-key if there is ssh-agent running (this is in case of dangerous process running, not just upload).

This is why I store keys on a hardware key that requires me to touch it when used and manually start ssh-agent when doing a lot of `git push`.

◧◩◪◨⬒⬓⬔
7. thewat+uS6[view] [source] 2023-04-07 18:35:16
>>0x457+r84
Yeah gpg/sk ssh keys are definitely the way to go.
[go to top]