Date: Sun, 19 Feb 2023 01:09:31 +0000 From: void <void@f-m.fm> To: freebsd-arm@freebsd.org Subject: Re: freebsd-update confusion Message-ID: <Y/F2yyAi4ddgHZfp@int21h> In-Reply-To: <FF4E1AA5-ADC9-4478-A56B-297884D731FC@yahoo.com> References: <Y/FI9NAuioJVU0WB@int21h> <Y/FNJkXgYgXwWTMy@mail.bsd4all.net> <Y/FZ7A1Uzd4y602A@int21h> <FF4E1AA5-ADC9-4478-A56B-297884D731FC@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 18, 2023 at 04:04:20PM -0800, Mark Millard wrote: >Same point for 13.1-RELEASE-p7 here: >OpenSSL 1.1.1o was patched to remove the problems. That does >not produce 1.1.1t as a result. ok - so I'm understanding from what you're saying is that (in this case) 13.1R is following openssl 1.1.1o branch ok I wasn't aware it was tied in this way. >The output of the openssl command likely is just as upstream >has defined it, it not being directly a FreeBSD thing. The >patches to the openssl source were likely also from upstream. I still find it counterintuitive though that after being patched, openssl version still returns 3 May 2022 and not the patch date. --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Y/F2yyAi4ddgHZfp>