Changeset View
Changeset View
Standalone View
Standalone View
website/content/en/releases/12.4R/relnotes.adoc
| Show First 20 Lines • Show All 378 Lines • ▼ Show 20 Lines | |||||
| === General Network | === General Network | ||||
| The man:dummynet[4] system facility had an out-of-bounds bug fixed as well as a bug regarding the validation of the length of socket options. | The man:dummynet[4] system facility had an out-of-bounds bug fixed as well as a bug regarding the validation of the length of socket options. | ||||
| The man:ipfilter[4] packet filter added the `SDT` and `DT5` man:dtrace[1] probes. It now has the ability to dump a copy of ippool in ippool.conf format. | The man:ipfilter[4] packet filter added the `SDT` and `DT5` man:dtrace[1] probes. It now has the ability to dump a copy of ippool in ippool.conf format. | ||||
| From now on, to improve security, man:ipfilter[4] only allows jails to manipulate ipfilter rules, NAT tables, and ippools if the jail has its own VNET. A number of other improvements have been implemented. | From now on, to improve security, man:ipfilter[4] only allows jails to manipulate ipfilter rules, NAT tables, and ippools if the jail has its own VNET. A number of other improvements have been implemented. | ||||
| The man:netmap[4] framework had a fix for a TOCTOU vulnerability as well as a bug regarding an integer overflow. | The man:netmap[4] framework had a fix for a TOCTOU vulnerability as well as a bug regarding an integer overflow. | ||||
| //// | |||||
| [[future-releases]] | [[future-releases]] | ||||
| == General Notes Regarding Future FreeBSD Releases | == General Notes Regarding Future FreeBSD Releases | ||||
| [[future-releases-cputype]] | [[future-releases-cputype]] | ||||
| === Default `CPUTYPE` Change | === Default `CPUTYPE` Change | ||||
| Starting with FreeBSD-13.0, the default `CPUTYPE` for the i386 architecture will change from `486` to `686`. | Starting with FreeBSD-13.0, the default `CPUTYPE` for the i386 architecture will change from `486` to `686`. | ||||
| This means that, by default, binaries produced will require a 686-class CPU, including but not limited to binaries provided by the FreeBSD Release Engineering team. FreeBSD 13.0 will continue to support older CPUs, however users needing this functionality will need to build their own releases for official support. | This means that, by default, binaries produced will require a 686-class CPU, including but not limited to binaries provided by the FreeBSD Release Engineering team. FreeBSD 13.0 will continue to support older CPUs, however users needing this functionality will need to build their own releases for official support. | ||||
| As the primary use for i486 and i586 CPUs is generally in the embedded market, the general end-user impact is expected to be minimal, as new hardware with these CPU types has long faded, and much of the deployed base of such systems is nearing retirement age, statistically. | As the primary use for i486 and i586 CPUs is generally in the embedded market, the general end-user impact is expected to be minimal, as new hardware with these CPU types has long faded, and much of the deployed base of such systems is nearing retirement age, statistically. | ||||
| There were several factors taken into account for this change. For example, i486 does not have 64-bit atomics, and while they can be emulated in the kernel, they cannot be emulated in the userland. Additionally, the 32-bit amd64 libraries have been i686 since their inception. | There were several factors taken into account for this change. For example, i486 does not have 64-bit atomics, and while they can be emulated in the kernel, they cannot be emulated in the userland. Additionally, the 32-bit amd64 libraries have been i686 since their inception. | ||||
| As the majority of 32-bit testing is done by developers using the lib32 libraries on 64-bit hardware with the `COMPAT_FREEBSD32` option in the kernel, this change ensures better coverage and user experience. This also aligns with what the majority of Linux(R) distributions have been doing for quite some time. | As the majority of 32-bit testing is done by developers using the lib32 libraries on 64-bit hardware with the `COMPAT_FREEBSD32` option in the kernel, this change ensures better coverage and user experience. This also aligns with what the majority of Linux(R) distributions have been doing for quite some time. | ||||
| This is expected to be the final bump of the default `CPUTYPE` in i386. | This is expected to be the final bump of the default `CPUTYPE` in i386. | ||||
| [IMPORTANT] | [IMPORTANT] | ||||
| ==== | ==== | ||||
| This change does not affect the FreeBSD 12.x series of releases. | This change does not affect the FreeBSD 12.x series of releases. | ||||
| ==== | ==== | ||||
| //// | |||||