|
Lines 21-26
Link Here
|
| 21 |
possible. This page will provide information about what to do in |
21 |
possible. This page will provide information about what to do in |
| 22 |
the event of a security vulnerability affecting your system</p> |
22 |
the event of a security vulnerability affecting your system</p> |
| 23 |
|
23 |
|
|
|
24 |
<h2>Table of Contents</h2> |
| 25 |
|
| 26 |
<ul> |
| 27 |
<li><a href="#reporting">Reporting FreeBSD security incidents</a></li> |
| 28 |
<li><a href="#recent">Recent FreeBSD security vulnerabilities</a></li> |
| 29 |
<li><a href="#advisories">Understanding FreeBSD security advisories</a></li> |
| 30 |
<li><a href="#how">How to update your system</a></li> |
| 31 |
<li><a href="#sup">Supported FreeBSD releases</a></li> |
| 32 |
<li><a href="#model">The FreeBSD support model</a></li> |
| 33 |
</ul> |
| 34 |
|
| 35 |
<a name="reporting"></a> |
| 24 |
<h2>Reporting FreeBSD security incidents</h2> |
36 |
<h2>Reporting FreeBSD security incidents</h2> |
| 25 |
|
37 |
|
| 26 |
<p>FreeBSD security issues specific to the operating system |
38 |
<p>FreeBSD security issues specific to the operating system |
|
Lines 36-54
Link Here
|
| 36 |
href="reporting.html">reporting FreeBSD security incidents</a> |
48 |
href="reporting.html">reporting FreeBSD security incidents</a> |
| 37 |
page.</p> |
49 |
page.</p> |
| 38 |
|
50 |
|
| 39 |
<h2>Table of Contents</h2> |
51 |
<a name="recent"></a> |
|
|
52 |
<h2>Recent FreeBSD security vulnerabilities</h2> |
| 40 |
|
53 |
|
|
|
54 |
<p>A full list of all security vulnerabilities affecting the base system |
| 55 |
can be found <a |
| 56 |
href="advisories.html">on this page</a>.</p> |
| 57 |
|
| 58 |
<a name="advisories"></a> |
| 59 |
<h2>Understanding FreeBSD security advisories</h2> |
| 60 |
|
| 61 |
<p>Advisories affecting the base system are sent to the following mailing lists:</p> |
| 41 |
<ul> |
62 |
<ul> |
| 42 |
<li><a href="#recent">Recent FreeBSD security vulnerabilities</a></li> |
63 |
<li>FreeBSD-security-notifications@FreeBSD.org</li> |
| 43 |
<li><a href="#how">How to update your system</a></li> |
64 |
<li>FreeBSD-security@FreeBSD.org</li> |
|
|
65 |
<li>FreeBSD-announce@FreeBSD.org</li> |
| 44 |
</ul> |
66 |
</ul> |
| 45 |
|
67 |
|
| 46 |
<a name="recent"></a> |
68 |
<p>The list of released advisories can be found on the <a |
| 47 |
<h2>Recent FreeBSD security vulnerabilities</h2> |
69 |
href="advisories.html">FreeBSD Security Advisories</a> page.</p> |
| 48 |
|
70 |
|
| 49 |
<p>A full list of all security vulnerabilities can be found <a |
71 |
<p>Advisories are always signed using the FreeBSD Security Officer |
| 50 |
href="advisories.html">on this page</a>.</p> |
72 |
<a href="so_public_key.asc">PGP |
|
|
73 |
key</a> and are archived, along with their associated patches, at |
| 74 |
the <a href="http://security.FreeBSD.org/">http://security.FreeBSD.org/</a> |
| 75 |
web server in the <a |
| 76 |
href="http://security.FreeBSD.org/advisories/">advisories</a> and <a |
| 77 |
href="http://security.FreeBSD.org/patches/">patches</a> |
| 78 |
subdirectories.</p> |
| 51 |
|
79 |
|
|
|
80 |
<p>The FreeBSD Security Officer provides security advisories for |
| 81 |
<em>-STABLE Branches</em> and the <em>Security Branches</em>. |
| 82 |
(Advisories are not issued for the <em>-CURRENT Branch</em>, |
| 83 |
which is primarily oriented towards &os; developers.)</p> |
| 84 |
|
| 85 |
<ul> |
| 86 |
<li><p>The -STABLE branch tags have |
| 87 |
names like <tt>stable/10</tt>. The corresponding builds have |
| 88 |
names like <tt>FreeBSD 10.1-STABLE</tt>.</p></li> |
| 89 |
|
| 90 |
<li><p>Each FreeBSD Release has an associated Security Branch. |
| 91 |
The Security Branch tags have names like <tt>releng/10.1</tt>. |
| 92 |
The corresponding builds have names like <tt>FreeBSD |
| 93 |
10.1-RELEASE-p4</tt>.</p></li> |
| 94 |
</ul> |
| 95 |
|
| 96 |
<p>Issues affecting the FreeBSD Ports Collection are covered separately in <a |
| 97 |
href="http://vuxml.FreeBSD.org/">the FreeBSD VuXML |
| 98 |
document</a>.</p> |
| 99 |
|
| 52 |
<a name="how"></a> |
100 |
<a name="how"></a> |
| 53 |
<h2>How to update your system</h2> |
101 |
<h2>How to update your system</h2> |
| 54 |
|
102 |
|
|
Lines 65-70
Link Here
|
| 65 |
<a name="sup"></a> |
113 |
<a name="sup"></a> |
| 66 |
<h2>Supported FreeBSD releases</h2> |
114 |
<h2>Supported FreeBSD releases</h2> |
| 67 |
|
115 |
|
|
|
116 |
<p>Each release is supported by the Security Officer for a limited |
| 117 |
time only.</p> |
| 118 |
|
| 68 |
<p>The designation and expected lifetime of all currently supported |
119 |
<p>The designation and expected lifetime of all currently supported |
| 69 |
branches are given below. The <em>Expected EoL (end-of-life)</em> |
120 |
branches are given below. The <em>Expected EoL (end-of-life)</em> |
| 70 |
column indicates the earliest date on which support for that |
121 |
column indicates the earliest date on which support for that |
|
Lines 71-90
Link Here
|
| 71 |
branch or release will end. Please note that these dates may be |
122 |
branch or release will end. Please note that these dates may be |
| 72 |
pushed back if circumstances warrant it.</p> |
123 |
pushed back if circumstances warrant it.</p> |
| 73 |
|
124 |
|
| 74 |
<p>Effective &os; 11.0-RELEASE, the support model has been |
125 |
<p>Older releases are not maintained and users are strongly |
| 75 |
changed to allow more rapid development while also providing |
126 |
encouraged to upgrade to one of the supported releases mentioned |
| 76 |
timely security updates for all supported releases.</p> |
127 |
above. A list of unsupported releases can be found <a |
|
|
128 |
href="unsupported.html">here</a>.</p> |
| 77 |
|
129 |
|
| 78 |
<p>Under the new support model, each major version's stable branch |
|
|
| 79 |
is explicitly supported for 5 years, while each individual point |
| 80 |
release is only supported for three months after the next point |
| 81 |
release.</p> |
| 82 |
|
| 83 |
<p>The details and rationale behind this change can be found in the |
| 84 |
<a |
| 85 |
href="https://lists.freebsd.org/pipermail/freebsd-announce/2015-February/001624.html">official |
| 86 |
announcement</a> sent in February 2015.</p> |
| 87 |
|
| 88 |
<!-- |
130 |
<!-- |
| 89 |
Please also update head/en_US.ISO8859-1/htdocs/releng/index.xml |
131 |
Please also update head/en_US.ISO8859-1/htdocs/releng/index.xml |
| 90 |
when updating this list of supported branches. |
132 |
when updating this list of supported branches. |
|
Lines 141-197
Link Here
|
| 141 |
</tr> |
183 |
</tr> |
| 142 |
</table> |
184 |
</table> |
| 143 |
|
185 |
|
| 144 |
<p>Older releases are not maintained and users are strongly |
186 |
<p>In the run-up to a release, a number of -BETA |
| 145 |
encouraged to upgrade to one of the supported releases mentioned |
187 |
and -RC releases may be published for testing purposes. These releases are only |
| 146 |
above. A list of unsupported releases can be found <a |
188 |
supported for a few weeks, as resources permit, and will not be |
| 147 |
href="unsupported.html">here</a>.</p> |
189 |
listed as supported on this page. Users are strongly discouraged |
|
|
190 |
from running these releases on production systems.</p> |
| 148 |
|
191 |
|
| 149 |
<p>Advisories are sent to the following FreeBSD mailing lists:</p> |
192 |
<a name="model"></a> |
| 150 |
<ul> |
193 |
<h2>The FreeBSD support model</h2> |
| 151 |
<li>FreeBSD-security-notifications@FreeBSD.org</li> |
|
|
| 152 |
<li>FreeBSD-security@FreeBSD.org</li> |
| 153 |
<li>FreeBSD-announce@FreeBSD.org</li> |
| 154 |
</ul> |
| 155 |
|
194 |
|
| 156 |
<p>The list of released advisories can be found on the <a |
195 |
<p>Effective &os; 11.0-RELEASE, the support model has been |
| 157 |
href="advisories.html">FreeBSD Security Advisories</a> page.</p> |
196 |
changed to allow more rapid development while also providing |
|
|
197 |
timely security updates for all supported releases.</p> |
| 158 |
|
198 |
|
| 159 |
<p>Advisories are always signed using the FreeBSD Security Officer |
199 |
<p>Under the new support model, each major version's stable branch |
| 160 |
<a href="so_public_key.asc">PGP |
200 |
is explicitly supported for 5 years, while each individual point |
| 161 |
key</a> and are archived, along with their associated patches, at |
201 |
release is only supported for three months after the next point |
| 162 |
the <a href="http://security.FreeBSD.org/">http://security.FreeBSD.org/</a> |
202 |
release.</p> |
| 163 |
web server in the <a |
|
|
| 164 |
href="http://security.FreeBSD.org/advisories/">advisories</a> and <a |
| 165 |
href="http://security.FreeBSD.org/patches/">patches</a> |
| 166 |
subdirectories.</p> |
| 167 |
|
203 |
|
| 168 |
<p>The FreeBSD Security Officer provides security advisories for |
204 |
<p>The details and rationale behind this change can be found in the |
| 169 |
<em>-STABLE Branches</em> and the <em>Security Branches</em>. |
205 |
<a |
| 170 |
(Advisories are not issued for the <em>-CURRENT Branch</em>.)</p> |
206 |
href="https://lists.freebsd.org/pipermail/freebsd-announce/2015-February/001624.html">official |
|
|
207 |
announcement</a> sent in February 2015.</p> |
| 171 |
|
208 |
|
| 172 |
<ul> |
209 |
<p>Previously, branches were designated as either <em>Normal</em> or |
| 173 |
<li><p>The -STABLE branch tags have |
210 |
<em>Extended</em>. The designation was used as a guideline for |
| 174 |
names like <tt>stable/10</tt>. The corresponding builds have |
|
|
| 175 |
names like <tt>FreeBSD 10.1-STABLE</tt>.</p></li> |
| 176 |
|
| 177 |
<li><p>Each FreeBSD Release has an associated Security Branch. |
| 178 |
The Security Branch tags have names like <tt>releng/10.1</tt>. |
| 179 |
The corresponding builds have names like <tt>FreeBSD |
| 180 |
10.1-RELEASE-p4</tt>.</p></li> |
| 181 |
</ul> |
| 182 |
|
| 183 |
<p>Issues affecting the FreeBSD Ports Collection are covered in <a |
| 184 |
href="http://vuxml.FreeBSD.org/">the FreeBSD VuXML |
| 185 |
document</a>.</p> |
| 186 |
|
| 187 |
<p>Each branch is supported by the Security Officer for a limited |
| 188 |
time only, and is designated as either <em>Normal</em> or |
| 189 |
<em>Extended</em>. The designation is used as a guideline for |
| 190 |
determining the lifetime of the branch as follows:</p> |
211 |
determining the lifetime of the branch as follows:</p> |
| 191 |
|
212 |
|
| 192 |
<dl> |
213 |
<dl> |
| 193 |
<dt>Normal</dt> |
214 |
<dt>Normal</dt> |
| 194 |
<dd>Releases which are published from a -STABLE branch will be |
215 |
<dd>Releases which are published from a -STABLE branch were |
| 195 |
supported by the Security Officer for a minimum of 12 months after the |
216 |
supported by the Security Officer for a minimum of 12 months after the |
| 196 |
release, and for sufficient additional time (if needed) to ensure |
217 |
release, and for sufficient additional time (if needed) to ensure |
| 197 |
that there is a newer release for at least 3 months before the |
218 |
that there is a newer release for at least 3 months before the |
|
Lines 199-205
Link Here
|
| 199 |
</dd> |
220 |
</dd> |
| 200 |
<dt>Extended</dt> |
221 |
<dt>Extended</dt> |
| 201 |
<dd>Selected releases (normally every second release plus the last |
222 |
<dd>Selected releases (normally every second release plus the last |
| 202 |
release from each -STABLE branch) will be supported by the |
223 |
release from each -STABLE branch) were supported by the |
| 203 |
Security Officer for a minimum of 24 months after the release, |
224 |
Security Officer for a minimum of 24 months after the release, |
| 204 |
and for sufficient additional time (if needed) to ensure that |
225 |
and for sufficient additional time (if needed) to ensure that |
| 205 |
there is a newer Extended release for at least 3 months before the |
226 |
there is a newer Extended release for at least 3 months before the |
|
Lines 206-216
Link Here
|
| 206 |
older Extended release expires. |
227 |
older Extended release expires. |
| 207 |
</dd> |
228 |
</dd> |
| 208 |
</dl> |
229 |
</dl> |
| 209 |
|
|
|
| 210 |
<p>In the run-up to a Normal or Extended release, a number of -BETA |
| 211 |
and -RC releases may be published. These releases are only |
| 212 |
supported for a few weeks, as resources permit, and will not be |
| 213 |
listed as supported on this page. Users are strongly discouraged |
| 214 |
from running these releases on production systems.</p> |
| 215 |
</body> |
230 |
</body> |
| 216 |
</html> |
231 |
</html> |