FreeBSD 10.0-RELEASE Errata

- The FreeBSD Project -

FreeBSD is a registered trademark of +FreeBSD 10.0-RELEASE Errata

FreeBSD 10.0-RELEASE Errata

The FreeBSD Project

FreeBSD is a registered trademark of the FreeBSD Foundation.

Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United @@ -15,15 +13,15 @@ and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the “™” or the “®” symbol.

Last modified on 2014-01-15 by hrs.

Abstract

This document lists errata items for FreeBSD 10.0-RELEASE, - containing significant information discovered after the release - or too late in the release cycle to be otherwise included in the - release documentation. - This information includes security advisories, as well as news - relating to the software or documentation that could affect its - operation or usability. An up-to-date version of this document - should always be consulted before installing this version of - FreeBSD.

This errata document for FreeBSD 10.0-RELEASE - will be maintained until the release of FreeBSD 10.1-RELEASE.

Table of Contents

1. Introduction
2. Security Advisories
3. Open Issues
4. Late-Breaking News

1. Introduction

This errata document contains “late-breaking news” + containing significant information discovered after the release + or too late in the release cycle to be otherwise included in the + release documentation. + This information includes security advisories, as well as news + relating to the software or documentation that could affect its + operation or usability. An up-to-date version of this document + should always be consulted before installing this version of + FreeBSD.

This errata document for FreeBSD 10.0-RELEASE + will be maintained until the release of FreeBSD 10.1-RELEASE.

Table of Contents

1. Introduction
2. Security Advisories
3. Open Issues
4. Late-Breaking News

1. Introduction

This errata document contains “late-breaking news” about FreeBSD 10.0-RELEASE Before installing this version, it is important to consult this document to learn about any post-release discoveries or problems @@ -32,10 +30,28 @@ out of date by definition, but other copies are kept updated on the Internet and should be consulted as the “current errata” for this release. These other copies of the - errata are located at http://www.FreeBSD.org/releases/, plus any sites + errata are located at + http://www.FreeBSD.org/releases/, + plus any sites which keep up-to-date mirrors of this location.

Source and binary snapshots of FreeBSD 10.0-STABLE also contain up-to-date copies of this document (as of the time of - the snapshot).

For a list of all FreeBSD CERT security advisories, see http://www.FreeBSD.org/security/ or ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/.

2. Security Advisories

No advisories.

3. Open Issues

No open issues.

4. Late-Breaking News

No news.

This file, and other release-related documents, + the snapshot).

For a list of all FreeBSD CERT security advisories, see + http://www.FreeBSD.org/security/ + or ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/.

2. Security Advisories

Advisory	Date	Topic
SA-13:14.openssh	19 November 2013	OpenSSH AES-GCM memory corruption + vulnerability
SA-14:01.bsnmpd	14 January 2014	bsnmpd remote denial of service vulnerability
SA-14:02.ntpd	14 January 2014	ntpd distributed reflection Denial of Service vulnerability
SA-14:03.openssl	14 January 2014	OpenSSL multiple vulnerabilities
SA-14:04.bind< /a>	14 January 2014	BIND remote denial of service vulnerability

3. Open Issues

FreeBSD/i386 10.0-RELEASE running as a guest + operating system on VirtualBox + can have a problem with disk I/O access. It depends on some + specific hardware configuration and does not depend on a + specific version of VitrualBox or + host operating system.
It causes various errors and makes FreeBSD quite unstable. + Although the cause is still unclear, disabling unmapped I/O + works as a workaround. To disable it, choose Escape to + loader prompt in the boot menu and enter the following + lines from loader(8) prompt, after + an OK:
```
set vfs.unmapped_buf_allowed=0
+boot
```
Note that the following line has to be added to + /boot/loader.conf after a boot. + It disables unmapped I/O at every boot:
```
vfs.unmapped_buf_allowed=0
```

4. Late-Breaking News

No news.