freebsd security - Dec 2017 - FreeBSD 11.0 end-of-life

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear FreeBSD community,

As of Nov 30, 2017, FreeBSD 11.0 has reached end-of-life and is no
longer supported by the FreeBSD Security Team.  Users of FreeBSD 11.0
are strongly encouraged to upgrade to a newer release as soon as
possible.

The currently supported branches and releases and their expected
end-of-life dates are:

 +--------------------------------------------------------------------------+
 |   Branch  |   Release  |  Type  |   Release Date |     Estimated EoL     |
 +-----------+------------+--------+----------------+-----------------------+
 |stable/10  |n/a         |n/a     |n/a             |October 31, 2018       |
 +-----------+------------+--------+----------------+-----------------------+
 |releng/10.3|10.3-RELEASE|Extended|April 4, 2016   |April 30, 2018         |
 +--------------------------------------------------------------------------+
 |releng/10.4|10.4-RELEASE|Normal  |October 3, 2017 |October 31, 2018       |
 +--------------------------------------------------------------------------+
 |stable/11  |n/a         |n/a     |n/a             |September 30, 2021     |
 +-----------+------------+--------+----------------+-----------------------+
 |releng/11.0|11.0-RELEASE|n/a     |October 10, 2016|November 30, 2017      |
 +--------------------------------------------------+-----------------------+
 |releng/11.1|11.1-RELEASE|n/a     |July 26, 2017   |11.2-RELEASE + 3 months|
 +--------------------------------------------------+-----------------------+

As a reminder, FreeBSD changed the support model as of 11.0-RELEASE.
For additional information, please see
https://lists.freebsd.org/pipermail/freebsd-announce/2015-February/001624.html

Please refer to https://security.freebsd.org/ for an up-to-date list of
supported releases and the latest security advisories.

- --
The FreeBSD Security Team
-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEHPf/b631yp++G4yy7Wfs1l3PaucFAloq5GZfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDFD
RjdGRjZGQURGNUNBOUZCRTFCOENCMkVENjdFQ0Q2NURDRjZBRTcACgkQ7Wfs1l3P
audOpA//YYr4etu0hGpQ+heBiOzF3H2artMNtoGAqwC1OGzbn48OP6+gh0FuVYlQ
oAReMVqisNvPAwXA38UoebRz22b2xJcN1es8Ykmwj6UPJeW8fTQ6dU2fsLd10+9+
vBwP/+LUeoh1kPEOh7IDhLo5W1CEfwlznA5FkrDuLMzI4K6/1u3KJdfUHHUIKsFZ
z7dOOQcIgXIUfOqcx5l49rn3eVy0y9hnFd0etG/+ndXpinoYeW9cvK11kUgsbs6W
2mAV3wcMeGs+XeQumVFvWF8U9Yrygbi4d+UPJeLOICTHLtn1jBDzESbzdle/dIn8
6CFp9ytBKqEVfMY2jWYFDuQuoVFcvJpSREBzQAPqi/0+ztNX5tpMb4X0MQzT2Vyj
C5b9YKQ3WLpvvDpJ49WgasufoX8sJxE5Q8HDdLhL66YXcAAsqhinyEcWwhbwXn4Q
kj0eihnHleUJENetfkxRir+XUV0sekxmFEH2CixWdXd1YBh6s9E48x7+4K94sSfp
Mv+68PFgUm0e7Hb70+uNDMPHrezvPhw0ntTaOqLtAIeNjA/PHoul9lnEC1u2mXwE
wfBfXjVmyHT9AiTUKdQMltzrugR+8rMfJpLf903vfRHboihUYD6HYdMsPG2IHuKt
SY6YGLOE/cR9WfY/hOa6XwakM2NF/DH2zVpLqMB0v9XZ/OCuUAQ=UT3M
-----END PGP SIGNATURE-----

Hi,
> On 8. Dec 2017, at 8:25 PM, FreeBSD Security Officer <security-officer
at freebsd.org> wrote:
> 
>
+--------------------------------------------------+-----------------------+
> |releng/11.1|11.1-RELEASE|n/a     |July 26, 2017   |11.2-RELEASE + 3
months|
>
+--------------------------------------------------+-----------------------+
Is there *any* indication when X + 3 is going to be?  Because as a downstream
vendor X + 3 months usually translates to X, because there is no time to prepare
for any of this, especially when swift adoption is enforced by upstream, e.g.
by deprecated packages, quarterly branch and locking users out of the ports
tree.

To that end, https://www.freebsd.org/releng/index.html states:
> Upcoming Release Schedule
> NOTE: Release dates are approximate and may be subject to schedule
slippage.
> As of 2017-10-03, the next release has not yet been announced.

Thank you,
Franco