FreeBSD Foundation’s Year-End Fundraising Campaign!

The FreeBSD Foundation has announced their end of year fundraising campaign.

So far, the Foundation has raised $256,532 of their $500,000 goal for 2012. Raised funds are used to sponsor projects which add features to the operating system, fund developers to attend DevSummits and conferences, and keep the FreeBSD hardware and web infrastructure going.

If you appreciate the work FreeBSD developers and the FreeBSD Foundation are doing, why not consider making a donation?

FreeBSD Foundation End of Year fundraising campaign. (via)

Countdown to importing BHyVe into FreeBSD

The BHyVe “BSD HyperVisor” developers Neel Natu and Peter Grehan have been hard at work preparing the project for merger into the main FreeBSD 10-CURRENT source tree and the result is a remarkably-usable system. These instructions will show you how to test a development snapshot based on FreeBSD 10.

Check out the CFT page for the instructions.

If you’re interested in finding out more about BHyve, visit the following pages: BHyVe Wiki  |  PDF presentation

 

FreeBSD Security Advisory (Bind)

The FreeBSD Security Team has identified an issue in Bind and has issued the following security advisory: FreeBSD-SA-12:06.bind (22/11/2012).

I. Background

BIND 9 is an implementation of the Domain Name System (DNS) protocols. The named(8) daemon is an Internet Domain Name Server.

II. Problem Description

The BIND daemon would crash when a query is made on a resource record with RDATA that exceeds 65535 bytes. The BIND daemon would lock up when a query is made on specific combinations of RDATA.

III. Impact

A remote attacker can query a resolving name server to retrieve a record whose RDATA is known to be larger than 65535 bytes, thereby causing the resolving server to crash via an assertion failure in named.

For a workaround and solution, check out the security advisory: FreeBSD-SA-12:06.bind

An attacker who is in a position to add a record with RDATA larger than 65535 bytes to an authoritative name server can cause that server to crash by later querying for that record.

The attacker can also cause the server to lock up with specific combinations of RDATA.

Security Incident on FreeBSD Infrastructure

The FreeBSD Security Team has announced that on 11 November two servers as part of the FreeBSD.org hosting infrastructure have been compromised.

The compromise is believed to have occurred due to the leak of an SSH key from a developer who legitimately had access to the machines in question, and was not due to any vulnerability or code exploit within FreeBSD.

No part of the base FreeBSD system has been put at risk and at no point has the intruder modified any part of the FreeBSD base system software. However, the attacker had access sufficient to potentially allow the compromise of third-party packages. No evidence of this has been found during in-depth analysis.

On Sunday 11th of November, an intrusion was detected on two machines within the FreeBSD.org cluster. The affected machines were taken offline for analysis. Additionally, a large portion of the remaining infrastructure machines were also taken offline as a precaution.
We have found no evidence of any modifications that would put any end user at risk. However, we do urge all users to read the report available at http://www.freebsd.org/news/2012-compromise.html and decide on any required actions themselves. We will continue to update that page as further information becomes known. We do not currently believe users have been affected given current forensic analysis, but we will provide updated information if this changes.
As a result of this event, a number of operational security changes are being made at the FreeBSD Project, in order to further improve our resilience to potential attacks. We plan, therefore, to more rapidly deprecate a number of legacy services, such as cvsup distribution of FreeBSD source, in favour of our more robust Subversion, freebsd-update, and portsnap models.
More information is available at http://www.freebsd.org/news/2012-compromise.html