aboutsummaryrefslogtreecommitdiff
path: root/website/content/en/security/_index.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'website/content/en/security/_index.adoc')
-rw-r--r--website/content/en/security/_index.adoc27
1 files changed, 17 insertions, 10 deletions
diff --git a/website/content/en/security/_index.adoc b/website/content/en/security/_index.adoc
index 3fa19716e9..ee5c2debb1 100644
--- a/website/content/en/security/_index.adoc
+++ b/website/content/en/security/_index.adoc
@@ -3,6 +3,7 @@ title: "FreeBSD Security Information"
sidenav: support
---
+include::shared/en/urls.adoc[]
include::shared/releases.adoc[]
= FreeBSD Security Information
@@ -50,6 +51,8 @@ Once it had been determined that a Security Advisory is warranted, either the su
A full list of all security vulnerabilities affecting the base system can be found link:advisories[on this page].
+A full list of all other errata affecting the base system can be found link:notices[on this page].
+
[[advisories]]
== Understanding FreeBSD security advisories
@@ -61,19 +64,21 @@ Advisories affecting the base system are sent to the following mailing lists:
The list of released advisories can be found on the link:advisories[FreeBSD Security Advisories] page.
-Advisories are always signed using the FreeBSD Security Officer link:so_public_key.asc[PGP key] and are archived, along with their associated patches, at the http://security.FreeBSD.org/ web server in the http://security.FreeBSD.org/advisories/[advisories] and http://security.FreeBSD.org/patches/[patches] subdirectories.
+Advisories are always signed using the FreeBSD Security Officer link:so_public_key.asc[PGP key] and are archived, along with their associated patches, at the https://security.FreeBSD.org web server in the https://security.FreeBSD.org/advisories/[advisories] and https://security.FreeBSD.org/patches/[patches] subdirectories.
The FreeBSD Security Officer provides security advisories for _-STABLE Branches_ and the _Security Branches_. (Advisories are not issued for the _-CURRENT Branch_, which is primarily oriented towards FreeBSD developers.)
-* The -STABLE branch tags have names like `stable/13`. The corresponding builds have names like `FreeBSD 13.0-STABLE`.
-* Each FreeBSD Release has an associated Security Branch. The Security Branch tags have names like `releng/13.0`. The corresponding builds have names like `FreeBSD 13.0-RELEASE-p1`.
+* The -STABLE branch tags have names like `stable/13`. The corresponding builds have names like `FreeBSD 13.2-STABLE`.
+* Each FreeBSD Release has an associated Security Branch. The Security Branch tags have names like `releng/13.2`. The corresponding builds have names like `FreeBSD 13.2-RELEASE-p1`.
+
+Issues affecting the FreeBSD Ports Collection are covered separately in https://vuxml.FreeBSD.org/[the FreeBSD VuXML document].
-Issues affecting the FreeBSD Ports Collection are covered separately in http://vuxml.FreeBSD.org/[the FreeBSD VuXML document].
+Errata affecting the base system but not classified as security vulnerabilities are covered separately on the link:notices[FreeBSD Errata Notices] page.
[[how]]
== How to update your system
-For users that have previously installed a binary version of FreeBSD (e.g., {rel130-current} or {rel122-current}), commands:
+For users that have previously installed a binary version of FreeBSD (e.g., {rel131-current} or {rel123-current}), commands:
`# freebsd-update fetch`
@@ -83,6 +88,8 @@ If that fails, follow the other instructions in the security advisory you care a
Note that the above procedure is only for users who have previously installed a binary distribution. Those who have built from source will need to update their source tree to upgrade.
+For more details, read link:{handbook}cutting-edge/#freebsdupdate-security-patches[how to apply security patches].
+
[[sup]]
== Supported FreeBSD releases
@@ -96,11 +103,11 @@ link:unsupported[Older releases] are not supported and users are strongly encour
[cols=",,,",options="header",]
|===
|Branch |Release |Release Date |Expected EoL
-|stable/13 |n/a |n/a |January 31, 2026
-|releng/13.0 |13.0-RELEASE |April 13, 2021 |13.1-RELEASE + 3 months
-|stable/12 |n/a |n/a |June 30, 2024
-|releng/12.3 |12.3-RELEASE |December 7, 2021 |12.4-RELEASE + 3 months
-|releng/12.2 |12.2-RELEASE |October 27, 2020 |March 31, 2022
+|stable/14 |n/a |n/a |November 30, 2028
+|releng/14.0 |14.0-RELEASE |November 20, 2023 |14.1-RELEASE + 3 months
+|stable/13 |n/a |n/a |April 30, 2026
+|releng/13.3 |13.3-RELEASE |March 5, 2024 |13.4-RELEASE + 3 months
+|releng/13.2 |13.2-RELEASE |April 11, 2023 |June 30, 2024
|===
In the run-up to a release, a number of -BETA and -RC releases may be published for testing purposes. These releases are only supported for a few weeks, as resources permit, and will not be listed as supported on this page. Users are strongly discouraged from running these releases on production systems.