Shakedown Social

Kevin Karhan :verified:<a href="https://infosec.exchange/@cR0w" class="u-url mention" rel="nofollow noopener" target="_blank">@cR0w</a> OFC that is a general problem.<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> talked about that violation of <a href="https://infosec.space/tags/KISSprinciple" class="mention hashtag" rel="nofollow noopener" target="_blank">#KISSprinciple</a> in a talk <a href="https://www.youtube.com/watch?v=SGmtP5Lg_t0&t=26m5s" rel="nofollow noopener" target="_blank">over a decade ago.</a>Add to that the horrible track record of many vendors of <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> and we all can see the problem...

Kevin Karhan :verified:<a href="https://infosec.exchange/@cR0w" class="u-url mention" rel="nofollow noopener" target="_blank">@cR0w</a> <a href="https://infosec.exchange/@da_667" class="u-url mention" rel="nofollow noopener" target="_blank">@da_667</a> nodds in agreement<ul><li>I'm convinced <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> won't "fix" <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> (by migrating to <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> and merely integrating a <a href="https://infosec.space/tags/WindowsSubsystemForLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsSubsystemForLinux</a> (aka. <a href="https://infosec.space/tags/Wine" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wine</a>) instead of their botched <a href="https://infosec.space/tags/LinuxSubsystemForWindows" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxSubsystemForWindows</a>) because they do get $$$$$$$$ from the <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a>-<a href="https://infosec.space/tags/Scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scam</a>-Industry that is "<a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Antivirus</a>"-<a href="https://infosec.space/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#Software</a>!</li></ul>But the best are those "<a href="https://infosec.space/tags/AV" class="mention hashtag" rel="nofollow noopener" target="_blank">#AV</a>" Vendors that use <a href="https://infosec.space/tags/ClownFlare" class="mention hashtag" rel="nofollow noopener" target="_blank">#ClownFlare</a> "for <a href="https://infosec.space/tags/DDoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DDoS</a>-Protection" like some <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a> distributors from <a href="https://infosec.space/tags/Russia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Russia</a>.<ul><li>Makes them look really trustworthy!</li></ul>Personally, I just <a href="https://infosec.space/tags/ban" class="mention hashtag" rel="nofollow noopener" target="_blank">#ban</a> all <a href="https://infosec.space/tags/proproetary" class="mention hashtag" rel="nofollow noopener" target="_blank">#proproetary</a> file.formats & -protocols as a matter of principle!<a href="https://infosec.space/tags/CloudFlare" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudFlare</a>

Kevin Karhan :verified:<a href="https://infosec.space/@topher" class="u-url mention" rel="nofollow noopener" target="_blank">@topher</a> <a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Antivirus</a> is for the most part <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> aimed at scamming <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterates</a> which at best only works against kniwn threats and at worst is literal <a href="https://infosec.space/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Malware</a> in and of itself selling user data to bad actors.<ul><li>There are commercial AV options for major distros, like <a href="https://infosec.space/tags/ESET" class="mention hashtag" rel="nofollow noopener" target="_blank">#ESET</a> <a href="https://www.eset.com/ie/" rel="nofollow noopener" target="_blank">offers</a> for all 3 big Desktop ones: @RedHat, <a href="https://infosec.space/tags/SUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#SUSE</a> & <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener" target="_blank">#UbuntuLTS</a>...</li></ul>As for the rest one can just scan <a href="https://infosec.space/tags/Fileservers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fileservers</a> regularly and do so on <a href="https://infosec.space/tags/Mailservers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mailservers</a>, but existing tools to enforce quick and early updates on those distros already do most of the heavy lifting re: <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a>... <a href="https://infosec.space/tags/JustSayling" class="mention hashtag" rel="nofollow noopener" target="_blank">#JustSayling</a>

Kevin Karhan :verified:<a href="https://goatdaddy.net/profile/vvelox" class="u-url mention" rel="nofollow noopener" target="_blank">@vvelox</a> <a href="https://infosec.exchange/@SecurityWriter" class="u-url mention" rel="nofollow noopener" target="_blank">@SecurityWriter</a> +9001%Also the fact that <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> gave birth to an entire cottage industry of <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> producers is already an indictment to it's shortcomings for any serious <a href="https://infosec.space/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a>.<ul><li>But if you need "<a href="https://infosec.space/tags/CheckboxSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#CheckboxSecurity</a>" for some <a href="https://infosec.space/tags/compliance" class="mention hashtag" rel="nofollow noopener" target="_blank">#compliance</a> stuff, there are commercial solutions for that too.</li></ul>Cuz unlike <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a>'s <a href="https://infosec.space/tags/MDM" class="mention hashtag" rel="nofollow noopener" target="_blank">#MDM</a>, <a href="https://infosec.space/tags/InTune" class="mention hashtag" rel="nofollow noopener" target="_blank">#InTune</a> is a joke!

Kevin Karhan :verified:<a href="https://mastodon.social/@Kensan" class="u-url mention" rel="nofollow noopener" target="_blank">@Kensan</a> <a href="https://waldvogel.family/@marcel" class="u-url mention" rel="nofollow noopener" target="_blank">@marcel</a> <a href="https://chaos.social/@adfichter" class="u-url mention" rel="nofollow noopener" target="_blank">@adfichter</a> Das kommt hinzu...Ich persönlich bin ja dafür dass <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> eine strikte <a href="https://infosec.space/tags/Produkthaftung" class="mention hashtag" rel="nofollow noopener" target="_blank">#Produkthaftung</a> befolgen müssen - inklusive <a href="https://infosec.space/tags/Versicherung" class="mention hashtag" rel="nofollow noopener" target="_blank">#Versicherung</a> für <a href="https://infosec.space/tags/Folgesch%C3%A4den" class="mention hashtag" rel="nofollow noopener" target="_blank">#Folgeschäden</a> und Schadensersatzansprüche...<ul><li>Bei <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> würde ich dies nicht einsehen weil diese ja kostenlos und ohne Haftung angeboten wird - bei CCSS gibt es keinen rationalen Grund dies zu erlauben!</li></ul>Ohnehin gehört <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> wie <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> und <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> wie <a href="https://infosec.space/tags/CrowdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#CrowdStrike</a> und der ganze andere "<a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Antivirus</a>" - <a href="https://infosec.space/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Malware</a> verboten, weil alles was <a href="https://infosec.space/tags/Binaryblob" class="mention hashtag" rel="nofollow noopener" target="_blank">#Binaryblob</a>-<a href="https://infosec.space/tags/Kernelhacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kernelhacks</a> erzeugen ist Mist!

Kevin Karhan :verified:<a href="https://waldvogel.family/@marcel" class="u-url mention" rel="nofollow noopener" target="_blank">@marcel</a> <a href="https://mastodon.social/@Kensan" class="u-url mention" rel="nofollow noopener" target="_blank">@Kensan</a> <a href="https://chaos.social/@adfichter" class="u-url mention" rel="nofollow noopener" target="_blank">@adfichter</a> die einzig wirksame <a href="https://infosec.space/tags/Konsequenz" class="mention hashtag" rel="nofollow noopener" target="_blank">#Konsequenz</a> ist, sich konsequent entsprechender <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> als <a href="https://infosec.space/tags/Betriebssystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Betriebssystem</a> zu verweigern und keine <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> mit <a href="https://infosec.space/tags/Rootkits" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rootkits</a> zu nutzen!<ul><li>Die <a href="https://infosec.space/tags/Sicherheit" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sicherheit</a> sollte im Zweifelsfalle durch den <a href="https://infosec.space/tags/Maintainer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Maintainer</a> des Betriebssystems / der Distribution bereitgestellt und verifizierbar sein, und wenn jene*r keine Haftung dafür anbietet so ist diese dafür zu disqualifizieren.</li></ul>So einfach ist das!

Kevin Karhan :verified:<a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener" target="_blank">@0xabad1dea</a> which confirms my own point.<ul><li>All <a href="https://infosec.space/tags/KernelLevelDrivers" class="mention hashtag" rel="nofollow noopener" target="_blank">#KernelLevelDrivers</a> are <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a> and should not exist to begin with.</li><li>There was never a <a href="https://infosec.space/tags/LegitimateReason" class="mention hashtag" rel="nofollow noopener" target="_blank">#LegitimateReason</a> to allow said <a href="https://infosec.space/tags/Kernelhacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kernelhacks</a> to exist.</li><li>Noone should've allowed this <a href="https://infosec.space/tags/scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#scareware</a> to exist or signed it (<a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a>) nor used it and the <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> it was made for (<a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>).</li><li>I sincerely hope they'll be made to face <a href="https://infosec.space/tags/accountability" class="mention hashtag" rel="nofollow noopener" target="_blank">#accountability</a> and <a href="https://infosec.space/tags/consequences" class="mention hashtag" rel="nofollow noopener" target="_blank">#consequences</a> for this shitshow, and I mean not a <a href="https://infosec.space/tags/ClassAction" class="mention hashtag" rel="nofollow noopener" target="_blank">#ClassAction</a> aka. "<a href="https://infosec.space/tags/GetOutOfJailCheque" class="mention hashtag" rel="nofollow noopener" target="_blank">#GetOutOfJailCheque</a>" that is insultingly low.</li></ul>

Kevin Karhan :verified:<a href="https://infosec.exchange/@howelloneill" class="u-url mention" rel="nofollow noopener" target="_blank">@howelloneill</a> call <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> as a subset of <a href="https://infosec.space/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Malware</a>, just like <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> aka. "<a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Antivirus</a>" and "<a href="https://infosec.space/tags/AntiMalware" class="mention hashtag" rel="nofollow noopener" target="_blank">#AntiMalware</a>" sold by 3rd parties withoit sourcecode access to the underlying systems' components!

Kevin Karhan :verified:<a href="https://cyberplace.social/@GossiTheDog" class="u-url mention" rel="nofollow noopener" target="_blank">@GossiTheDog</a> doesn't change the fact that I think the entire <a href="https://infosec.space/tags/CottageIndustry" class="mention hashtag" rel="nofollow noopener" target="_blank">#CottageIndustry</a> of <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> like <a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Antivirus</a> & <a href="https://infosec.space/tags/AmtiMalware" class="mention hashtag" rel="nofollow noopener" target="_blank">#AmtiMalware</a> products shouldn't exist to begin with and instead <a href="https://infosec.space/tags/OS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS</a> vendors - or at least those that charge for the privilegue of using their <a href="https://infosec.space/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#Software</a> like <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> - should be obligated to keep their shit secure and maintain it.<ul><li>Unlike some nieche distro maintained by unpaid volunteers Microsoft has no problem to finance that!</li></ul>Espechally since most good <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> distros already offer that cheaper and better!

Kevin Karhan :verified:<a href="https://mastodon.social/@Mastokarl" class="u-url mention" rel="nofollow noopener" target="_blank">@Mastokarl</a> ich fragemich ehrr warum die <a href="https://infosec.space/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> vergeit und wieso <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> und <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> woe <a href="https://infosec.space/tags/CorwdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#CorwdStrike</a> nicht illegal sind in <a href="https://infosec.space/tags/KRITIS" class="mention hashtag" rel="nofollow noopener" target="_blank">#KRITIS</a>!

Kevin Karhan :verified:<a href="https://ruhr.social/@usi" class="u-url mention" rel="nofollow noopener" target="_blank">@usi</a> <a href="https://troet.cafe/@Thea_gruen" class="u-url mention" rel="nofollow noopener" target="_blank">@Thea_gruen</a> <a href="https://mastodon.social/@tazgetroete" class="u-url mention" rel="nofollow noopener" target="_blank">@tazgetroete</a> also ich sehe das genau andersherum:<ol><li><a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> und <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> wie <a href="https://infosec.space/tags/CrowdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#CrowdStrike</a> gehört ausnahmslos verboten und die Entscheider*innen bei beiden Unternehmen & Kundenunternehmen in Regress genommen!</li><li>Die Tatsache dass irgendwelche Kiddies den Perimeter des Flughafen durchbrechen und aufs Rollfeld und die Taxiways kommen konnten gehört aufgearbeitet, weil das sollte gem. <a href="https://infosec.space/tags/ICAO" class="mention hashtag" rel="nofollow noopener" target="_blank">#ICAO</a> denen selbst unter Anwendung von Waffengewalt nicht möglich sein!! Hier haben die Seccies verkackt!!!</li></ol>

Kevin Karhan :verified:<a href="https://fedi.lynnesbian.space/@lynnesbian" class="u-url mention" rel="nofollow noopener" target="_blank">@lynnesbian</a> see, that's why I'll soldier on and stick to <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMEMO</a>, <a href="https://infosec.space/tags/Mumble" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mumble</a>, <a href="https://infosec.space/tags/WebCall" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebCall</a>, <a href="https://infosec.space/tags/JitsiMeet" class="mention hashtag" rel="nofollow noopener" target="_blank">#JitsiMeet</a>, <a href="https://infosec.space/tags/VoIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoIP</a> and <a href="https://infosec.space/tags/eMail" class="mention hashtag" rel="nofollow noopener" target="_blank">#eMail</a> and avoid <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> at all costs.Cuz my time is way too precious to waste it on unpaid labour on people that are not only <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterates</a> but ignorant...In return I can just reply to shit like <a href="https://infosec.space/tags/CrowdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#CrowdStrike</a> "Lol, who uses that <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a>?" and provide evidenve that I wasn't impacted at all...

Kevin Karhan :verified:<a href="https://infosec.town/@mttaggart" class="u-url mention" rel="nofollow noopener" target="_blank">@mttaggart</a> I just don't use <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> not <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> and instead burden the load of <a href="https://infosec.space/tags/hardenibg" class="mention hashtag" rel="nofollow noopener" target="_blank">#hardenibg</a> towards the Distro Maintainer as oer Contract...

Kevin Karhan :verified:<a href="https://pfalz.social/@Saupreiss" class="u-url mention" rel="nofollow noopener" target="_blank">@Saupreiss</a> Klar, nur bietet <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> nichtmals ansatzweise die Menge an <a href="https://infosec.space/tags/Support" class="mention hashtag" rel="nofollow noopener" target="_blank">#Support</a> und <a href="https://infosec.space/tags/Assurance" class="mention hashtag" rel="nofollow noopener" target="_blank">#Assurance</a> an die <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> Distros wie <a href="https://infosec.space/tags/RHEL" class="mention hashtag" rel="nofollow noopener" target="_blank">#RHEL</a> (Workstation), <a href="https://infosec.space/tags/SLES" class="mention hashtag" rel="nofollow noopener" target="_blank">#SLES</a> / <a href="https://infosec.space/tags/SLED" class="mention hashtag" rel="nofollow noopener" target="_blank">#SLED</a>, <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener" target="_blank">#UbuntuLTS</a> und <a href="https://infosec.space/tags/OracleLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#OracleLinux</a> abmnbieten obwohl <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> und besonders <a href="https://infosec.space/tags/WindowsServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsServer</a> deutlich teurer durchzulizensieren ist.Außerdem ist das komplette "<a href="https://infosec.space/tags/Antimalware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Antimalware</a>" / "<a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Antivirus</a>" - Business doch einfach nur <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> die auf kongnitive Dissonanz abzielt weil Leute die <a href="https://infosec.space/tags/WindowsDefender" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsDefender</a> misstrauen nicht gleich die <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> namens Windows mit enstorgen!

Kevin Karhan :verified:<a href="https://toot.yosh.is/@yosh" class="u-url mention" rel="nofollow noopener" target="_blank">@yosh</a> Same with like <a href="https://infosec.space/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> fuckups like <a href="https://infosec.space/tags/CrowdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#CrowdStrike</a>.<ul><li><a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> like it amd <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> like <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> is being used because they ain't painful enough!</li></ul>

Kevin Karhan :verified:<a href="https://social.tchncs.de/@simsus" class="u-url mention" rel="nofollow noopener" target="_blank">@simsus</a> oder ein Bezriebssystem ohne jene <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> (<a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>)...

Kevin Karhan :verified:<a href="https://zug.network/@Zugschlus" class="u-url mention" rel="nofollow noopener" target="_blank">@Zugschlus</a> <a href="https://mastodon.social/@Cappyjax" class="u-url mention" rel="nofollow noopener" target="_blank">@Cappyjax</a> <a href="https://mastodon.radio/@WB2EEE" class="u-url mention" rel="nofollow noopener" target="_blank">@WB2EEE</a> <a href="https://donotsta.re/users/elly" class="u-url mention" rel="nofollow noopener" target="_blank">@elly</a> well, I'd rather not take or stay in a job than commit what I call "Professional <a href="https://infosec.space/tags/Malpractice" class="mention hashtag" rel="nofollow noopener" target="_blank">#Malpractice</a>"!<ul><li>I know this makes me an outlier, but the fact that I did my job so well that everything I deployed runs like clockwork to this day amd that I'm not short of offers tells me that being a honest <a href="https://infosec.space/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#sysadmin</a> is the way to go morally instead of being a <a href="https://infosec.space/tags/bootlicker" class="mention hashtag" rel="nofollow noopener" target="_blank">#bootlicker</a>!</li></ul>Again: We have this entire shitshow because we allow <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterates</a> and other dipshits to make up regulations on the spot.<ul><li>Also yes, there are means to harden <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> on Sesktops amd Servers beyond the already existing <a href="https://infosec.space/tags/CommonCriteria" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommonCriteria</a> and <a href="https://infosec.space/tags/CIS2" class="mention hashtag" rel="nofollow noopener" target="_blank">#CIS2</a> as well as beyond <a href="https://infosec.space/tags/PCIDSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#PCIDSS</a> compliance and good Distros will even offer a warranty and assurance for that directly - something <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> just won't do for <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> no matter the amount of money one shoves down their throat!</li></ul>The fact that we even allow that <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> and <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> [to even exist, espechally] in <a href="https://infosec.space/tags/CriticalInfrastructure" class="mention hashtag" rel="nofollow noopener" target="_blank">#CriticalInfrastructure</a> when in both cases their <a href="https://infosec.space/tags/EULA" class="mention hashtag" rel="nofollow noopener" target="_blank">#EULA</a> explicitly bans that use-case is a testiment for the false priorities of regulators and their rules.<ul><li>So yeah, if a concrete-headed <a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterate</a> wants that they can have it - but not from or with me!</li></ul>And then they all whine about why noone wants to work for them... What a shitshow. Tell you what, I'd rather <a href="https://zug.network/@Zugschlus/112822635158064785" rel="nofollow noopener" target="_blank">welcome such meetings</a>, because the last time some CEO did that (with an absurd office mandate forcing a colleague into a 500km [one-way!] commute twice a week) they basically mobbed out the two best colleagues I had and subsequently imploded the Linux Infrastructure team.<ul><li>Last time I checked that company hadn't filled the vacancies and once Recruiters hear the story, they tend to fire said company as a client.</li></ul><a href="https://infosec.space/tags/Sarcasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sarcasm</a> <a href="https://infosec.space/tags/venting" class="mention hashtag" rel="nofollow noopener" target="_blank">#venting</a> <a href="https://infosec.space/tags/CrowdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#CrowdStrike</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@Cappyjax" class="u-url mention" rel="nofollow noopener" target="_blank">@Cappyjax</a> <a href="https://mastodon.radio/@WB2EEE" class="u-url mention" rel="nofollow noopener" target="_blank">@WB2EEE</a> <a href="https://zug.network/@Zugschlus" class="u-url mention" rel="nofollow noopener" target="_blank">@Zugschlus</a> <a href="https://donotsta.re/users/elly" class="u-url mention" rel="nofollow noopener" target="_blank">@elly</a> I disagree with <a href="https://mastodon.social/@Cappyjax/112821333101353573" rel="nofollow noopener" target="_blank">your assessment</a> to some extent, as on <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> there's not much of a tolerace or even acceptance of <a href="https://infosec.space/tags/rootkits" class="mention hashtag" rel="nofollow noopener" target="_blank">#rootkits</a> like <a href="https://infosec.space/tags/CorwdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#CorwdStrike</a> for all the right reasons!<ul><li><a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scareware</a> like that has no legitimate reason to exist and the only place I've seen that is on <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> because people distrusting <a href="https://infosec.space/tags/WindowsDefender" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsDefender</a> and thus <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> are unwilling to to what is evidently the correct solution and yeet Windows for good.</li></ul>Cuz it's not about <a href="https://infosec.space/tags/Fanboyism" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fanboyism</a>, but a fact that most Windows - <a href="https://infosec.space/tags/Sysadmins" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sysadmins</a> (or rather decisionmakers for that matter) seem to be high on <a href="https://infosec.space/tags/Copium" class="mention hashtag" rel="nofollow noopener" target="_blank">#Copium</a> and refuse to take actual <a href="https://infosec.space/tags/consequences" class="mention hashtag" rel="nofollow noopener" target="_blank">#consequences</a> but accept the <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enshittification</a> as a fact of life when it's not...<ul><li>Or am I the only one who remembers the rightful backclash when <a href="https://infosec.space/tags/ads" class="mention hashtag" rel="nofollow noopener" target="_blank">#ads</a> were shoved into <a href="https://infosec.space/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ubuntu</a> whilst on <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows11</a> and <a href="https://infosec.space/tags/Windows10" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows10</a> people just seem to shrug their shoulders?</li></ul>It's just that this entire shitshow would not have happened on <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> because here we don't have an entire ecosystem of <a href="https://infosec.space/tags/ValueRemoving" class="mention hashtag" rel="nofollow noopener" target="_blank">#ValueRemoving</a> "<a href="https://infosec.space/tags/AntiVirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#AntiVirus</a>" bs being shoved on Desktops and Servers in the form of <a href="https://infosec.space/tags/Binaryblob" class="mention hashtag" rel="nofollow noopener" target="_blank">#Binaryblob</a> <a href="https://infosec.space/tags/Kernelhacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kernelhacks</a>!

Recent searches

Search options

Administered by:

Server stats:

#scareware