Message-ID: <669ca686@news.ausics.net> From: Computer Nerd Kev Subject: Re: Wonderful Windows Zaps Banks/Transport/Media after "Update" Yesterday Newsgroups: comp.os.linux.misc References: <-7CcndX6lpSstAb7nZ2dnZfqnPudnZ2d@earthlink.com> <669c53b2@news.ausics.net> User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (Linux/2.4.31 (i686)) NNTP-Posting-Host: news.ausics.net Date: 21 Jul 2024 16:11:19 +1000 Organization: Ausics - https://newsgroups.ausics.net Lines: 20 X-Complaints: abuse@ausics.net Path: csiph.com!news.bbs.nz!news.ausics.net!not-for-mail Xref: csiph.com comp.os.linux.misc:57091 Lawrence D'Oliveiro wrote: > On 21 Jul 2024 10:17:55 +1000, Computer Nerd Kev wrote: >> That was very interesting. Although following the link to the article >> about the whistleblower who quit Microsoft, guess who hired them next? > > What is that supposed to be suggesting, exactly? Is it saying something > about the ethics of the whistleblower, or of the company who hired them? > If so, what? As is so often the case replying to you, I meant what I said in the bit of my text that you snipped. The fact the whistleblower took up a job at CrowdStrike after quitting M$ due to their management culture suggested that CrowdStrike would be more responsible. But the way this bug slipped out on such a wide scale contradicts that now. I'm meerly commenting that the business of trying to protect Windows systems from attack seems to be dodgy wherever you turn. -- __ __ #_ < |\| |< _#