101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

504
active users

#windowsdefender

0 posts0 participants0 posts today

I just replied to a blog comment, and I thought that I post my reply here as well:

I think that I have good reasons to be “against Avast,” having published seven articles on them so far. The security issues alone are bad enough. But Avast abused their position to collect and sell users’ browsing profiles. After they were caught they claimed the data to be anonymized, they claimed to only sell aggregated data – and they continue lying to this day, despite there being conclusive evidence to the contrary. While the company has been bought, it’s still the same people in charge. This sort of undermines any trust in them for anything related to security.

As the security of antivirus software goes, I’m not very fond of any as the articles in the “antivirus” category of my blog show. With Kaspersky it wasn’t only the security issues but also how they handled them, pushing out half-hearted fixes only for these to be circumvented shortly afterwards. McAfee and BullGuard had massive security issues stemming from being careless about security and not following best practices.

I’ve found a critical security issue in Bitdefender’s solution as well, but with them I at least had the impression that they were trying. Unfortunately, that’s currently the bar in the antivirus industry – at least trying to make their product secure.

Security-wise, one good thing about Windows Defender is that it only needs to do one job. It doesn’t need all the extra functionality as a selling argument. It doesn’t need to be a banking browser, it doesn’t need to be a phishing protection, it only needs to be an antivirus solution. It can keep a very small attack surface compared to all those antivirus suites, and so it does (yes, I checked).

@bedast My problem is that these people refuse to take the correct consequences and migrate away from garbage:

  1. You just don't install such garbage on #Unix-esque Systems like #Linux!

  2. #CrowdStrike is just yet another #Scareware #Scam.

  3. The entire business model of #AntiVirus and other Scareware shouldn't exist to begin with.

  4. 3rd party #BinaryBlobs on a non-#FLOSS'd kernel are just bad!

  5. It should be #Microsoft's sole tesponsibility to just not allow #Rootkits / #Bootkits like that to exist eith their blessing aka. #Signature on.

  6. #Windows & #WindowsServer are unbelieveably #cursed and unmaintainable mess that'll make even #Solaris 7 look clean and sleek.

  7. The diversity of Linux and Unix-esque distros like #BSD's make it basically impossible to bmhave such a giant and direct effect.

  8. The whole issue should've been avoided throug extensive testing because it's certainly so rampant that it would've been picked up by #QA testers.

  9. The fuckedup-ness of #CensorBoot aka. "#SecureBoot" (which is insecure af - see #GoldenKeyBoot!) is the reason why this results in such catastrophic failures, whereas on #Linux one just uses #LUKS and can easily recover files.

  10. Most Windows users & -#sysadmins neglect #Backups of Windows machines because there is no good way to backup them!

  11. 3rd party kernel binaryblobs are #malware, regardless if "Anti-Malware" or "#AntiCheat" is the claimed functionality.

  12. If I don't trust #WindowsDefender then I don't trust Windows or rather Microsoft and thus have to cease using it!

  13. This shit would not have been possible under Linux!

Nondeterministic ComputerMatthew Garrett (@mjg59@nondeterministic.computer)"Linux would have prevented this!" literally true because my former colleague KP Singh wrote a kernel security module that lets EDR implementations load ebpf into the kernel to monitor and act on security hooks and Crowdstrike now uses that rather than requiring its own kernel module that would otherwise absolutely have allowed this to happen, so everyone please say thank you to him

I have said before, but it bears repeating: to all the people screaming "Defender is the best", #windowsdefender is buggy. I don't know if it's the UI or the threat removal, but it has:
- detected a file sitting on disk (not an infection)
- removed it
- still keeps detecting it
This is not an infected system. This is not active malware.
If this was a real system, you want Defender to detect the threat, remove it, and be done. Instead, it took several times to even remove it (again, not an active infection, but a malware sample in a zip file).
It's also inconsistent. One part of the UI says threats are detected, but when I click, no threats are shown.

Continued thread

Zzz… #Windows10 update is up to 92% now (91% in the picture), and it seems to be going at 1% per 5-10 minutes or so…

Looks like #Windows is also doing a #WindowsDefender scan in the background, probably part of the update process.

The #English language pack update also seems to be stuck in the background, so for now I'll have to live with a #Norwegian UI. I guess good practice?

Yeah, not going to be using this system tonight, so I'll just try to get some sleep.

mastodon.social/media/cHX0GFe3