Date: Mon, 20 Jun 2022 02:51:00 +0000 From: "Chen, Alvin W" <Weike.Chen@Dell.com> To: "Ronald F. Guilmette" <rfg@tristatelogic.com>, "freebsd-security@freebsd.org" <freebsd-security@freebsd.org> Subject: RE: Intel CPU CVE Issue: CVE-2022-21166/CVE-2022-21125/CVE-2022-21123 Message-ID: <PH0PR19MB4938B21235745345178FB4E89EB09@PH0PR19MB4938.namprd19.prod.outlook.com> In-Reply-To: <41717.1655451216@segfault.tristatelogic.com> References: <90e55cbc-a0f7-7220-3759-e05dee2daaf9@inbox.lv> <41717.1655451216@segfault.tristatelogic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>=20 > [EXTERNAL EMAIL] >=20 > In message <90e55cbc-a0f7-7220-3759-e05dee2daaf9@inbox.lv>, > John Long <codeblue@inbox.lv> wrote: >=20 > >1st of all, my comment was because of your post but was not directed at > >you. Sorry if that was unclear. > > > >2nd of all, great that they give advice. Not so great that people have > >to actually do the work. This costs everybody *besides Intel* a lot of > >money and there is no end in sight. > > > >How about if Intel gives refunds to people afflicted by their defective > >products and pays remediation costs to software projects similarly > >afflicted? Maybe that would give them incentive to do a better job with > >the junk they're selling. >=20 >=20 > There's neither any need nor any point to being rude to the guy. He just > asked a couple of simple simple questions. It's not his job to issue ref= unds > for Intel's broken & insecure processors. (He doesn't even work for Inte= l.) >=20 >=20 > Regards, > rfg Hope FreeBSD mail list is only for technical discussion with no individual = emotion. Internal Use - Confidential
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi? <PH0PR19MB4938B21235745345178FB4E89EB09>