Date: Mon, 12 Dec 2022 14:53:48 -0500 From: Ed Maste <emaste@freebsd.org> To: mike tancsa <mike@sentex.net> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-22:15.ping Message-ID: <CAPyFy2CFdZ0rFM6hMRLqEFbSzypoiCYS1TO4HaXQN1h%2Bo03i%2BQ@mail.gmail.com> In-Reply-To: <4ce47f73-c48f-22f6-e0c0-0bd03452bcda@sentex.net> References: <20221130004601.043CE1C623@freefall.freebsd.org> <3dc86282-165d-8562-5cba-0da9896557b9@sentex.net> <e9a7b2ca-a4a4-5b99-f915-0db46b60d1e8@apt322.org> <2b590fd0-8b02-1344-d501-005c6cd9fb8f@sentex.net> <20221130223855.GA89753@spindle.one-eyed-alien.net> <4ce47f73-c48f-22f6-e0c0-0bd03452bcda@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 1 Dec 2022 at 10:28, mike tancsa <mike@sentex.net> wrote: > > My concern is the "evil server in the middle" ... Things like route > highjacking are not that uncommon. I have a number of IoT devices out > there I will need to patch, some still based on RELENG_11. The bug was introduced after releng/11, so those ones won't be affected.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2CFdZ0rFM6hMRLqEFbSzypoiCYS1TO4HaXQN1h%2Bo03i%2BQ>