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.