Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://squirrelmob.com/@bedast" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bedast</span></a></span> My problem is that these people <em>refuse</em> to take the <em>correct consequences</em> and migrate away from garbage:</p><ol><li><p>You <em>just don't</em> install such garbage on <a href="https://infosec.space/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unix</span></a>-esque Systems like <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>!</p></li><li><p><a href="https://infosec.space/tags/CrowdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CrowdStrike</span></a> is just yet another <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Scareware</span></a> <a href="https://infosec.space/tags/Scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Scam</span></a>.</p></li><li><p>The entire business model of <a href="https://infosec.space/tags/AntiVirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AntiVirus</span></a> and other Scareware shouldn't exist to begin with.</p></li><li><p>3rd party <a href="https://infosec.space/tags/BinaryBlobs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BinaryBlobs</span></a> on a non-<a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a>'d kernel are just bad!</p></li><li><p>It should be <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a>'s sole tesponsibility to just not allow <a href="https://infosec.space/tags/Rootkits" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Rootkits</span></a> / <a href="https://infosec.space/tags/Bootkits" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bootkits</span></a> like that to exist eith their blessing aka. <a href="https://infosec.space/tags/Signature" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Signature</span></a> on.</p></li><li><p><a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows</span></a> &amp; <a href="https://infosec.space/tags/WindowsServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WindowsServer</span></a> are unbelieveably <a href="https://infosec.space/tags/cursed" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cursed</span></a> and unmaintainable mess that'll make even <a href="https://infosec.space/tags/Solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Solaris</span></a> 7 look clean and sleek.</p></li><li><p>The diversity of Linux and Unix-esque distros like <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a>'s make it basically impossible to bmhave such a giant and direct effect.</p></li><li><p>The whole issue should've been avoided throug extensive testing because it's certainly so rampant that it would've been picked up by <a href="https://infosec.space/tags/QA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>QA</span></a> testers.</p></li><li><p>The fuckedup-ness of <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CensorBoot</span></a> aka. <em>"<a href="https://infosec.space/tags/SecureBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SecureBoot</span></a>"</em> (which is insecure af - see <a href="https://infosec.space/tags/GoldenKeyBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GoldenKeyBoot</span></a>!) is the reason why this results in such catastrophic failures, whereas on <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> one just uses <a href="https://infosec.space/tags/LUKS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LUKS</span></a> and can easily recover files.</p></li><li><p>Most Windows users &amp; -<a href="https://infosec.space/tags/sysadmins" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysadmins</span></a> neglect <a href="https://infosec.space/tags/Backups" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Backups</span></a> of Windows machines because there is no good way to backup them!</p></li><li><p>3rd party kernel binaryblobs are <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malware</span></a>, regardless if <em>"Anti-Malware"</em> or <em>"<a href="https://infosec.space/tags/AntiCheat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AntiCheat</span></a>"</em> is the claimed functionality.</p></li><li><p>If I don't trust <a href="https://infosec.space/tags/WindowsDefender" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WindowsDefender</span></a> then I don't trust Windows or rather Microsoft and thus have to cease using it!</p></li><li><p><a href="https://nondeterministic.computer/@mjg59/112816011370924959" rel="nofollow noopener" target="_blank">This shit would not have been possible under Linux</a>!</p></li></ol>