Actually, I'm testing this on a 13.0-RC3 host and am not getting the p1. This
is likely due to the freebsd-update build scripts not properly messing with the
newvers.sh. I'll investigate. Thanks for the report!
Gordon
> On Mar 26, 2021, at 3:50 PM, Tatsuki Makino
> wrote:
>
> This is a fix t
This is a fix that does not require replacing the kernel, so freebsd-update
does not change the kernel.
I think the Doctor rebuilt the kernel himself/herself, so there is a -p1.
This is a frequent occurrence :)
___
freebsd-security@freebsd.org mailing
On Fri, Mar 26, 2021 at 09:13:57PM +0900, Masachika ISHIZUKA wrote:
> > FreeBSD-SA-21:07.openssl
> >
> [snip]
> >
> > # freebsd-update fetch
> > # freebsd-update install
>
> I did above on 13.0-RC3 and rebooted.
> But 'motd', 'uname -a', 'freebsd-version -uk' shows 13.0-RC3,
> not 13.0-RC3-
On Fri, Mar 26, 2021 at 12:05:23AM +, FreeBSD Security Advisories wrote:
> A TLSv1.2 renegotiation ClientHello message sent to a TLS server that omits
> the signature_algorithms extension (where it was present in the initial
> ClientHello), but includes a signature_algorithms_cert extension res
> FreeBSD-SA-21:07.openssl
>
[snip]
>
> # freebsd-update fetch
> # freebsd-update install
I did above on 13.0-RC3 and rebooted.
But 'motd', 'uname -a', 'freebsd-version -uk' shows 13.0-RC3,
not 13.0-RC3-p1.
--
Masachika ISHIZUKA
___
freebsd-secur
