Nabble - freebsd-announce

FreeBSD Security Advisory FreeBSD-SA-09:15.ssl [REVISED]

2009-12-03T12:43:16Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-SA-09:15.ssl Security Advisory
The FreeBSD Project

Topic: SSL protocol flaw

Category: contrib
Module: openssl
Announced: 2009-12-03
Credits: Marsh Ray, Steve Dispensa
Affects: All supported versions of FreeBSD.
Corrected: 2009-12-03 09:18:40 UTC (RELENG_8, 8.0-STABLE)
2009-12-03 09:18:40 UTC (RELENG_8_0, 8.0-RELEASE-p1)
2009-12-03 09:18:40 UTC (RELENG_7, 7.2-STABLE)
2009-12-03 09:18:40 UTC (RELENG_7_2, 7.2-RELEASE-p5)
2009-12-03 09:18:40 UTC (RELENG_7_1, 7.1-RELEASE-p9)
2009-12-03 09:18:40 UTC (RELENG_6, 6.4-STABLE)
2009-12-03 09:18:40 UTC (RELENG_6_4, 6.4-RELEASE-p8)
2009-12-03 09:18:40 UTC (RELENG_6_3, 6.3-RELEASE-p14)
CVE Name: CVE-2009-3555

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

0. Revision History

v1.0 2009-12-03 Initial release.
v1.1 2009-12-03 Corrected instructions in section V.2)b).

I. Background

The SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols
provide a secure communications layer over which other protocols can be
utilized. The most widespread use of SSL/TLS is to add security to the
HTTP protocol, thus producing HTTPS.

FreeBSD includes software from the OpenSSL Project which implements SSL
and TLS.

II. Problem Description

The SSL version 3 and TLS protocols support session renegotiation without
cryptographically tying the new session parameters to the old parameters.

III. Impact

An attacker who can intercept a TCP connection being used for SSL or TLS
can cause the initial session negotiation to take the place of a session
renegotiation. This can be exploited in several ways, including:
* Causing a server to interpret incoming messages as having been sent
under the auspices of a client SSL key when in fact they were not;
* Causing a client request to be appended to an attacker-supplied
request, potentially revealing to the attacker the contents of the client
request (including any authentication parameters); and
* Causing a client to receive a response to an attacker-supplied request
instead of a response to the request sent by the client.

IV. Workaround

No workaround is available.

V. Solution

NOTE WELL: This update causes OpenSSL to reject any attempt to renegotiate
SSL / TLS session parameters. As a result, connections in which the other
party attempts to renegotiate session parameters will break. In practice,
however, session renegotiation is a rarely-used feature, so disabling this
functionality is unlikely to cause problems for most systems.

Perform one of the following:

1) Upgrade your vulnerable system to 6-STABLE, 7-STABLE, or 8-STABLE, or to
the RELENG_8_0, RELENG_7_2, RELENG_7_1, RELENG_6_4, or RELENG_6_3 security
branch dated after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 6.3, 6.4,
7.1, 7.2, and 8.0 systems.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/SA-09:15/ssl.patch
# fetch http://security.FreeBSD.org/patches/SA-09:15/ssl.patch.asc

b) Execute the following commands as root:

# cd /usr/src
# patch < /path/to/patch
# cd /usr/src/secure/lib/libssl
# make obj && make depend && make includes && make && make install

NOTE: On the amd64 platform, the above procedure will not update the
lib32 (i386 compatibility) libraries. On amd64 systems where the i386
compatibility libraries are used, the operating system should instead
be recompiled as described in
<URL:http://www.FreeBSD.org/handbook/makeworld.html>

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_6
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.10.2.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.14.2.3
src/crypto/openssl/ssl/s3_lib.c 1.1.1.10.2.1
RELENG_6_4
src/UPDATING 1.416.2.40.2.12
src/sys/conf/newvers.sh 1.69.2.18.2.14
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.10.12.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.14.2.1.6.2
src/crypto/openssl/ssl/s3_lib.c 1.1.1.10.12.1
RELENG_6_3
src/UPDATING 1.416.2.37.2.19
src/sys/conf/newvers.sh 1.69.2.15.2.18
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.10.10.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.14.2.1.4.2
src/crypto/openssl/ssl/s3_lib.c 1.1.1.10.10.1
RELENG_7
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.12.2.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.17.2.2
src/crypto/openssl/ssl/s3_lib.c 1.1.1.13.2.1
RELENG_7_2
src/UPDATING 1.507.2.23.2.8
src/sys/conf/newvers.sh 1.72.2.11.2.9
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.12.8.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.17.2.1.2.1
src/crypto/openssl/ssl/s3_lib.c 1.1.1.13.8.1
RELENG_7_1
src/UPDATING 1.507.2.13.2.12
src/sys/conf/newvers.sh 1.72.2.9.2.13
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.12.6.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.17.6.2
src/crypto/openssl/ssl/s3_lib.c 1.1.1.13.6.1
RELENG_8
src/crypto/openssl/ssl/s3_pkt.c 1.2.2.1
src/crypto/openssl/ssl/s3_srvr.c 1.3.2.1
src/crypto/openssl/ssl/s3_lib.c 1.2.2.1
RELENG_8_0
src/UPDATING 1.632.2.7.2.4
src/sys/conf/newvers.sh 1.83.2.6.2.4
src/crypto/openssl/ssl/s3_pkt.c 1.2.4.1
src/crypto/openssl/ssl/s3_srvr.c 1.3.4.1
src/crypto/openssl/ssl/s3_lib.c 1.2.4.1
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/6/ r200054
releng/6.4/ r200054
releng/6.3/ r200054
stable/7/ r200054
releng/7.2/ r200054
releng/7.1/ r200054
- -------------------------------------------------------------------------

VII. References

http://extendedsubset.com/Renegotiating_TLS.pdf

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3555

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-SA-09:15.ssl.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iEYEARECAAYFAksYIm4ACgkQFdaIBMps37J5jwCZAQurPSu2CyGz2thi8ljb+MlF
LcwAnjSLYWT1nV5G9a46n9zcrpEqydJ3
=XuZD
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Security Advisory FreeBSD-SA-09:17.freebsd-update

2009-12-03T01:30:49Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-SA-09:17.freebsd-update Security Advisory
The FreeBSD Project

Topic: Inappropriate directory permissions in freebsd-update(8)

Category: core
Module: usr.sbin
Announced: 2009-12-03
Credits: KAMADA Ken'ichi
Affects: All supported versions of FreeBSD.
Corrected: 2009-12-03 09:18:40 UTC (RELENG_8, 8.0-STABLE)
2009-12-03 09:18:40 UTC (RELENG_8_0, 8.0-RELEASE-p1)
2009-12-03 09:18:40 UTC (RELENG_7, 7.2-STABLE)
2009-12-03 09:18:40 UTC (RELENG_7_2, 7.2-RELEASE-p5)
2009-12-03 09:18:40 UTC (RELENG_7_1, 7.1-RELEASE-p9)
2009-12-03 09:18:40 UTC (RELENG_6, 6.4-STABLE)
2009-12-03 09:18:40 UTC (RELENG_6_4, 6.4-RELEASE-p8)
2009-12-03 09:18:40 UTC (RELENG_6_3, 6.3-RELEASE-p14)

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

I. Background

The freebsd-update(8) utility is used to fetch, install, and rollback
updates to the FreeBSD base system, and also to upgrade from one FreeBSD
release to another.

II. Problem Description

When downloading updates to FreeBSD via 'freebsd-update fetch' or
'freebsd-update upgrade', the freebsd-update(8) utility copies currently
installed files into its working directory (/var/db/freebsd-update by
default) both for the purpose of merging changes to configuration files
and in order to be able to roll back installed updates.

The default working directory used by freebsd-update(8) is normally
created during the installation of FreeBSD with permissions which allow
all local users to see its contents, and freebsd-update(8) does not take
any steps to restrict access to files stored in said directory.

III. Impact

A local user can read files which have been updated by freebsd-update(8),
even if those files have permissions which would normally not allow users
to read them. In particular, on systems which have been upgraded using
'freebsd-update upgrade', local users can read freebsd-update's backed-up
copy of the master password file.

IV. Workaround

Set the permissions on the freebsd-update(8) working directory to not
allow unprivileged users to read said directory:

# chmod 0700 /var/db/freebsd-update

Note that if freebsd-update(8) is run using the '-d workdir' option, the
directory which should have its permissions adjusted will be different.

V. Solution

Perform one of the following:

1) Upgrade your vulnerable system to 6-STABLE, 7-STABLE or 8-STABLE,
or to the RELENG_8_0, RELENG_7_2, RELENG_7_1, RELENG_6_4, or
RELENG_6_3 security branch dated after the correction date.

2) To patch your present system:

The following patch has been verified to apply to FreeBSD 6.3, 6.4,
7.1, 7.2, and 8.0 systems.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/SA-09:17/freebsd-update.patch
# fetch http://security.FreeBSD.org/patches/SA-09:17/freebsd-update.patch.asc

b) Execute the following commands as root:

# cd /usr/src
# patch < /path/to/patch
# cd /usr/src/usr.sbin/freebsd-update
# make obj && make depend && make && make install
# chmod 0700 /var/db/freebsd-update

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_6
src/usr.sbin/freebsd-update/freebsd-update.sh 1.2.2.11
src/etc/mtree/BSD.var.dist 1.71.2.4
RELENG_6_4
src/UPDATING 1.416.2.40.2.12
src/sys/conf/newvers.sh 1.69.2.18.2.14
src/usr.sbin/freebsd-update/freebsd-update.sh 1.2.2.10.2.2
src/etc/mtree/BSD.var.dist 1.71.2.3.6.2
RELENG_6_3
src/UPDATING 1.416.2.37.2.19
src/sys/conf/newvers.sh 1.69.2.15.2.18
src/usr.sbin/freebsd-update/freebsd-update.sh 1.2.2.8.2.1
src/etc/mtree/BSD.var.dist 1.71.2.3.4.1
RELENG_7
src/usr.sbin/freebsd-update/freebsd-update.sh 1.8.2.5
src/etc/mtree/BSD.var.dist 1.75.2.1
RELENG_7_2
src/UPDATING 1.507.2.23.2.8
src/sys/conf/newvers.sh 1.72.2.11.2.9
src/usr.sbin/freebsd-update/freebsd-update.sh 1.8.2.4.4.2
src/etc/mtree/BSD.var.dist 1.75.8.2
RELENG_7_1
src/UPDATING 1.507.2.13.2.12
src/sys/conf/newvers.sh 1.72.2.9.2.13
src/usr.sbin/freebsd-update/freebsd-update.sh 1.8.2.4.2.2
src/etc/mtree/BSD.var.dist 1.75.6.2
RELENG_8
src/usr.sbin/freebsd-update/freebsd-update.sh 1.16.2.3
src/etc/mtree/BSD.var.dist 1.75.10.2
RELENG_8_0
src/UPDATING 1.632.2.7.2.4
src/sys/conf/newvers.sh 1.83.2.6.2.4
src/usr.sbin/freebsd-update/freebsd-update.sh 1.16.2.2.2.2
src/etc/mtree/BSD.var.dist 1.75.10.1.2.2
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/6/ r200054
releng/6.4/ r200054
releng/6.3/ r200054
stable/7/ r200054
releng/7.2/ r200054
releng/7.1/ r200054
stable/8/ r200054
releng/8.0/ r200054
- -------------------------------------------------------------------------

VII. References

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-SA-09:17.freebsd-update.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iEYEARECAAYFAksXhA0ACgkQFdaIBMps37Lg+wCfSK5sMXpsxTW9jpgwwcqx+24z
zzwAniR50V8K8/vI0qshCUaKwryEYDuK
=/lsC
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Security Advisory FreeBSD-SA-09:16.rtld

2009-12-03T01:30:43Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-SA-09:16.rtld Security Advisory
The FreeBSD Project

Topic: Improper environment sanitization in rtld(1)

Category: core
Module: rtld
Announced: 2009-12-03
Affects: FreeBSD 7.0 and later.
Corrected: 2009-12-01 02:59:22 UTC (RELENG_8, 8.0-STABLE)
2009-12-03 09:18:40 UTC (RELENG_8_0, 8.0-RELEASE-p1)
2009-12-01 03:00:16 UTC (RELENG_7, 7.2-STABLE)
2009-12-03 09:18:40 UTC (RELENG_7_2, 7.2-RELEASE-p5)
2009-12-03 09:18:40 UTC (RELENG_7_1, 7.1-RELEASE-p9)
CVE Name: CVE-2009-4146, CVE-2009-4147

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

I. Background

The run-time link-editor, rtld, links dynamic executable with their
needed libraries at run-time. It also allows users to explicitly
load libraries via various LD_ environmental variables.

II. Problem Description

When running setuid programs rtld will normally remove potentially
dangerous environment variables. Due to recent changes in FreeBSD
environment variable handling code, a corrupt environment may
result in attempts to unset environment variables failing.

III. Impact

An unprivileged user who can execute programs on a system can gain
the privileges of any setuid program which he can run. On most
systems configurations, this will allow a local attacker to execute
code as the root user.

IV. Workaround

No workaround is available, but systems without untrusted local users,
where all the untrusted local users are jailed superusers, and/or where
untrusted users cannot execute arbitrary code (e.g., due to use of read
only and noexec mount options) are not affected.

Note that "untrusted local users" include users with the ability to
upload and execute web scripts (CGI, PHP, Python, Perl etc.), as they
may be able to exploit this issue.

V. Solution

Perform one of the following:

1) Upgrade your vulnerable system to 7-STABLE or 8-STABLE,
or to the RELENG_8_0, RELENG_7_2, or RELENG_7_1 security branch dated
after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 7.1, 7.2,
and 8.0 systems.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

[FreeBSD 7.x]
# fetch http://security.FreeBSD.org/patches/SA-09:16/rtld7.patch
# fetch http://security.FreeBSD.org/patches/SA-09:16/rtld7.patch.asc

[FreeBSD 8.0]
# fetch http://security.FreeBSD.org/patches/SA-09:16/rtld.patch
# fetch http://security.FreeBSD.org/patches/SA-09:16/rtld.patch.asc

b) Execute the following commands as root:

# cd /usr/src
# patch < /path/to/patch
# cd /usr/src/libexec/rtld-elf
# make obj && make depend && make && make install

NOTE: On the amd64 platform, the above procedure will not update the
ld-elf32.so.1 (i386 compatibility) run-time link-editor (rtld). On
amd64 systems where the i386 rtld are installed, the operating system
should instead be recompiled as described in
<URL:http://www.FreeBSD.org/handbook/makeworld.html>

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_7
src/libexec/rtld-elf/rtld.c 1.124.2.7
RELENG_7_2
src/UPDATING 1.507.2.23.2.8
src/sys/conf/newvers.sh 1.72.2.11.2.9
src/libexec/rtld-elf/rtld.c 1.124.2.4.2.2
RELENG_7_1
src/UPDATING 1.507.2.13.2.12
src/sys/conf/newvers.sh 1.72.2.9.2.13
src/libexec/rtld-elf/rtld.c 1.124.2.3.2.2
RELENG_8
src/libexec/rtld-elf/rtld.c 1.139.2.4
RELENG_8_0
src/UPDATING 1.632.2.7.2.4
src/sys/conf/newvers.sh 1.83.2.6.2.4
src/libexec/rtld-elf/rtld.c 1.139.2.2.2.2
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/7/ r199981
releng/7.2/ r200054
releng/7.1/ r200054
stable/8/ r199980
releng/8.0/ r200054
- -------------------------------------------------------------------------

VII. References

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4146
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4147

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-SA-09:16.rtld.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iEUEARECAAYFAksXg/IACgkQFdaIBMps37KrLwCdH4JsCrvdS1RGoGj7MlNgV3+/
nhYAliVcz9tL8Ll6pYKpIalR740sZ5s=
=jK/a
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Security Advisory FreeBSD-SA-09:15.ssl

2009-12-03T01:30:38Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-SA-09:15.ssl Security Advisory
The FreeBSD Project

Topic: SSL protocol flaw

Category: contrib
Module: openssl
Announced: 2009-12-03
Credits: Marsh Ray, Steve Dispensa
Affects: All supported versions of FreeBSD.
Corrected: 2009-12-03 09:18:40 UTC (RELENG_8, 8.0-STABLE)
2009-12-03 09:18:40 UTC (RELENG_8_0, 8.0-RELEASE-p1)
2009-12-03 09:18:40 UTC (RELENG_7, 7.2-STABLE)
2009-12-03 09:18:40 UTC (RELENG_7_2, 7.2-RELEASE-p5)
2009-12-03 09:18:40 UTC (RELENG_7_1, 7.1-RELEASE-p9)
2009-12-03 09:18:40 UTC (RELENG_6, 6.4-STABLE)
2009-12-03 09:18:40 UTC (RELENG_6_4, 6.4-RELEASE-p8)
2009-12-03 09:18:40 UTC (RELENG_6_3, 6.3-RELEASE-p14)
CVE Name: CVE-2009-3555

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

I. Background

The SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols
provide a secure communications layer over which other protocols can be
utilized. The most widespread use of SSL/TLS is to add security to the
HTTP protocol, thus producing HTTPS.

FreeBSD includes software from the OpenSSL Project which implements SSL
and TLS.

II. Problem Description

The SSL version 3 and TLS protocols support session renegotiation without
cryptographically tying the new session parameters to the old parameters.

III. Impact

An attacker who can intercept a TCP connection being used for SSL or TLS
can cause the initial session negotiation to take the place of a session
renegotiation. This can be exploited in several ways, including:
* Causing a server to interpret incoming messages as having been sent
under the auspices of a client SSL key when in fact they were not;
* Causing a client request to be appended to an attacker-supplied
request, potentially revealing to the attacker the contents of the client
request (including any authentication parameters); and
* Causing a client to receive a response to an attacker-supplied request
instead of a response to the request sent by the client.

IV. Workaround

No workaround is available.

V. Solution

NOTE WELL: This update causes OpenSSL to reject any attempt to renegotiate
SSL / TLS session parameters. As a result, connections in which the other
party attempts to renegotiate session parameters will break. In practice,
however, session renegotiation is a rarely-used feature, so disabling this
functionality is unlikely to cause problems for most systems.

Perform one of the following:

1) Upgrade your vulnerable system to 6-STABLE, 7-STABLE, or 8-STABLE, or to
the RELENG_8_0, RELENG_7_2, RELENG_7_1, RELENG_6_4, or RELENG_6_3 security
branch dated after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 6.3, 6.4,
7.1, 7.2, and 8.0 systems.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/SA-09:15/ssl.patch
# fetch http://security.FreeBSD.org/patches/SA-09:15/ssl.patch.asc

b) Execute the following commands as root:

# cd /usr/src
# patch < /path/to/patch
# cd /usr/src/secure/lib/libcrypto
# make obj && make depend && make includes && make && make install

NOTE: On the amd64 platform, the above procedure will not update the
lib32 (i386 compatibility) libraries. On amd64 systems where the i386
compatibility libraries are used, the operating system should instead
be recompiled as described in
<URL:http://www.FreeBSD.org/handbook/makeworld.html>

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_6
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.10.2.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.14.2.3
src/crypto/openssl/ssl/s3_lib.c 1.1.1.10.2.1
RELENG_6_4
src/UPDATING 1.416.2.40.2.12
src/sys/conf/newvers.sh 1.69.2.18.2.14
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.10.12.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.14.2.1.6.2
src/crypto/openssl/ssl/s3_lib.c 1.1.1.10.12.1
RELENG_6_3
src/UPDATING 1.416.2.37.2.19
src/sys/conf/newvers.sh 1.69.2.15.2.18
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.10.10.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.14.2.1.4.2
src/crypto/openssl/ssl/s3_lib.c 1.1.1.10.10.1
RELENG_7
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.12.2.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.17.2.2
src/crypto/openssl/ssl/s3_lib.c 1.1.1.13.2.1
RELENG_7_2
src/UPDATING 1.507.2.23.2.8
src/sys/conf/newvers.sh 1.72.2.11.2.9
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.12.8.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.17.2.1.2.1
src/crypto/openssl/ssl/s3_lib.c 1.1.1.13.8.1
RELENG_7_1
src/UPDATING 1.507.2.13.2.12
src/sys/conf/newvers.sh 1.72.2.9.2.13
src/crypto/openssl/ssl/s3_pkt.c 1.1.1.12.6.1
src/crypto/openssl/ssl/s3_srvr.c 1.1.1.17.6.2
src/crypto/openssl/ssl/s3_lib.c 1.1.1.13.6.1
RELENG_8
src/crypto/openssl/ssl/s3_pkt.c 1.2.2.1
src/crypto/openssl/ssl/s3_srvr.c 1.3.2.1
src/crypto/openssl/ssl/s3_lib.c 1.2.2.1
RELENG_8_0
src/UPDATING 1.632.2.7.2.4
src/sys/conf/newvers.sh 1.83.2.6.2.4
src/crypto/openssl/ssl/s3_pkt.c 1.2.4.1
src/crypto/openssl/ssl/s3_srvr.c 1.3.4.1
src/crypto/openssl/ssl/s3_lib.c 1.2.4.1
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/6/ r200054
releng/6.4/ r200054
releng/6.3/ r200054
stable/7/ r200054
releng/7.2/ r200054
releng/7.1/ r200054
- -------------------------------------------------------------------------

VII. References

http://extendedsubset.com/Renegotiating_TLS.pdf

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3555

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-SA-09:15.ssl.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iEYEARECAAYFAksXg+oACgkQFdaIBMps37JenACfdPIoOc1uHHsBap0FkH1uctHp
VeoAnirgLeaG00lD6Um6qJK2EjlU8hEg
=dioq
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

BSDCan 2010

2009-11-30T18:04:32Z

Hello folks,

BSDCan 2010 will be held 13-14 May, 2010 in Ottawa at the University of
Ottawa. It will be preceded by two days of tutorials on 11-12 May.

We are now accepting proposals for talks.

The talks should be designed with a very strong technical content bias.
Proposals of a business development or marketing nature are not
appropriate for this venue.

If you are doing something interesting with a BSD operating system,
please submit a proposal. Whether you are developing a very complex
system using BSD as the foundation, or helping others and have a story
to tell about how BSD played a role, we want to hear about your
experience. People using BSD as a platform for research are also
encouraged to submit a proposal. Possible topics include:

* How we manage a giant installation with respect to handling spam.
* and/or sysadmin.
* and/or networking.

From the BSDCan website, the Archives section will allow you to review
the wide variety of past BSDCan presentations as further examples.

Both users and developers are encouraged to share their experiences.

The schedule is:

19 Dec 2009 Proposal acceptance begins
19 Jan 2010 Proposal acceptance ends
19 Feb 2010 Confirmation of accepted proposals

See also <http://www.bsdcan.org/2010/papers.php>

Instructions for submitting a proposal to BSDCan 2010 are available
from: <http://www.bsdcan.org/2010/submissions.php>

_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

Upcoming FreeBSD Security Advisory

2009-11-30T17:20:40Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

A short time ago a "local root" exploit was posted to the full-disclosure
mailing list; as the name suggests, this allows a local user to execute
arbitrary code as root.

Normally it is the policy of the FreeBSD Security Team to not publicly
discuss security issues until an advisory is ready, but in this case
since exploit code is already widely available I want to make a patch
available ASAP. Due to the short timeline, it is possible that this
patch will not be the final version which is provided when an advisory
is sent out; it is even possible (although highly doubtful) that this
patch does not fully fix the issue or introduces new issues -- in short,
use at your own risk (even more than usual).

The patch is at
http://people.freebsd.org/~cperciva/rtld.patch
and has SHA256 hash
ffcba0c20335dd83e9ac0d0e920faf5b4aedf366ee5a41f548b95027e3b770c1

I expect a full security advisory concerning this issue will go out on
Wednesday December 2nd.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iEYEARECAAYFAksUbjcACgkQFdaIBMps37LP9ACgljaYCfgVuhD2gd9Natpq4H/9
i48An1mgl+Mih+AWN7J9KZ1rsiEU31IZ
=MPXj
-----END PGP SIGNATURE-----

--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid

_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD 8.0-RELEASE Available

2009-11-26T16:09:44Z

The FreeBSD Release Engineering Team is pleased to announce the availability
of FreeBSD 8.0-RELEASE. This release starts off the new 8-STABLE branch
which improves on the functionality of FreeBSD 7.X and introduces many
new features. Some of the highlights:

- Xen Dom-U, VirtualBox guest and host, hierarchal jails
- NFSv3 GSSAPI support, experimental NFSv4 client and server
- 802.11s D3.03 wireless mesh networking and Virtual Access Point
support
- ZFS no longer in experimental status
- ground-up rewrite of USB, including USB target support
- continued SMP scalability improvements in many areas, especially
VFS
- revised network link layer subsystem
- experimental MIPS architecture support

For a complete list of new features and known problems, please see the
online release notes and errata list, available at:

http://www.FreeBSD.org/releases/8.0R/relnotes.html
http://www.FreeBSD.org/releases/8.0R/errata.html

For more information about FreeBSD release engineering activities,
please see:

http://www.FreeBSD.org/releng/

Dedication
----------

The FreeBSD Project dedicates this release to the memories of
Jean-Marc Zucconi (jmz@) and John Birrell (jb@) who passed away
in May and November of 2009 respectively. Jean-Marc and John were
both FreeBSD committers since the mid-1990s and made extensive
contributions to the operating system. They will be missed.

Availability
-------------

FreeBSD 8.0-RELEASE is now available for the amd64, i386, ia64, pc98,
powerpc, and sparc64 architectures.

FreeBSD 8.0 can be installed from bootable ISO images or over the
network. Some architectures (currently amd64 and i386) also support
installing from a USB memory stick. The required files can be downloaded
via FTP or BitTorrent as described in the sections below. While some
of the smaller FTP mirrors may not carry all architectures, they will
all generally contain the more common ones such as amd64 and i386.

MD5 and SHA256 hashes for the release ISO and memory stick images are
included at the bottom of this message.

The purpose of the images provided as part of the release are as follows:

dvd1: This contains everything necessary to install the base FreeBSD
operating system, a collection of pre-built packages, and the
documentation. It also supports booting into a "livefs" based
rescue mode. This should be all you need if you can burn
and use DVD-sized media.

disc1: This contains the base FreeBSD operating system and the
documentation packages for CDROM-sized media. There are no
other packages.

livefs: This contains support for booting into a "livefs" based
rescue mode but does not support doing an install from the
CD itself. It is meant to help rescue an existing system
but could be used to do a network based install if necessary.

bootonly: This supports booting a machine using the CDROM drive but
does not contain the support for installing FreeBSD from the
CD itself. You would need to perform a network based install
(e.g. from an FTP server) after booting from the CD.

memstick: This can be written to an USB memory stick (flash drive) and
used to do an install on machines capable of booting off USB
drives. It also supports booting into a "livefs" based rescue
mode. The documentation packages are provided but no other
packages.

As one example of how to use the memstick image, assuming the USB drive
appears as /dev/da0 on your machine something like this should work:

# dd if=8.0-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync

Be careful to make sure you get the target (of=) correct.

FreeBSD 8.0-RELEASE can also be purchased on CD-ROM or DVD from several
vendors. One of the vendors that will be offering FreeBSD 8.0-based
products is:

~ FreeBSD Mall, Inc. http://www.freebsdmall.com/

BitTorrent
----------

8.0-RELEASE ISOs are available via BitTorrent. A collection of torrent
files to download the images is available at:

http://torrents.freebsd.org:8080/

FTP
---

At the time of this announcement the following FTP sites have
FreeBSD 8.0-RELEASE available.

ftp://ftp.freebsd.org/pub/FreeBSD/
ftp://ftp1.freebsd.org/pub/FreeBSD/
ftp://ftp5.freebsd.org/pub/FreeBSD/
ftp://ftp10.freebsd.org/pub/FreeBSD/
ftp://ftp13.freebsd.org/pub/FreeBSD/
ftp://ftp14.freebsd.org/pub/FreeBSD/
ftp://ftp.br.freebsd.org/pub/FreeBSD/
ftp://ftp.cz.freebsd.org/pub/FreeBSD/
ftp://ftp.dk.freebsd.org/pub/FreeBSD/
ftp://ftp.fr.freebsd.org/pub/FreeBSD/
ftp://ftp.jp.freebsd.org/pub/FreeBSD/
ftp://ftp.ru.freebsd.org/pub/FreeBSD/
ftp://ftp1.ru.freebsd.org/pub/FreeBSD/
ftp://ftp.tw.freebsd.org/pub/FreeBSD/
ftp://ftp4.tw.freebsd.org/pub/FreeBSD/
ftp://ftp.uk.freebsd.org/pub/FreeBSD/
ftp://ftp1.us.freebsd.org/pub/FreeBSD/
ftp://ftp5.us.freebsd.org/pub/FreeBSD/
ftp://ftp10.us.freebsd.org/pub/FreeBSD/

However before trying these sites please check your regional mirror(s)
first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

More information about FreeBSD mirror sites can be found at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html

For instructions on installing FreeBSD, please see Chapter 2 of The
FreeBSD Handbook. It provides a complete installation walk-through
for users new to FreeBSD, and can be found online at:

http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html

Updates from Source
-------------------

The procedure for doing a source code based update is described in the
FreeBSD Handbook:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html

The branch tag to use for updating the source is RELENG_8_0.

FreeBSD Update
--------------

The freebsd-update(8) utility supports binary upgrades of i386 and amd64
systems running earlier FreeBSD releases. Systems running 7.[012]-RELEASE,
8.0-BETA[1234], or 8.0-RC[123] can upgrade as follows:

# freebsd-update upgrade -r 8.0-RELEASE

During this process, FreeBSD Update may ask the user to help by merging
some configuration files or by confirming that the automatically
performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new
userland components:

# freebsd-update install

At this point, users of systems being upgraded from FreeBSD 8.0-BETA2 or
earlier will be prompted by freebsd-update to rebuild all third-party
applications (e.g., ports installed from the ports tree) due to updates
in system libraries. See:

http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html

for more details. After updating installed third-party applications
(and again, only if freebsd-update printed a message indicating that
this was necessary), run freebsd-update again so that it can delete the
old (no longer used) system libraries:

# freebsd-update install

Finally, reboot into 8.0-RELEASE:

# shutdown -r now

Support
-------

The FreeBSD Security Team currently plans to support FreeBSD 8.0 until
November 30th, 2010. For more information on the Security Team and
their support of the various FreeBSD branches see:

http://www.freebsd.org/security/

Acknowledgments
---------------

Many companies donated equipment, network access, or man-hours to
support the release engineering activities for FreeBSD 8.0 including
The FreeBSD Foundation, Hewlett-Packard, Yahoo!, NetApp,
Internet Systems Consortium, and Sentex Communications.

The release engineering team for 8.0-RELEASE includes:

Ken Smith <kensmith@...> Release Engineering,
amd64, i386, sparc64 Release Building,
Mirror Site Coordination
Robert Watson <rwatson@...> Release Engineering, Security
Konstantin Belousov <kib@...> Release Engineering
Marc Fonvieille <blackend@...> Release Engineering, Documentation
George Neville-Neil <gnn@...> Release Engineering
Hiroki Sato <hrs@...> Release Engineering, Documentation
Bjoern Zeeb <bz@...> Release Engineering
Marcel Moolenaar <marcel@...> ia64, powerpc Release Building
Takahashi Yoshihiro <nyan@...> PC98 Release Building
Joe Marcus Clarke <marcus@...> Package Building
Erwin Lansing <erwin@...> Package Building
Mark Linimon <linimon@...> Package Building
Pav Lucistnik <pav@...> Package Building
Ion-Mihai Tetcu <itetcu@...> Package Building
Martin Wilke (miwi@...> Package Building
Colin Percival <cperciva@...> Security Officer

Trademark
---------

FreeBSD is a registered trademark of The FreeBSD Foundation.

ISO Image Checksums
-------------------

MD5 (8.0-RELEASE-amd64-bootonly.iso) = 49ccdac2e01b33c943ae89233c465ef1
MD5 (8.0-RELEASE-amd64-disc1.iso) = eba84fbd08133cbc8c9ed67be27ee0c8
MD5 (8.0-RELEASE-amd64-dvd1.iso) = 44c016ae8812a266f710d1845722366d
MD5 (8.0-RELEASE-amd64-livefs.iso) = 8db54cfc97b2afa97fb13dbccace4bfa
MD5 (8.0-RELEASE-amd64-memstick.img) = b4558fa30d13776988d86477e9631887

MD5 (8.0-RELEASE-i386-bootonly.iso) = aede8888c250b648bf799d508bc9bf9d
MD5 (8.0-RELEASE-i386-disc1.iso) = ace0afedfa7c6e0ad12c77b6652b02ab
MD5 (8.0-RELEASE-i386-dvd1.iso) = 5336cd827991e4d4cff6d73c4a5ca105
MD5 (8.0-RELEASE-i386-livefs.iso) = 7f4f0ab014f853c8a99c053c2dc12641
MD5 (8.0-RELEASE-i386-memstick.img) = 0a769af739a92f5f495d1a6842e8150b

MD5 (8.0-RELEASE-ia64-bootonly.iso) = be9dcfc2f638d5f86e21b0b344bec91b
MD5 (8.0-RELEASE-ia64-disc1.iso) = e982547f376432d09be603b117f4da54
MD5 (8.0-RELEASE-ia64-disc2.iso) = 5bc7616212e6977c4f054a84ef538615
MD5 (8.0-RELEASE-ia64-disc3.iso) = cefe2fd4694f5065e55778f879dc5852
MD5 (8.0-RELEASE-ia64-dvd1.iso) = 6b8df7fb34d5960ecf91a291926a1e6f
MD5 (8.0-RELEASE-ia64-livefs.iso) = fe7933f2c1ddc2f4a90d5dfc48c38995

MD5 (8.0-RELEASE-pc98-bootonly.iso) = 16a29c2e31025c02997de21aac5041bb
MD5 (8.0-RELEASE-pc98-disc1.iso) = 58e423d5a0a69a72016ebbecde265abd
MD5 (8.0-RELEASE-pc98-livefs.iso) = 6ad13607eb305338edd9501310e6699c

MD5 (8.0-RELEASE-powerpc-bootonly.iso) = f60f73d55100f664c635c6848f00c6d8
MD5 (8.0-RELEASE-powerpc-disc1.iso) = 1323203ffeb317f47219ed8927449980
MD5 (8.0-RELEASE-powerpc-disc2.iso) = 5967750bf681428d59070a133b272bfd
MD5 (8.0-RELEASE-powerpc-disc3.iso) = 43e4846683ce43fa8d6158c703767635

MD5 (8.0-RELEASE-sparc64-bootonly.iso) = 75b2f04c29e6b81058944e42055fe604
MD5 (8.0-RELEASE-sparc64-disc1.iso) = f4aa61db620c97089641a0c63531225a
MD5 (8.0-RELEASE-sparc64-dvd1.iso) = 85307705213a86a383e21941ee34d8e2
MD5 (8.0-RELEASE-sparc64-livefs.iso) = 1ff6d6a449975dcc829f328b866f8128

SHA256 (8.0-RELEASE-amd64-bootonly.iso) = b0e07e8f92303b61220cba18691e86ab50d67c7df974bb62a6f1d4ffb94a1ee6
SHA256 (8.0-RELEASE-amd64-disc1.iso) = 7d4583c20c651093b208170a7fd4ed5f38ee5af0cbe19fb742f67175a9fee10f
SHA256 (8.0-RELEASE-amd64-dvd1.iso) = 408f7fdf3226d72564f2476fff365e4fd071bd48ddae26cd34755d808ad54b8b
SHA256 (8.0-RELEASE-amd64-livefs.iso) = ae939a96b3b3691df84227a33de5d5f4a76d469379dca27114c3557ed443a8f3
SHA256 (8.0-RELEASE-amd64-memstick.img) = b6cd7b0644f636f2099820ad1250940975fa3bfc19f74a0a94f69e75cc2be4c2

SHA256 (8.0-RELEASE-i386-bootonly.iso) = 12e32cea29b2f7bf873df43321a1a93d45b48a6fbb37c8e1c7f3003d5ce82e5d
SHA256 (8.0-RELEASE-i386-disc1.iso) = d7ef47a76a20a716c006a635b476ed3515830b8442ded2702ed015f0bde32bcf
SHA256 (8.0-RELEASE-i386-dvd1.iso) = 8b7bc67599fffc443ebc08efae8a49dd4a0fed7512cfb02b963b9a218e7c286c
SHA256 (8.0-RELEASE-i386-livefs.iso) = feb8998bf2b9dbd6ae86f24feb9ab3c25983dc62c9f4a27f6a5314c3a4a7b59a
SHA256 (8.0-RELEASE-i386-memstick.img) = 7e9b9cd2fd7af0fa0715b826a034b83b0f732a544a51cac7539ead5522a08806

SHA256 (8.0-RELEASE-ia64-bootonly.iso) = c594debd1cb629bf4c906da79c4a6d47b24cf4836d7690f18bc42ee9e31b6b92
SHA256 (8.0-RELEASE-ia64-disc1.iso) = c7f4bd197ff9996ead66f4c77d077e115d18a2822e006bdfdc86a5824dcef37e
SHA256 (8.0-RELEASE-ia64-disc2.iso) = bfcd99680bc15e1b66329a0e71eaf6b38b44d1909a3fb43ba5485238e6807dfd
SHA256 (8.0-RELEASE-ia64-disc3.iso) = 8e8edea7117239af60c07c7e724567ea276fa32d8634f04dd30312e72b35df9a
SHA256 (8.0-RELEASE-ia64-dvd1.iso) = bd1c9a3e8a6a287ee7bef62b3e15646d76a97dec3108177a7c606706a7ee9952
SHA256 (8.0-RELEASE-ia64-livefs.iso) = 60a9a7738ad94765cad45dbc4f62913dd728b335d22bb4e5b065c0cae40a99db

SHA256 (8.0-RELEASE-pc98-bootonly.iso) = 7df38839c8da226bca8ef18b00f0b680074267b8333a393c3431f9b620f0ab9f
SHA256 (8.0-RELEASE-pc98-disc1.iso) = b41fb185b1e057ee36ae6e080021f309a379c3fdf5d45a0a40461092d31e052a
SHA256 (8.0-RELEASE-pc98-livefs.iso) = 1313ec3d5a28af8a85c181cd702b2adb91c783db7e2ad2021d311686ce5e0c2d

SHA256 (8.0-RELEASE-powerpc-bootonly.iso) = 78e18d76c24c9636b87f1946f2020a0a58fc70b80bcb925c27fa497b3c9e5bb4
SHA256 (8.0-RELEASE-powerpc-disc1.iso) = 80f5c024b61629b77a73fd396917c68b4d0215019a5e5aaf5882cf14144764a2
SHA256 (8.0-RELEASE-powerpc-disc2.iso) = 28c8e62c10b42fe5fb1e7a2235a6decbddbbfece0535ea42174c7ac937735068
SHA256 (8.0-RELEASE-powerpc-disc3.iso) = e36db6e05b434a0256e977cab9e3eedb5984b2c45c400a14d7c69bbf4dda9065

SHA256 (8.0-RELEASE-sparc64-bootonly.iso) = 941b5e76a67960045040c268894b8666f5b7a8cbd2e9f98186f2618abb5bf431
SHA256 (8.0-RELEASE-sparc64-disc1.iso) = 2d0a74cf867fa34c5a073777cf2d8e2469906425c9a54068892bd2d58ac9c3c5
SHA256 (8.0-RELEASE-sparc64-dvd1.iso) = 482447b382fa50ffdc80e02a0cfd774e0eecf7d009e5b06864e8a4f828536876
SHA256 (8.0-RELEASE-sparc64-livefs.iso) = 7499ca1af16de7b3d431741b1551a4b59f277fda997d57cf2615155992beaef7

attachment0 (203 bytes) Download Attachment

Death announcement for John Birrell

2009-11-24T14:04:57Z

Dear Friends,

It is with great sadness that I announce the passing of FreeBSD
committer John Birrell <jb@...>.

John Birrell / jb@...

BACKGROUND
==========
John Birrell was a Unix developer since 1988 and a FreeBSD user since version 1.0.5.
He had a Bachelor Degree in Engineering (Electrical, First Class Honours, 1981)
from Monash University in Australia.

Over the years he developed with various commercial Unix variants such as SysVR2/3,
Solaris, AIX, HP-UX, OSF/1 and SCO and several embedded operatings systems
like VxWorks, LynxOS and Microware's OS9.

In the open source world he was once a user of NetBSD and OpenBSD in addition to FreeBSD.
Afterwards, he preferred just to use FreeBSD.

In 20 years of consulting he worked in the automotive, building materials,
pharmaceutical, petrochemical, telecommunications, defence and business systems industries.

John worked on an oil rig in China, for Ford in Australia, and for other customers
in Philippines and other parts of Asia.

While on a business trip visiting his employer Juniper Networks in Sunnyvale, California,
U.S.A., John suffered a stroke, and passed away on November 20, 2009.

FREEBSD CONTRIBUTIONS
=====================

John Birrell was a member of the FreeBSD project, for over 12 years,
and could commit to the FreeBSD source code. John felt passionately
about FreeBSD, and his contributions to this software project were many and varied:

- port of Sun's DTrace to FreeBSD (2007)
- contributed BSD licensed libdwarf to FreeBSD (2008)
- contributed initial implementation of FreeBSD on DEC Alpha, from NetBSD (1998)
-> this was the first 64-bit OS that FreeBSD ran on
- contributed original libc_r pthread implementation to FreeBSD before KSE (1998)
- contributed to port of Sun UltraSPARC-T1 (Niagara) to FreeBSD (2005)

John also participated as a mentor in the Google Summer of Code project.
For Google Summer of Code, John mentored students in various FreeBSD
projects that were funded by Google. Mentoring new developers and colleagues
was something that John felt very strongly about.

John also liked to attend BSD conferences. In May 2009, I attended
the BSDCan conference with John in Ottawa, Canada. He was in his element,
and had many interesting and animated discussions with other FreeBSD developers,
including people like Randall Stewart.

JBUILD
======

As part of John's work at Juniper Networks in 2008, John started working
on a project called jbuild. jbuild is a modification of the
FreeBSD make(1) utility, which adds improved dependency tracking as a first
level feature, by tracking read/write system calls of all invoked utilities,
either by using DTrace, or by using a special kernel module named filemon.

At Juniper, the project is ongoing and will be deployed as part of the
software build at Juniper next year.

Although this work was started in response to needs at Juniper,
John was quite passionate about pushing this work back to FreeBSD, in order
to improve the FreeBSD build. John observed that in FreeBSD,
a "make universe" which verifies that all code changes work on all
architectures takes so long that very few people actually do it, so
less popular architectures often get broken. John also observed that
by simplifying a "make universe" and other "buildworld" targets often
rebuilds a lot of things unnecessarily, due to the fact that it is "safer"
to do so, because the dependencies are not tracked as accurately as they could be.

John has a branch in the FreeBSD svn repo for building all of FreeBSD with jbuild here:

http://svn.freebsd.org/viewvc/base/projects/jbuild/

I will update this branch as I have time, but it would be nice if folks in
the FreeBSD community could keep this work alive.

John was keen that distributions like PC-BSD could adopt jbuild.
John wanted to simplify the FreeBSD build, to make it easier
for people to make new distributions based on FreeBSD.

Let me know if you want to learn more about any of this stuff.

PERSONAL
========

John lived alone on a 118 acre rural property in Apollo Bay, Australia, which
is on the southeastern coast of Australia, approximately 4 hours from Melbourne.

His house was not connected to the local grid.....his water supply
was obtained from tanks on his roof which were filled with rainwater.
His electricity was supplied by solar cells.

On one trip to Sunnyvale in 2008, he bought an alcohol distilling device
which he brought back home. His goal was to try to grow potato and sugar
beets on his property, and distill them into alcohol, so that he
could fuel is car with ethanol instead of gasoline, thus having
a very minimal carbon footprint.

John was also passionate about animal welfare. He owned a few
cats, and just bought a puppy dog in 2009. In 2008, when massive fires
swept much of the Australian countryside, he took time
off of Juniper to volunteer with Wildlife Victoria.
This organization provided assistance to many animals who suffered
during the fires, such as kangaroos, wallabies, and even pets
of people who abandoned their properties when fleeing the fires.

John also liked motorcycles. He told me stories about how he
motorcycled around Asia many years ago. He was also hoping
to buy a motorcycle to garage in California, so that he could
drive it whenever he visited Sunnyvale.

WORKING WITH JOHN
=================

I worked very closely with John over the past year.
I was in constant communication with John over IRC chat,
and Skype. I also Skyped John into many meetings, to keep
him up to date on the pulse of what was going on in Juniper.
Although John was in a remote place, he felt like he was
in the cube next to me.

John was very patient with me and took the time to explain point by point what he
was trying to achieve with jbuild and why it solved legitimate problems
with make(1) based builds.

John also had taste for good "expensive" food and fine wine.
In 2009, as thanks for my help in working on jbuild,
John treated me to a sumptuous and expensive meal at
Sent Sovi Restaurant, in Saratoga, California, U.S.A......a fond memory for me. :)

John was one of the smartest engineers that I have ever worked
with, and was a mentor and friend.

SUMMARY
=======

I am going to miss talking to John every day on IRC, hearing interesting stories
about living in rural Australia, and solving new and challenging
technical problems with him. His passion really pushed me to work very hard on jbuild,
and learn new things. I will miss him as a colleague, mentor, and friend.

--
Craig Rodrigues
rodrigc@...
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Foundation End-of-Year Fundraising Campaign

2009-11-17T13:32:10Z

Dear FreeBSD Community,

Since the start of our 'Be Counted!' campaign in August of this year,
over 350 new and returning donors have contributed to the FreeBSD
Foundation. With your help, we are now 50% of the way to meeting our
2009 fund raising goal. Thank you donors, for your support! Now, in
these last few weeks of 2009, the FreeBSD Foundation needs the support
of those who have yet to donate to take us the rest of the way.

The recession has hit everyone hard. For many, every possible expense
has been cut, and what spending they do is out of strict necessity.
Unfortunately the challenges facing FreeBSD are undiminished by recessions
and the technological landscape continues to change at a rampant pace.
That is why the FreeBSD Foundation nearly doubled its 2008 budget for
2009 and needs your support so we can avoid cutting our investments in
2010.

If you benefit from FreeBSD, please donate so:

o development projects are funded to support emerging technologies such
as solid state disks, USB 3.0, machine and network virtualization,
highly parallel processors, clustering, and data replication.
o BSD conferences continue around the globe.
o students and contributors have the opportunity to attend conferences
and developer summits.
o the infrastructure of computers and equipment supporting our community
can be maintained.
o the FreeBSD community is grown through marketing and outreach to
users and businesses.
o FreeBSD trademarks are protected and the project has access to
legal counsel.
o FreeBSD continues to serve as the foundation for research
and enterprise.

Every donation, no matter its size, makes this work possible. As a
non-profit with very low overhead, your donation is the best way to
invest in FreeBSD. Please make that investment today so we can meet
our dual goals for 2009 of 1000 donors and $300,000.

You can make a donation (including recurring subscriptions) by going to:
http://www.freebsdfoundation.org/donate/.

To find out more about The FreeBSD Foundation, please visit
http://www.freebsdfoundation.org.

Thank You,

Justin T. Gibbs
President and Founder
The FreeBSD Foundation
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

BSDCan 2010 - dates

2009-11-02T20:35:47Z

Hello folks,

BSDCan 2010 will be held 13-14 May, 2010 in Ottawa, at the University of
Ottawa. It will be preceded by two days of tutorials on 11-12 May.

NOTE: the conference is Tue-Fri with social events planned for Saturday.
This differs from previous years when it was Wed-Sat.

--
Dan Langille - http://www.langille.org/
BSDCan - The Technical BSD Conference: http://www.bsdcan.org/
PGCon - The PostgreSQL Confernce: http://www.pgcon.org/

_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

Flattened Device Tree Project Announcement

2009-10-21T06:48:44Z

Dear FreeBSD Community,

The FreeBSD Foundation is pleased to announce another funded project!

Rafal Jaworowski and Semihalf has been awarded a grant to provide
FreeBSD with support for the flattened device tree (FDT) technology.
This project allows for describing hardware resources of a computer
system and their dependencies in a platform-neutral and portable way.

The main consumers of this functionality are embedded systems whose
hardware resources assignment cannot be probed or self-discovered.

The FDT idea is inherited from Open Firmware IEEE 1275 device-tree
notion (part of the regular Open Firmware implementation), and among
other deployments is used as a basis for Power.org's embedded platform
reference specification (ePAPR).

"Thanks to this project, embedded FreeBSD platforms will grow in a
uniform and extensible way of representing hardware devices, compliant
with industry standards (ePAPR, Open Firmware), independent of
architecture and platform (portable across ARM, MIPS, PowerPC etc.),"
said Rafal Jaworoski, FreeBSD Developer.

Semihalf is a privately owned company, based in Krakow, Poland. They
specialize in embedded systems design and development, with expertise in
both software and hardware. Among their portfolio are FreeBSD ports to
high-end embedded processors (including multi-core) with a wide range of
peripheral drivers (storage, networking, pattern matching, security
engines etc.); most of this work is publicly available from the FreeBSD
repository.

You can find out more about the project at
http://wiki.freebsd.org/FlattenedDeviceTree.

This project will complete by February 2010.

Sincerely,

The FreeBSD Foundation
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

HAST Project Announcement

2009-10-21T06:30:01Z

Dear FreeBSD Community,

The FreeBSD Foundation is pleased to announce a new funded project!

Pawel Jakub Dawidek has been awarded a grant to implement storage
replication software that will enable users to use the FreeBSD operating
system for highly available configurations where data has to be shared
across the cluster nodes. The project is partly being funded by OMCnet
Internet Service (GmbH www.omc.net) and TransIP BV (www.transip.nl).

The software will allow for synchronous block-level replication of any
storage media (GEOM providers, using FreeBSD nomenclature) over the
TCP/IP network and for fast failure recovery. HAST will provide storage
using GEOM infrastructure, which means it will be file system and
application independent and could be combined with any existing GEOM
class. In case of a master node failure, the cluster will be able to
switch to the slave node, check and mount UFS file system or import ZFS
pool and continue to work without missing a single bit of data.

"High-availability is the number one requirement for any serious use of
any operating system," said Pawel Jakub Dawidek, FreeBSD Developer.
"Highly available storage is one of the key components in such
environments. I strongly believe there are many FreeBSD users that have
been waiting a long time for this functionality. I'll do my best to
deliver software that matches FreeBSD quality and that will satisfy the
needs of our users."

Pawel has been an active FreeBSD committer since 2003. During this
period, he has touched almost every part of the kernel. But, his main
interest in FreeBSD is storage and security related topics. Pawel is the
author of various GEOM classes (eli, mirror, gate, label, journal, hsec,
etc.), geom(8) utility, various opencrypto improvements as well as port
of the ZFS file system from OpenSolaris to FreeBSD.

The project will complete by February 2010.

Sincerely,

The FreeBSD Foundation

_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

Portmaster funding proposal

2009-10-18T17:23:44Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I have launched an initiative to give the community the opportunity to
fund further development work on portmaster. As much as I love doing
this work I need to be able to support myself and my family and the
kinds of features that users have requested (such as package support)
will take a lot of time to implement correctly.

The URL is here: http://dougbarton.us/portmaster-proposal.html

Several users have been kind enough to send donations and I have
updated the web page to indicate the work that has been completed, and
that which is in progress.

If you have any interest in funding this project take a look at that
web page. Of course additional ideas for features are also welcome.

Finally, if you find this message unwelcome or inappropriate in any
way please accept my apologies.

Regards,

Doug

- --

Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)

iEYEAREDAAYFAkrbsY8ACgkQyIakK9Wy8Pu7cACgoko/evOX/4VXHnN49DqvU558
rlkAn1K5oa2KPxPCspHFg76qIhQmg5W7
=KXY+
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

HEADS UP: FreeBSD 6.3 EoL coming soon

2009-10-18T05:37:32Z

Hi all,

On January 31st, FreeBSD 6.3 will reach its End of Life and will no longer be
supported by the FreeBSD Security Team. Users of this release are strongly
encouraged to upgrade to a newer release before that date -- more conservative
users will probably wish to upgrade to FreeBSD 6.4 or FreeBSD 7.1 (which are
both extended-support branches), while others will probably wish to upgrade to
FreeBSD 7.2 or the upcoming FreeBSD 8.0.

The freebsd-update(8) utility can be used to upgrade i386 and amd64 systems
from 6.3-RELEASE (or 6.3-RELEASE-pX for some X) to 6.4-RELEASE using binary
updates (i.e., without compiling from source) as described in the 6.4-RELEASE
announcement; given an adequate internet connection, this process usually takes
15 minutes or less.

The current supported branches and expected EoL dates are:

+---------------------------------------------------------------------+
| Branch | Release | Type | Release date | Estimated EoL |
|-----------+------------+--------+-----------------+-----------------|
|RELENG_6 |n/a |n/a |n/a |November 30, 2010|
|-----------+------------+--------+-----------------+-----------------|
|RELENG_6_3 |6.3-RELEASE |Extended|January 18, 2008 |January 31, 2010 |
|---------------------------------------------------------------------|
|RELENG_6_4 |6.4-RELEASE |Extended|November 18, 2008|November 30, 2010|
|---------------------------------------------------------------------|
|RELENG_7 |n/a |n/a |n/a |last release + 2y|
|-----------+------------+--------+-----------------+-----------------|
|RELENG_7_1 |7.1-RELEASE |Extended|January 4, 2009 |January 31, 2011 |
|-----------+------------+--------+-----------------+-----------------|
|RELENG_7_2 |7.2-RELEASE |Normal |May 4, 2009 |May 31, 2010 |
+---------------------------------------------------------------------+

When FreeBSD 8.0-RELEASE is released, it will receive "Normal" support, i.e., it
will be supported for at least 12 months.

--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Status Reports April - September, 2009

2009-10-11T10:54:58Z

FreeBSD Quarterly Status Report

Introduction

This report covers FreeBSD related projects between April and September
2009. During that time a lot of work has been done on wide variety of
projects, including the Google Summer of Code projects. The BSDCan
conference was held in Ottawa, CA, in May. The EuroBSDCon conference
was held in Cambridge, UK, in September. Both events were very
successful. A new major version of FreeBSD, 8.0 is to be released soon.
If you are wondering what's new in this long-awaited release, read Ivan
Voras' excellent summary.

Thanks to all the reporters for the excellent work! We hope you enjoy
the reading.

Please note that the next deadline for submissions covering reports
between October and December 2009 is January 15th, 2010.
__________________________________________________________________

Google Summer of Code

* About Google Summer of Code 2009
* BSD-licensed iconv (Summer of Code 2009)
* BSD-licensed text-processing tools (Summer of Code 2008)
* Ext2fs Status report (Summer of Code 2009)
* libnetstat(3) - networking statistics (Summer of Code 2009)
* pefs - stacked cryptographic filesystem (Summer of Code 2009)

Projects

* BSD# Project
* Clang replacing GCC in the base system
* FreeBSD TDM Framework
* Grand Central Dispatch - FreeBSD port
* libprocstat(3) - process statistics
* New BSD licensed debugger
* NFSv4 ACLs
* The Newcons project
* VirtualBox on FreeBSD

FreeBSD Team Reports

* FreeBSD Bugbusting Team
* FreeBSD KDE Team
* FreeBSD Ports Management Team
* Release Engineering Status Report
* The FreeBSD Foundation Status Report

Network Infrastructure

* Enhancing the FreeBSD TCP Implementation
* Modular Congestion Control
* Network Stack Virtualization
* Stream Control Transmission Protocol (SCTP)

Kernel

* FreeBSD/ZFS
* hwpmc for MIPS

Documentation

* The FreeBSD Dutch Documentation Project
* The FreeBSD German Documentation Project
* The FreeBSD Hungarian Documentation Project
* The FreeBSD Spanish Documentation Project

Architectures

* FreeBSD/sparc64

Ports

* FreeBSD Gecko Project
* Portmaster - utility to assist users with managing ports
* Valgrind suite on FreeBSD

Miscellaneous

* EuroBSDcon 2009
* FreeBSD Developer Summit, Cambridge UK
* New approach to the locale database
* The FreeBSD Forums
__________________________________________________________________

About Google Summer of Code 2009

URL: http://socghop.appspot.com/org/home/google/gsoc2009/freebsd
URL: http://wiki.freebsd.org/SummerOfCode2009Projects

Contact: Brooks Davis <brooks@...>
Contact: Tim Kientzle <kientzle@...>
Contact: Robert Watson <rwatson@...>

2009 was The FreeBSD Project's fifth year of participation in the
Google Summer of Code. We had a total of 17 successful projects. Some
GSoC code will be shipping with FreeBSD 8.0-RELEASE and others will be
integrated into future releases.

The FreeBSD GSoC admin team would like to thank Google and our students
and mentors of another great year!
__________________________________________________________________

BSD# Project

URL: http://code.google.com/p/bsd-sharp/
URL: http://www.mono-project.org/

Contact: Romain Tartičre <romain@...>

The BSD# Project is devoted to porting the Mono .NET framework and
applications to the FreeBSD operating system.

During the past year, the BSD# Team continued to track the Mono
development and the lang/mono port have almost always been up-to-date
(we however had to skip mono-2.2 because of some regression issues in
this release). Most of our patches have been merged in the mono trunk
upstream, and should be included in the upcoming mono-2.6 release.

In the meantime, a few more .NET related ports have been updated or
added to the FreeBSD ports tree. These ports include:
* www/xsp and www/mod_mono that make it possible to use FreeBSD for
hosting ASP.NET application;
* lang/boo, a CLI-targeted programming language similar to Python;
* lang/mono-basic, the Visual Basic .NET Framework for Mono;
* devel/monodevelop, an Integrated Development Environment for .NET;
* and much more...

Open tasks:

1. Test mono ports and send feedback (we are especially interested in
tests where NOPORTDOCS / WITH_DEBUG is enabled).
2. Port the mono-debugger to FreeBSD.
3. Build a debug live-image of FreeBSD so that Mono hackers without a
FreeBSD box can help us fixing bugs more efficiently.
__________________________________________________________________

BSD-licensed iconv (Summer of Code 2009)

URL: http://wiki.freebsd.org/G%C3%A1borSoC2009

Contact: Gábor Kövesdán <gabor@...>

The code has been extracted from NetBSD and has been transformed into
an independent shared library. The basic encodings are well supported.
Almost all forward conversions (foo -> UTF-32) are compatible with GNU
but the reverse ones are not so accurate because of GNU's advanced
transliteration. Some extra encodings have also been added. There are
two modules, which segfault; they need some debugging. I can keep
working on this project as part of my BSc thesis, so I hope to be able
to solve the remaining issues. Improved GNU compatibility is also very
desired (extra command line options for iconv(1), iconvctl(), private
interfaces, etc.).

Open tasks:

1. Fix segfaults in Big5 and HZ modules
2. Improve transliteration in reverse encodings
3. Improve GNU compatibility by implementing extra features
4. Verify POSIX compatibility
5. Verify GNU compatibility
6. Check performance
__________________________________________________________________

BSD-licensed text-processing tools (Summer of Code 2008)

URL: http://wiki.freebsd.org/G%C3%A1borSoC2008

Contact: Gábor Kövesdán <gabor@...>

This project was started as part of Google Summer of Code 2008 but
there is still a bit of work to complete some missing parts. The
BSD-licensed grep implementation is feature-complete and has a good
level of GNU compatibility. Our only current concern about the
BSD-licensed version is to improve its performance. The GNU variant is
much more complex, has about 8 KSLOC, while BSD grep is tiny, has only
1.5 KSLOC. GNU uses some shortcuts and optimizations to speed-up calls
to the regex library; that is why it is significantly faster. My point
of view is that such optimizations must be implemented in the regex
library, keeping the dependent utilities clean and easy to read. BSD
grep is so tiny that there is hardly any optimization opportunity by
simplifying the code, so the regex library is the next important TODO.
There is another issue with the current regex library. It does not
support some invalid regular expressions, which work in GNU. We need to
maintain compatibility, so we cannot just drop this feature. Actually,
BSD grep is linked to the GNU regex library to maintain this feature
but due to the lack of the mentioned shortcuts, it is still slower than
GNU. Anyway, if we can live with this little performance hit until we
get a modern regex library, I think grep is ready to enter HEAD. As for
the regex library, NetBSD's result of the last SoC is worth taking a
look.

The sort utility has been rewritten from scratch. The existing
BSD-licensed implementation could not deal with wide characters by
design. The new implementation is still lacking some features but is
quite complete. There is a performance issue, though. Sorting is a
typical algorithmic subject but I am not an algorithmic expert, so my
implementation is not completely optimal. Some help would be welcome
with this part.

The bc/dc utilities have been ported from OpenBSD. They pass OpenBSD's
and GNU's regression tests but they arrived too late to catch 8.X, so
they will go to HEAD after the release.

Open tasks:

1. Improve sort's sorting and file merging algorithms
2. Complete missing features for sort
3. Get a modern regex library for FreeBSD
__________________________________________________________________

Clang replacing GCC in the base system

URL: http://wiki.freebsd.org/BuildingFreeBSDWithClang

Contact: Ed Schouten <ed@...>
Contact: Roman Divacky <rdivacky@...>
Contact: Brooks Davis <brooks@...>
Contact: Pawel Worach <pawel.worach@...>

The clang@FreeBSD team presents the status of clang/LLVM being able to
compile FreeBSD system. The current status is:
* i386 - kernel boots, world needs little hacks but works
* amd64 - kernel boots, world needs little hacks but works
* ppc - broken because of unknown RTLD bug
* other - unknown

All other platforms are untested.

A lot has happened over the spring/summer: amd64 got proper
mcmodel=kernel support, compiler-rt has been introduced (paving the way
for libgcc replacement), we have run two experimental port builds to
see how clang does there. The C++ support is able to parse devd.cc
without warnings. We have got the kernel working with -O2. FreeBSD has
been promoted to be an officially supported plaform in LLVM. As a
result of all this work, many parts of FreeBSD that did not compile
before now build without problems.

Open tasks:

1. The "ClangBSD" branch of FreeBSD got a little stale and has not
been updated for a while.
2. We also need to get some important fixes into LLVM to get libc
compiling and some other smaller issues.
3. We can still appreciate more testers on minor platforms (mostly on
ARM, PPC and MIPS, but testing on other platforms is also welcome).
__________________________________________________________________

Enhancing the FreeBSD TCP Implementation

URL: http://caia.swin.edu.au/freebsd/etcp09/
URL: http://caia.swin.edu.au/urp/newtcp/
URL: http://www.freebsdfoundation.org/projects.shtml
URL: http://people.freebsd.org/~lstewart/patches/tcp_ffcaia2008/

Contact: Lawrence Stewart <lstewart@...>

TCP appropriate byte counting (RFC 3465) support has been merged into
the FreeBSD 8 branch and will ship in FreeBSD 8.0-RELEASE.

The reassembly queue auto-tuning and SIFTR work was not ready in time
to safely integrate for 8.0-RELEASE. Padding has been added to
necessary TCP structs to facilitate MFCing features back to the
8-STABLE branch after 8.0 is released.

Candidate patches against FreeBSD-CURRENT will be ready for wider
testing in the coming weeks. The freebsd-net mailing list will be
solicited for testing/feedback when everything is ready.

Open tasks:

1. Solicit review/testing and integrate the ALQ kld and variable
length message support patch into FreeBSD-CURRENT.
2. Solicit review/testing and integrate the SIFTR tool into
FreeBSD-CURRENT.
3. Complete dynamic reassembly queue auto-tuning patch for
FreeBSD-CURRENT.
4. Fix an identified bug in the SACK implementation's fast
retransmit/fast recovery behavior.
5. Profit!
__________________________________________________________________

EuroBSDcon 2009

URL: http://2009.eurobsdcon.org/
URL: http://2010.eurobsdcon.org/

Contact: Sam Smith <eurobsdcon@...>
Contact: Robert Watson <rwatson@...>

EuroBSDcon 2009 happened in Cambridge, with over 160 users, developers,
friends and others. Slides, papers and audio are now up on the website
for those who could not make it to Cambridge. Next year's event in 2010
will take place in Karlsruhe from 8 to 10 October 2010. If you are
interested in what you missed in 2009, or to join the mailing list so
you do not miss out next year, visit http://2009.eurosbsdcon.org.
__________________________________________________________________

Ext2fs Status report (Summer of Code 2009)

URL: http://wiki.freebsd.org/SOC2009AdityaSarawgi

Contact: Aditya Sarawgi <sarawgi.aditya@...>

FreeBSD's ext2fs had some parts under GPL. The aim of my project was to
rewrite those parts and free ext2fs from GPL. I have been successful in
rewriting the parts and NetBSD's ext2fs was a great help in this.
Certain critical parts under GPL were also removed due to which the
write performance suffered. I also implemented Orlov Block Allocator
for ext2fs. Currently I am planning to make ext2fs Multiprocessor Safe
(MPSAFE). My work resides in truncs_ext2fs branch of Perforce.

Open tasks:

1. Ext4 support for FreeBSD
2. Directory indexing for ext2fs
3. Journaling in ext2fs using gjournal
__________________________________________________________________

FreeBSD Bugbusting Team

URL: http://www.FreeBSD.org/support.html#gnats
URL: http://wiki.FreeBSD.org/BugBusting
URL: http://people.FreeBSD.org/~linimon/studies/prs/
URL:
http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html

Contact: Gavin Atkinson <gavin@...>
Contact: Mark Linimon <linimon@...>
Contact: Remko Lodder <remko@...>
Contact: Volker Werth <vwe@...>

We continue to classify PRs as they arrive, adding 'tags' to the
subject lines corresponding to the kernel subsystem involved, or man
page references for userland PRs. These tags, in turn, produce lists of
PRs sorted both by tag and by manpage.

The list of PRs recommended for committer evaluation by the Bugbusting
Team continues to receive new additions. This list contains PRs, mostly
with patches, that the Bugbusting Team feel are probably ready to be
committed as-is, or are probably trivially resolved in the hands of a
committer with knowledge of the particular subsystem. All committers
are invited to take a look at this list whenever they have a spare 5
minutes and wish to close a PR.

A full list of all the automatically generated reports is also
available at one of the cited URLs. Any recommendations for reports
which not currently exist but which would be beneficial are welcomed.

Gavin Atkinson gave a presentation on "The PR Collection Status" at the
EuroBSDCon 2009 DevSummit, and discussed with other participants
several other ideas to make the PR database more useful and usable.
Several good ideas came from this, and will hopefully lead to more
useful tools in the near future. Discussions also took place on how it
may be possible to automatically classify non-ports PRs with a view
towards notifying interested parties, although investigations into this
have not yet begun.

Mark Linimon also continues attempting to define the general problem
and investigating possible new workflow models, and presented work on
this at BSDCan 2009.

Since the last status report, the number of open bugs has increased to
around the 5900 mark, partially because of an increased focus on
getting more information into the existing PRs, in an attempt to make
sure all the information required is now available. As a result,
although the number of open PRs has increased, they are hopefully of
better quality.

As always, more help is appreciated, and committers and non-committers
alike are always invited to join us on #freebsd-bugbusters on EFnet and
help close stale PRs or commit patches from valid PRs.

Open tasks:

1. Work on suggestions from developers who were at the EuroBSDCon
DevSummit.
2. Try to find ways to get more committers helping us with closing the
PRs that the team has already analyzed.
__________________________________________________________________

FreeBSD Developer Summit, Cambridge UK

URL: http://wiki.FreeBSD.org/200909DevSummit

Contact: Robert Watson <rwatson@...>

Around 70 FreeBSD developers and guests attended the FreeBSD developer
summit prior to EuroBSDCon 2009 in Cambridge, UK. Hosted at the
University of Cambridge Computer Laboratory, the workshop-style event
consisted of prepared presentations, as well as group hacking and
discussion sessions. Talks covered topics including 802.11 mesh
networking, virtual network stacks and kernels, a new BSD-licensed
debugger, benchmarking, bugbusting, NetFPGA, a port of Apple's GCD
(Grand Central Dispatch) to FreeBSD, security policy work,
cryptographic signatures, FreeBSD.org system administration, time
geeks, a new console driver, and the FreeBSD subversion migration.
Slides for many talks are now available on the wiki page. A good time
was had by all, including a punting outing on the River Cam!
__________________________________________________________________

FreeBSD Gecko Project

URL: https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO

Contact: Beat Gaetzi <beat@...>
Contact: Martin Wilke <miwi@...>
Contact: Andreas Tobler <andreast-list@...>

Andreas Tobler made the classic mistake of sending us a lot of powerpc
and sparc64 related patches. The usual punishment, of giving him a
commit bit to the Gecko repository, has been applied.

We currently have some old ports in the ports tree:
* www/mozilla is 5 year old now, no longer supported upstream, and
has a lot of security vulnerabilities. We can use www/seamonkey
instead.
* www/xulrunner is superseeded by www/libxul.

A patch that includes the following changes has been tested on
pointyhat and is ready for commit:
* Remove references to www/mozilla/Makefile.common and
www/mozilla/bsd.gecko.mk
* Switch USE_GECKO= xulrunner firefox mozilla to USE_GECKO= libxul
and remove www/xulrunner

We are also working on Firefox 3.6 (Alpha 2), Thunderbird 3.0 (Beta 4),
new libxul 1.9.1.3 and Seamonkey 2.0 (Beta 2) ports. All of them are
already committed to our Gecko repository.

A current status and todo list can be found at
http://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO.

Open tasks:

1. Remove mozilla, xulrunner and firefox2 from the ports tree.
2. The www/firefox35 port should be moved to www/firefox.
3. The old (and somewhat stale) Gecko providers mozilla, nvu,
xulrunner, flock and firefox also need to be removed.
__________________________________________________________________

FreeBSD KDE Team

URL: http://freebsd.kde.org
URL: http://miwi.bsdcrew.de/category/kde/
URL: http://blogs.freebsdish.org/tabthorpe/category/kde

Contact: Thomas Abthorpe <tabthorpe@...>
Contact: Max Brazhnikov <makc@...>
Contact: Martin Wilke <miwi@...>

Since the spring, the FreeBSD KDE team has been busy upgrading KDE from
4.2.0 up through to 4.3.1. As part of the ongoing maintenance of KDE,
the team also updated Qt4 from 4.4.3 through to 4.5.2

We added two new committers/maintainers to the team, Kris Moore
(kmoore@) and Dima Panov (fluffy@). We also granted enhanced area51
access to contributors Alberto Villa and Raphael Kubo da Costa. Alberto
has been our key contributor updating and testing Qt 4.6.0-tp1. Raphael
is a KDE developer, who has become our Gitorious liaison, he has been
responsible for getting FreeBSD Qt patches merged in upstream.

Markus Brüffer (markus@) spent a lot of time patching widgets and
system plugins so they would work under FreeBSD. We would like to thank
him for all his effort!

Open tasks:

1. Update to Qt 4.6.0
2. Update to KDE 4.4.0
3. Work with our userbase on fixing an EOL for KDE3 in the ports tree
__________________________________________________________________

FreeBSD Ports Management Team

URL: http://www.freebsd.org/ports/
URL:
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/
URL: http://portsmon.FreeBSD.org/index.html
URL: http://www.freebsd.org/portmgr/index.html
URL: http://tinderbox.marcuscom.com

Contact: Mark Linimon <linimon@...>

The ports count has soared to over 20,700. The PR count had been driven
below 800 by some extraordinary effort, but once again is back to its
usual count of around 900.

We are currently building packages for amd64-6, amd64-7, amd64-8,
i386-6, i386-7, i386-8, sparc64-7, and sparc64-8. There have been
preliminary runs of i386-9; however, to be able to continue builds on
-9, we will either need to find places to host a number of new
machines, or drop package building for -6. The mailing list discussion
of the latter proved quite controversial.

We have added some new i386 machines to help speed up the builds, but
this only makes up for the disk failures on some of our older, slower,
i386 nodes.

We also appreciate the loan of more package build machines from several
committers, including pgollucci@, gahr@, erwin@, Boris Kochergin, and
Craig Butler.

The portmgr@ team has also welcomed new members Ion-Mihai Tetcu
(itetcu@) and Martin Wilke (miwi@). We also thank departing member
Kirill Ponomarew (krion@) for his long service.

Ion-Mihai has spent much time working on a system that does automatic
Quality Assurance on new commits, called QAT. A second tinderbox called
QATty has helped us to fix many problems, especially those involving
custom PREFIX and LOCALBASE settings, and documentation inclusion
options. Ports conformance to documented features / non-default
configuration will follow.

Between pav and miwi, over 2 dozen experimental ports runs have been
completed and committed.

We have added 5 new committers since the last report, and 2 older ones
have rejoined.

Open tasks:

1. We are currently trying to set up ports tinderboxes that can be
made available to committers for pre-testing; those who can loan
machines for this should contact Ion-Mihai (itetcu@) with details
regarding the hardware and bandwidth.
2. Most of the remaining ports PRs are "existing port/PR assigned to
committer". Although the maintainer-timeout policy is helping to
keep the backlog down, we are going to need to do more to get the
ports in the shape they really need to be in.
3. Although we have added many maintainers, we still have almost 4,700
unmaintained ports (see, for instance, the list on portsmon). (The
percentage is down to 22%.) We are always looking for dedicated
volunteers to adopt at least a few unmaintained ports. As well, the
packages on amd64 and sparc64 lag behind i386, and we need more
testers for those.
__________________________________________________________________

FreeBSD TDM Framework

Contact: Rafal Czubak <rcz@...>
Contact: Michal Hajduk <mih@...>

This work's purpose is a generic and flexible framework for systems
equipped with Time Division Multiplexing (TDM) units, often found on
embedded telecom chips. The framework is designed to support various
controllers and many types of TDM channels e.g. voiceband, sound and
miscellaneous data channels. Currently, voiceband infrastructure is
being developed on Marvell RD-88F6281 reference board. It will serve as
an example of how to use the TDM framework for other channel types. The
direct objective of using TDM with voiceband channels is bringing a
FreeBSD based VoIP system, capable of bridging analog telephone world
with digital IP telephony. Together with third party VoIP software
(e.g. Asterisk), the design can serve as VoIP Private Branch Exchange
(PBX).

Current state highlights:
* TDM controller interface
* TDM channel interface
* TDM channel API for kernel modules
* codec interface
* voiceband channel character device driver
* TDM controller driver for Marvell Kirkwood and Discovery SoCs
* Si3215 SLIC driver
* Si3050 DAA driver

Open tasks:

1. Develop demo application showing example usage of voiceband
channel.
2. Integrate voiceband infrastructure with Zaptel/DAHDI telephony
hardware drivers.
__________________________________________________________________

FreeBSD/sparc64

Contact: Marius Strobl <marius@...>

Noteworthy developments regarding FreeBSD/sparc64 since the last Status
Reports are:
* Cas(4), a driver for Sun Cassini/Cassini+, as well as National
Semiconductor DP83065 Saturn Gigabit NICs has been committed and
thus will be part of FreeBSD beginning with 8.0-RELEASE and
7.3-RELEASE, respectively. This means that the on-board NICs found
in Fire V440, as well as the add-on cards based on these chips, are
now supported, including on non-sparc64 machines. Unfortunately,
the cas(4) driver triggers what seem to be secondary problems with
the on-board NICs found in B100 blades and Fire V480, which due to
lack of access to such systems could not be fixed so far.
* Initial support for sun4u machines based on the "Fire"
Host-PCI-Express bridge like Fire V215, V245, etc. has been
completed (including support for the on-board ATA controller, which
caused several problems at first, and MSI/MSI-X). Some code like
the quirk handling for the ALi/ULi chips found in these machines
needs to be revisited though and no stability tests have been
conducted so far. If all goes well, the code will hit HEAD some
time after FreeBSD 8.0-RELEASE has been released. In theory,
machines based on the "Oberon" Host-PCI-Express bridge, at least
for the most part, should also be supported with these changes, but
due to lack of access to a Mx000 series machine the code could not
be tested with these so far.
* Some bugs in the snd_t4dwave(4) driver have been fixed, as well as
some special handling for sparc64 has been added so it does 32-bit
DMA and now generally works with the on-board ALi M5451 found for
example in Blade 100 and Blade 1500. Unfortunately, it was only
tested to work correctly in two out of three Blade 100. Why it
still does not work correctly in the remaining one is currently
unknown but at least no longer causes IOMMU-panics so testing
snd_t4dwave(4) on sparc64 is no longer harmful. These changes will
be part of FreeBSD 8.0-RELEASE and 7.3-RELEASE.
* Ata-marvell(4) has been fixed to work on sparc64 (actually also on
anything that is not x86 with less than 4GB of RAM). These fixes
will be part of FreeBSD 8.0-RELEASE and 7.3-RELEASE.
* A proper and machine-independent fix for the old problem that the
loader leaves the NIC opened by the firmware, which could lead to
panics during boot when netbooting, has been developed but not
committed yet.

Open tasks:
__________________________________________________________________

FreeBSD/ZFS

Contact: Pawel Dawidek <pjd@...>

We believe that the ZFS file system is now production-ready in FreeBSD
8.0. Most (if not all) reported bugs were fixed and ZFS is no longer
tagged as experimental. There is also ongoing work in Perforce to bring
the latest ZFS version (v19) to FreeBSD.

Open tasks:

1. Download 8.0 release candidates and test, test, test and report any
problems to the freebsd-fs@... mailing list.
__________________________________________________________________

Grand Central Dispatch - FreeBSD port

URL: http://libdispatch.macosforge.org/

Contact: Robert Watson <rwatson@...>
Contact: Stacey Son <sson@...>
Contact: libdispatch mailing list
<libdispatch-dev@...>

We have ported libdispatch, Apple's Grand Central Dispatch event and
concurrency framework to FreeBSD:
* Added new kqueue primitives required to support GCD, such as
EVFILT_USER and EV_TRIGGER
* Created autoconf and automake build framework for libdispatch
* Modified libdispatch to use POSIX semaphores instead of Mach
semaphores
* Adapted libdispatch to use portable POSIX time routines

Jordan Hubbard has also prepared a blocks-aware clang compiler package
for FreeBSD. When compiled with clang, libdispatch provides
blocks-based, as well as function-based callbacks.

The port was presented at the FreeBSD Developer Summit in Cambridge, UK
in September, and slides are online on the devsummit wiki page. A
FreeBSD port is now available in the Ports Collection. After FreeBSD
8.0-RELEASE has shipped, the new kqueue primitives will be MFC'd so
that libdispatch works out of the box on FreeBSD 8.1-RELEASE.

Open tasks:

1. Complete porting of libdispatch test suite to FreeBSD.
2. Investigate pthread work queue implementation for FreeBSD.
3. Evaluate performance impact of some machine-dependent and
OS-dependent optimizations present in the Mac OS X version of
libdispatch to decide if they should be done for other platforms
and OS's.
4. Explore whether FreeBSD base operating system tools would benefit
from being modified to use libdispatch.
__________________________________________________________________

hwpmc for MIPS

URL: http://wiki.freebsd.org/FreeBSD/mips
URL: http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStationPro

Contact: George Neville-Neil <gnn@...>

Currently working on board bringup. I have looked over the docs for how
MIPS provides performance counters and will begin adding code soon.
__________________________________________________________________

libnetstat(3) - networking statistics (Summer of Code 2009)

URL: http://wiki.FreeBSD.org/PGJSoc2009
URL:
http://p4web.freebsd.org/@md=d&cd=//&c=McZ@//depot/projects/soc2009/pgj
_libstat/?ac=83

Contact: Gábor Páli <pgj@...>

The libnetstat(3) project provides a user-space library API to monitor
networking functions with the following benefits:
* ABI-robust interface making use of accessor functions in order to
divorce monitoring applications from kernel or user ABI changes.
* Supports running 32-bit monitoring tools on top of a 64-bit kernel.
* Improved consistency for both kvm(3) and sysctl(3) when retrieving
information.

The supported abstractions are as follows:
* Active sockets and socket buffers
* Network interfaces and multicast interfaces
* mbuf(9) statistics
* bpf(4) statistics
* Routing statistics, routing tables, multicast routing
* Protocol-dependent statistics

There is a sample application, called nettop(8), which provides a
simple ncurses-based top(1)-like interface for monitoring active
connections and network buffer allocations via the library. A modified
version of netstat(1) has also been created to use libnetstat(3) as
much as possible.
__________________________________________________________________

libprocstat(3) - process statistics

URL: http://svn.freebsd.org/viewvc/base/projects/libprocstat/

Contact: Stanislav Sedov <stas@...>
Contact: Ulf Lilleengen <lulf@...>

The libprocstat project is an ongoing effort to develop a library that
can be used to retrieve information about running processes and open
files in the uniform and platform-independent way both from a running
system or from core files. This will facilitate the implementation of
file- or process-monitoring applications like lsof(1), fstat(1), fuser,
etc. The libprocstat repository contains a preliminary version of the
library. It also includes rewrites of the fstat and the fuser utilities
ported to use this library instead of retrieving all the required
information via the kvm(3) interface; one of the important advantages
of the versions that use libprocstat is that these utilities are ABI
independent.

Open tasks:

1. Implement KVM-based namecache lookup to retrieve filesystem paths
associated with file descriptors and VM objects.
2. Analyze possible ways of exporting file and process information
from the kernel in an extensible and ABI-independent way.
__________________________________________________________________

Modular Congestion Control

URL: http://caia.swin.edu.au/urp/newtcp/
URL: http://svn.freebsd.org/viewvc/base/projects/tcp_cc_8.x/

Contact: Lawrence Stewart <lstewart@...>

The patch has received some significant rototilling in the past few
months to prepare it for merging to FreeBSD-CURRENT. Additionally, I
completed an implementation of the CUBIC congestion control algorithm
to complement the existing NewReno and H-TCP algorithm implementations
already available.

I have one further intrusive change to make, which will allow
congestion control modules to be shared between the TCP and SCTP
stacks. Once this is complete, I will be soliciting for review/testing
in the hope of committing the patch to FreeBSD-CURRENT in time to be
able to backport it for 8.1-RELEASE.

Open tasks:

1. Abstract the congestion control specific variables out of the TCP
and SCTP control blocks into a new struct that can be passed into
the API instead of the control block itself.
__________________________________________________________________

Network Stack Virtualization

URL: http://wiki.freebsd.org/Image
URL: http://wiki.freebsd.org/200909DevSummit

Contact: Bjoern A. Zeeb <bz@...>
Contact: Marko Zec <zec@...>
Contact: Robert Watson <rwatson@...>

The network stack virtualization project aims at extending the FreeBSD
kernel to maintain multiple independent instances of networking state.
This allows for networking independence between jail environment, each
maintaining its private network interfaces, IPv4 and IPv6 network and
port address space, routing tables, IPSec configuration, firewalls, and
more.

During the last months the remaining pieces of the VIMAGE work were
merged by Marko, Julian and Bjoern. Robert Watson developed a vnet
allocator to overcome ABI issues. Jamie Gritton merged his hierachical
jail framework that now also is the management interface for virtual
network stacks.

During the FreeBSD Developer Summit that took place at EuroBSDCon 2009
in Cambridge, UK, people virtualized more code. As a result SCTP and
another accept filter were virtualized and more people became familiar
with the design of VImage and the underlying concepts. Finally getting
more hands involved was a crucial first step for the long term success
of kernel virtualization.

The next steps will be to finish the network stack virtualization,
generalize the allocator framework before thinking of virtualizing
further subsystems and to update the related documentation. Along with
that a proper jail management framework will be worked on. Long term
goals, amongst others, will be to virtualize more subsystems like SYS-V
IPC, better privilege handling, and resource limits.

In the upcoming FreeBSD 8.0 Release, vnets are treated as an
experimental feature. As a result, they are not yet recommended for use
in production environments. There was lots of time spent to finalize
the infrastructure for vnets though, so that further changes can be
merged and we are aiming to have things production ready for 8.2.

In case you want to help to achieve this goal, feel free to contact us
and support or help virtualizing outstanding parts like two firewalls,
appletalk, netipx, ... as well as generating regression tests.
__________________________________________________________________

New approach to the locale database

URL: http://wiki.freebsd.org/LocaleNewApproach
URL: svn://svn.freebsd.org/base/user/edwin/locale

Contact: Edwin Groothuis <edwin@...>
Contact: i18n mailinglist <freebsd-i18n@...>

Problem: Over the years the FreeBSD locale database (share/colldef,
share/monetdef, share/msgdef, share/numericdef, share/timedef) has
accumulated a total of 165 definitions (language - country-code -
character-set triplets). The contents of the files for Western European
languages are often low-ASCII but for Eastern European and Asian
languages partly or fully high-ASCII. Without knowing how to display or
interpret the character-sets, it is difficult to make sure by the
general audience that the local language (language - country-code)
definitions are displayed properly in various character-sets.

Suggested approach: With the combination of the data in the Unicode
project (whose goal is to define all the possible written characters
and symbols on this planet) and the Common Locale Data Repository
(whose goal is to document all the different data and definitions
needed for the locale database), we can easily keep track of the data,
without the need of being able to display the data in the required
character sets or understand them fully when updates are submitted by
third parties.

Current status: Conversion of share/monetdef, share/msgdef,
share/numericdef, share/timedef to the new design is completed. The
Makefile infrastructure is converted. Regression checks are done. Most
of the tools are in place, waiting on the import of bsdiconv to the
base system.

Open tasks:

1. At this moment the system is not self-hosted yet, because of the
lack of an iconv-kind of program in the base operating system.
Gabor@ is working on bsdiconv as a GSoC project and once that has
been imported we will be able to perform a clean install from the
definitions in Unicode text format to the required formats and
character sets.
__________________________________________________________________

New BSD licensed debugger

URL: http://wiki.freebsd.org/TheBsdDebugger
URL: http://people.freebsd.org/~dfr/ngdb.git
URL:
http://wiki.freebsd.org/200909DevSummit?action=AttachFile&do=view&targe
t=NGDB-200909.pdf

Contact: Doug Rabson <>

I have been working recently on writing a new debugger, primarily for
the FreeBSD platform. For various reasons, I have been writing it in a
relatively obscure C-like language called D.

So far, I have a pretty useful (if a little raw at the edges) command
line debugger which supports ELF, Dwarf debugging information and
(currently) 32 bit FreeBSD and Linux. The engine includes parsing and
evaluation of arbitrary C expressions along with the usual debugging
tools such as breakpoints, source code listing, single-step etc. All
the code is new and BSD licensed. Currently, the thing supports
userland debugging of i386 targets via ptrace and post-mortem core file
debugging of the same. I will be adding amd64 support real soon (TM)
and maybe support for GDB's remote debugging protocol later.
__________________________________________________________________

NFSv4 ACLs

URL: http://wiki.freebsd.org/NFSv4_ACLs

Contact: Edward Tomasz Napierala <trasz@...>

During Google Summer of Code 2008, I have implemented native support
for NFSv4 ACLs for both ZFS and UFS. Most of the code has already been
merged to CURRENT. NFSv4 ACLs are unconditionally enabled in ZFS and
the usual tools, like getfacl(1) and setfacl(1) can be used to view and
change them. I plan to merge the remaining bits (UFS support) this
month. It should be possible to MFC it in order to ship in FreeBSD
8.1-RELEASE.

Open tasks:

1. UFS changes review
2. Support for NFSv4 ACLs in tar(1)
__________________________________________________________________

pefs - stacked cryptographic filesystem (Summer of Code 2009)

URL: http://blogs.freebsdish.org/gleb/
URL: http://wiki.freebsd.org/SOC2009GlebKurtsov

Contact: Gleb Kurtsou <gk@...>
Contact: Stanislav Sedov <stas@...>

Pefs is a kernel level filesystem for transparently encrypting files on
top of other filesystems (like zfs or ufs). It adds no extra
information into files (unlike others), doesn't require cipher block
sized io operations, supports per directory/file keys and key chaining,
uses unique per file tweak for encryption. Supported algorithms: AES,
Camellia, Salsa20. The code is ready for testing.

Open tasks:

1. Implement encrypted name lookup/readir cache
2. Optimize sparse files handling and file resizing
__________________________________________________________________

Portmaster - utility to assist users with managing ports

URL: http://dougbarton.us/portmaster.html

Contact: Doug Barton <dougb@...>

I am currently seeking funding for further development work on
portmaster. There are several features that are regularly requested by
the community (such as support for installing packages) that I would
very much like to implement but that will take more time than I can
reasonably volunteer to implement correctly. There is information about
the funding proposal available at the link above.

Meanwhile I have recently completed another round of bug fixes and
feature enhancements. The often-requested ability to specify the -x
(exclude) option more than once on the command line was added in
version 2.12. Also in that version I added the --list-origins option to
make it easier to reinstall ports after a major version upgrade, or
install the same set of ports on another system.

Open tasks:

1. See the funding proposal.
__________________________________________________________________

Release Engineering Status Report

URL: http://www.FreeBSD.org/releng/

Contact: Release Engineering Team <re@...>

The Release Engineering Team continues to work on FreeBSD 8.0-RELEASE.
Public testing has turned up quite a few problems, many related to the
low-level network (routing/ARP table) changes and their interactions
with IPv6.

Progress continues to be made on fixing up the issues that have been
identified during the public testing. At this point in time we are
shooting for two more public test builds (RC2 and RC3) followed by the
release late October or early November.
__________________________________________________________________

Stream Control Transmission Protocol (SCTP)

Contact: Randall Stewart <rrs@FreeBSD>

SCTP continues to have minor fixes added to it as well as some new
features. First and foremost, we now have VIMAGE and SCTP working and
playing together. This goal was accomplished with the help of bz@, my
new mentee tuexen@ and myself working together at the FreeBSD DevSummit
in Cambridge, UK. Also the non-renegable SACK feature contributed by
the university of Delaware was fixed so that now its safe to turn on
(its sysctl). If you are using SCTP with CMT (Conncurrent Multipath
Transfer) you will want to enable this option (CMT is also a sysctl).
With CMT enabled you will be able to send data to all the destinations
of an SCTP peer.

We welcomed a new mentee (soon to be a commiter) to FreeBSD. Michael
Tuexen is now a mentee of rrs@. Michael has been contributing to the
SCTP work for quite some time and also moonlights as a Professor at the
University of Muenster in Germany (when not doing SCTP coding).
__________________________________________________________________

The FreeBSD Dutch Documentation Project

URL: http://www.freebsd.org/docproj/translations.html#dutch

Contact: René Ladan <rene@...>
Contact: Remko Lodder <remko@...>

The current translations (Handbook and some articles) are kept up to
date with the English versions. Some parts of the website have been
translated, more work is in progress.

Open tasks:

1. Find more volunteers for translating the remaining parts of the
website and the FAQ.
__________________________________________________________________

The FreeBSD Forums

URL: http://forums.freebsd.org/

Contact: FreeBSD Forums Admins <forum-admins@...>
Contact: FreeBSD Forums Moderators <forum-moderators@...>

Since their public launch in November 2008, the FreeBSD Forums (the
most recent addition to the user community and support channels for the
FreeBSD Operating System) have witnessed a healthy and steady growth.

The user population is now at over 8,000 registered users, who have
participated in over 6,000 topics, containing over 40,000 posts in
total. The sign-up rate hovers between 50-100 each week. The total
number of visitors (including 'guests') is hard to gauge but is likely
to be a substantial multiple of the registered userbase.

New topics and posts are actively 'pushed out' to search engines. This
in turn makes the Forums show up in search results more and more often,
making it a valuable and very accessible source of information for the
FreeBSD community.

One of the contributing factors to the Forums' success is their
'BSD-style' approach when it comes to administration and moderation.
The Forums have a strong and unified identity, they are neatly divided
into sub-forums (like 'Networking', 'Installing & Upgrading', etc.),
very actively moderated, spam-free, and with a core group of very
active and helpful members, dispensing many combined decades' worth of
knowledge to starting, intermediate and professional users of FreeBSD.

We expect the Forums to be, and to remain, a central hub in FreeBSD's
community and support efforts.
__________________________________________________________________

The FreeBSD Foundation Status Report

URL: http://www.freebsdfoundation.org

Contact: Deb Goodkin <deb@...>

Kicking off our fall fund-raising campaign! Find out more at
http://www.freebsdfoundation.org/donate/.

We were a sponsor for EuroBSDCon 2009, and provided travel grants to 8
FreeBSD developers and users. We sponsored Kyiv BSD 2009, in Kiev
Ukraine. We were also a sponsor of BSDCan, and sponsored 7 developers.
We funded three new projects, New Console Driver by Ed Schouten, AVR32
Support by Arnar Mar Sig, and Wireless Mesh Support by Rui Paulo, which
has completed. We continued funding a project that is making
improvements to the FreeBSD TCP Stack by Lawrence Stewart. The project
that made removing disk devices with mounted filesystems on them safe,
by Edward Napierala, is now complete.

We recognized the following FreeBSD developers at EuroBSDCon 2009:
Poul-Henning Kamp, Bjoern Zeeb, and Simon Nielsen. These developers
received limited edition FreeBSD Foundation vests.

Follow us on Twitter now!
__________________________________________________________________

The FreeBSD German Documentation Project

URL: https://doc.bsdgroup.de
URL: http://code.google.com/p/bsdcg-trans/wiki/BSDPJTAdede

Contact: Johann Kois <jkois@...>
Contact: Benedict Reuschling <bcr@...>
Contact: Martin Wilke <miwi@...>

In May 2009, Benedict Reuschling received his commit bit to the www/de
and doc/de_DE.ISO8859-1 trees under the mentorship of Johann Kois.
Since then, he has been working primarily on the Handbook, updating
existing chapters and translating new ones. Most notably, the
filesystems and DTrace chapters have been recently translated. Bugs
found in the original documents along the way were reported back so
that the other translation teams could incorporate them, as well.

Christoph Sold has put his time in translating the wiki pages of the
BSD Certification Group into the German language. This is very helpful
for all German people who want to take the exam and like to read the
information about it in their native language. Daniel Seuffert has sent
valuable corrections and bugfixes. Thanks to both of them for their
time and efforts!

The website is translated and updated constantly. Missing parts will be
translated as time permits.

We appreciate any help from volunteers in proofreading documents,
translating new ones and keeping them up to date. Even small error
reports are of great help for us. You can find contact information at
the above URL.

Open tasks:

1. Update the existing documentation set (especially the Handbook).
2. Translate more articles to German.
3. Read the translations. Check for problems and mistakes. Send
feedback.
__________________________________________________________________

The FreeBSD Hungarian Documentation Project

URL: http://www.FreeBSD.org/hu
URL: http://www.FreeBSD.org/doc/hu
URL: http://wiki.FreeBSD.org/HungarianDocumentationProject
URL:
http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//
depot/projects/docproj_hu/?ac=83

Contact: Gábor Kövesdán <gabor@...>
Contact: Gábor Páli <pgj@...>

In the last months, we have not added new translations, although we
have been working on the existing ones to have them updated. We need
more translators and volunteers to keep the amount of the translated
documentation growing, so feel free to contribute. Every line of
submission or feedback is appreciated and highly welcome.

If you want to join our work, please read the introduction to the
project as well as the FDP Primer (both of them are available in
Hungarian).

Open tasks:

1. Translate news entries, press releases
2. Translate Release Notes for -CURRENT and 8.X
3. Translate articles
4. Translate web pages
5. Read the translations, send feedback
__________________________________________________________________

The FreeBSD Spanish Documentation Project

URL: http://www.FreeBSD.org/es
URL: http://www.FreeBSD.org/doc/es
URL: http://www.freebsd.org/doc/es/articles/fdp-es/

Contact: José Vicente Carrasco Vayá <carvay@...>
Contact: Gábor Kövesdán <gabor@...>

Recently, we have added one new article translation. The existing
translations have not been updated, though. We need more human
resources to keep up with the work and keep the translations
up-to-date.

Open tasks:

1. Update the Handbook translation
2. Update the web page translation
__________________________________________________________________

The Newcons project

URL: http://wiki.FreeBSD.org/Newcons
URL: http://people.freebsd.org/~ed/newcons/patches/

Contact: Ed Schouten <ed@...>

Some time ago I started writing a new driver for the FreeBSD kernel
called vt(4), which is basically a replacement of syscons. There is
still a lot of work that needs to be done but it is probably useful to
mention what it does (and what does not).

Right now there are just two graphics drivers for vt(4), namely a VGA
driver for i386 and amd64 and a Microsoft Xbox graphics driver (because
it was so easy to implement). I still have to figure out what I am
going to do with VESA, because maybe it is better to just ignore VESA
and figure out how hard it is to extend DRM to interact with vt(4).

Some random features: it already supports both Unicode (UTF-8) input
and output, it is MPSAFE and supports per-window graphical fonts of
variable dimensions, containing an almost infinite amount of glyphs
(both bold and regular).

Open tasks:

1. Research needs to be done on DRM's codebase.
2. Syscons should already be migrated to TERM=xterm to make switching
between drivers a bit easier.
__________________________________________________________________

Valgrind suite on FreeBSD

URL: http://wiki.freebsd.org/Valgrind

Contact: Stanislav Sedov <stas@...>

The Valgrind suite in the FreeBSD ports collection has been updated to
version 3.5.0 (the latest available version). Most of the issues of the
previous version should be resolved now: we expect memcheck, callgrind
and cachegrind to be fully functional on both i386 and amd64 platforms
as well as for i386 binaries running on amd64 system. DRD/hellgrind
should work too, though they generate a lot of false-positives for now,
so their output is a bit messy.

Open tasks:

1. Port exp-ptrcheck valgrind tool and fix outstanding issues that
show up in memcheck/helgrind/DRD in the Valgrind regression tests
suite.
2. More testing (please, help).
3. Integrate our patches upstream.
__________________________________________________________________

VirtualBox on FreeBSD

URL: http://wiki.freebsd.org/VirtualBox

Contact: Beat Gaetzi <beat@...>
Contact: Bernhard Froehlich <decke@...>
Contact: Dennis Herrmann <dhn@...>
Contact: Juergen Lock <nox@...>
Contact: Martin Wilke <miwi@...>

VirtualBox has been committed to the Ports tree and synchronized with
the latest trunk version from Sun. Several known problems are already
fixed and some new features have been added:
* VT-x support
* Bridging support (Big Thanks to Fredrik Lindberg)
* Host Serial Support
* ACPI Support
* Host DVD/CD access
* SMP Support

We would like to say thanks to all the people who helped us by
reporting bugs and submitting fixes. We also thank the VirtualBox
developers for their help with the ongoing effort to port VirtualBox on
FreeBSD.

_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Errata Notice FreeBSD-EN-09:05.null

2009-10-02T13:12:55Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-EN-09:05.null Errata Notice
The FreeBSD Project

Topic: No zero mapping feature

Category: core
Module: kern
Announced: 2009-10-02
Credits: John Baldwin, Konstantin Belousov, Alan Cox, and Bjoern Zeeb
Affects: All supported versions of FreeBSD.
Corrected: 2009-10-02 18:09:56 UTC (RELENG_8, 8.0-RC2)
2009-10-02 18:09:56 UTC (RELENG_7, 7.2-STABLE)
2009-10-02 18:09:56 UTC (RELENG_7_2, 7.2-RELEASE-p4)
2009-10-02 18:09:56 UTC (RELENG_7_1, 7.1-RELEASE-p8)
2009-10-02 18:09:56 UTC (RELENG_6, 6.4-STABLE)
2009-10-02 18:09:56 UTC (RELENG_6_4, 6.4-RELEASE-p7)
2009-10-02 18:09:56 UTC (RELENG_6_3, 6.3-RELEASE-p13)

For general information regarding FreeBSD Errata Notices and Security
Advisories, including descriptions of the fields above, security
branches, and the following sections, please visit
<URL:http://security.freebsd.org/>.

I. Background

In the C programming language, address 0 (NULL) is used to represent
unallocated memory. NULL pointer dereferences are a common class of C
programming bug in which pointers are not properly checked for NULL
before being used. Dereferencing a NULL pointer normally terminates
execution, via a segmentation fault for user processes, or a page
fault panic in the kernel.

II. Problem Description

On most architectures, the FreeBSD kernel splits the process virtual
memory address space into two portions: user and kernel. This
improves system call performance by avoiding a full address space
switch when a process enters the kernel, and improves performance for
kernel access to user memory.

However, in this design, address 0 is part of the user-controlled
portion of the virtual address space. If the kernel dereferences a
NULL pointer due to a kernel bug, a malicious process that has mapped
code or data at address 0 may be able to manipulate kernel behavior.
For example, if a malicious user process maps code at address 0 and
then triggers a kernel bug in which a NULL function pointer is
invoked, the kernel may execute that code with kernel privilege rather
than panicking.

III. Impact

This errata patch introduces a mitigation feature in which user
mapping at address 0 is disallowed, limiting the attacker's ability to
convert a kernel NULL pointer dereference into a privilege escalation
attack.

The feature is disabled by default in FreeBSD 7 and lower, and must be
enabled by setting the sysctl(8) variable security.bsd.map_at_zero to
0. In FreeBSD 8 and later feature is enabled by default.

While extremely rare, certain applications may rely on mapping memory
at address 0. Careful testing is advised when enabling this feature
when using virtual machines, emulation technologies, and older a.out
format binaries.

Changing the mentioned sysctl(8) variable only affects processes
started after the sysctl(8) variable was set. Processes started
before the sysctl(8) variable was changed will continue to run with
the setting of the sysctl(8) variable which existed when the processes
was started.

Consequently, to ensure that the sysctl(8) variable affects all
processes, a reboot is required with the sysctl(8) variable configured
as mentioned below.

IV. Workaround

No workaround is available.

V. Solution

Perform one of the following:

1) Upgrade your system to 6-STABLE, 7-STABLE, or 8-RC, or to the
RELENG_7_2, RELENG_7_1, RELENG_6_4, or RELENG_6_3 security branch
dated after the correction date.

Enable feature as mentioned below.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 6.3, 6.4,
7.1, and 7.2 systems.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

[FreeBSD 7.x]
# fetch http://security.FreeBSD.org/patches/EN-09:05/null.patch
# fetch http://security.FreeBSD.org/patches/EN-09:05/null.patch.asc

[FreeBSD 6.x]
# fetch http://security.FreeBSD.org/patches/EN-09:05/null6.patch
# fetch http://security.FreeBSD.org/patches/EN-09:05/null6.patch.asc

NOTE WELL: The patch for FreeBSD 7.x can be used on FreeBSD 8, but
does not enable the feature by default!

b) Apply the patch.

# cd /usr/src
# patch < /path/to/patch

c) Recompile your kernel as described in
<URL:http://www.FreeBSD.org/handbook/kernelconfig.html> and reboot the
system.

To actually enable the feature in FreeBSD 6.x and 7.x, add the
following to either /boot/loader.conf or /etc/sysctl.conf:

security.bsd.map_at_zero="0"

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_6
src/sys/kern/kern_exec.c 1.275.2.9
RELENG_6_4
src/UPDATING 1.416.2.40.2.11
src/sys/conf/newvers.sh 1.69.2.18.2.13
src/sys/kern/kern_exec.c 1.275.2.8.4.2
RELENG_6_3
src/UPDATING 1.416.2.37.2.18
src/sys/conf/newvers.sh 1.69.2.15.2.17
src/sys/kern/kern_exec.c 1.275.2.8.2.1
RELENG_7
src/sys/kern/kern_exec.c 1.308.2.11
RELENG_7_2
src/UPDATING 1.507.2.23.2.7
src/sys/conf/newvers.sh 1.72.2.11.2.8
src/sys/kern/kern_exec.c 1.308.2.8.2.2
RELENG_7_1
src/UPDATING 1.507.2.13.2.11
src/sys/conf/newvers.sh 1.72.2.9.2.12
src/sys/kern/kern_exec.c 1.308.2.6.2.2
RELENG_8
src/sys/kern/kern_exec.c 1.337.2.3
src/sys/kern/init_main.c 1.303.2.2
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/6/ r197715
releng/6.4/ r197715
releng/6.3/ r197715
stable/7/ r197715
releng/7.2/ r197715
releng/7.1/ r197715
stable/8/ r197714
- -------------------------------------------------------------------------

VII. References

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-EN-09:05.null.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iD8DBQFKxltpFdaIBMps37IRAoniAJ9ENWQ431doaje7gXrAfAov5l0FKwCdFRxh
rTmlD1oew/hZTMBuFKM/LSI=
=+ZZf
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Security Advisory FreeBSD-SA-09:14.devfs

2009-10-02T13:12:04Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-SA-09:14.devfs Security Advisory
The FreeBSD Project

Topic: Devfs / VFS NULL pointer race condition

Category: core
Module: kern
Announced: 2009-10-02
Credits: Przemyslaw Frasunek
Affects: FreeBSD 6.x and 7.x
Corrected: 2009-05-18 10:41:59 UTC (RELENG_7, 7.2-STABLE)
2009-10-02 18:09:56 UTC (RELENG_7_2, 7.2-RELEASE-p4)
2009-10-02 18:09:56 UTC (RELENG_7_1, 7.1-RELEASE-p8)
2009-10-02 18:09:56 UTC (RELENG_6, 6.4-STABLE)
2009-10-02 18:09:56 UTC (RELENG_6_4, 6.4-RELEASE-p7)
2009-10-02 18:09:56 UTC (RELENG_6_3, 6.3-RELEASE-p13)

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

I. Background

The device file system (devfs) provides access to system devices, such as
storage devices and serial ports, via the file system namespace.

VFS is the Virtual File System, which abstracts file system operations in
the kernel from the actual underlying file system.

II. Problem Description

Due to the interaction between devfs and VFS, a race condition exists
where the kernel might dereference a NULL pointer.

III. Impact

Successful exploitation of the race condition can lead to local kernel
privilege escalation, kernel data corruption and/or crash.

To exploit this vulnerability, an attacker must be able to run code with user
privileges on the target system.

IV. Workaround

An errata note, FreeBSD-EN-09:05.null has been released simultaneously to
this advisory, and contains a kernel patch implementing a workaround for a
more broad class of vulnerabilities. However, prior to those changes, no
workaround is available.

V. Solution

Perform one of the following:

1) Upgrade your vulnerable system to 6-STABLE, or 7-STABLE, or to the
RELENG_7_2, RELENG_7_1, RELENG_6_4, or RELENG_6_3 security branch
dated after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 6.3, 6.4,
7.1, and 7.2 systems.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

[FreeBSD 6.x]
# fetch http://security.FreeBSD.org/patches/SA-09:14/devfs6.patch
# fetch http://security.FreeBSD.org/patches/SA-09:14/devfs6.patch.asc

[FreeBSD 7.x]
# fetch http://security.FreeBSD.org/patches/SA-09:14/devfs7.patch
# fetch http://security.FreeBSD.org/patches/SA-09:14/devfs7.patch.asc

b) Apply the patch.

# cd /usr/src
# patch < /path/to/patch

c) Recompile your kernel as described in
<URL:http://www.FreeBSD.org/handbook/kernelconfig.html> and reboot the
system.

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_6
src/sys/fs/devfs/devfs_vnops.c 1.114.2.17
RELENG_6_4
src/UPDATING 1.416.2.40.2.11
src/sys/conf/newvers.sh 1.69.2.18.2.13
src/sys/fs/devfs/devfs_vnops.c 1.114.2.16.2.2
RELENG_6_3
src/UPDATING 1.416.2.37.2.18
src/sys/conf/newvers.sh 1.69.2.15.2.17
src/sys/fs/devfs/devfs_vnops.c 1.114.2.15.2.1
RELENG_7
src/sys/fs/devfs/devfs_vnops.c 1.149.2.9
RELENG_7_2
src/UPDATING 1.507.2.23.2.7
src/sys/conf/newvers.sh 1.72.2.11.2.8
src/sys/fs/devfs/devfs_vnops.c 1.149.2.8.2.2
RELENG_7_1
src/UPDATING 1.507.2.13.2.11
src/sys/conf/newvers.sh 1.72.2.9.2.12
src/sys/fs/devfs/devfs_vnops.c 1.149.2.4.2.2
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/6/ r197715
releng/6.4/ r197715
releng/6.3/ r197715
stable/7/ r192301
releng/7.2/ r197715
releng/7.1/ r197715
- -------------------------------------------------------------------------

VII. References

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-SA-09:14.devfs.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iD8DBQFKxltlFdaIBMps37IRAp4zAJwJEwIySGqxH4EXwc0wjkDXlcTb1wCfTltO
Syds53GSM0YbsMNUVMGsLaU=
=exPZ
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Security Advisory FreeBSD-SA-09:13.pipe

2009-10-02T13:11:56Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-SA-09:13.pipe Security Advisory
The FreeBSD Project

Topic: kqueue pipe race conditions
Category: core
Module: kern
Announced: 2009-10-02
Credits: Przemyslaw Frasunek
Affects: FreeBSD 6.x
Corrected: 2009-10-02 18:09:56 UTC (RELENG_6, 6.4-STABLE)
2009-10-02 18:09:56 UTC (RELENG_6_4, 6.4-RELEASE-p7)
2009-10-02 18:09:56 UTC (RELENG_6_3, 6.3-RELEASE-p13)

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

I. Background

Pipes are a form of inter-process communication (IPC) provided by the
FreeBSD kernel. kqueue is an event management API that applications can
use to monitor pipes and other kernel services.

II. Problem Description

A race condition exists in the pipe close() code relating to kqueues,
causing use-after-free for kernel memory, which may lead to an
exploitable NULL pointer vulnerability in the kernel, kernel memory
corruption, and other unpredictable results.

III. Impact

Successful exploitation of the race condition can lead to local kernel
privilege escalation, kernel data corruption and/or crash.

To exploit this vulnerability, an attacker must be able to run code on
the target system.

IV. Workaround

An errata notice, FreeBSD-EN-09:05.null has been released simultaneously to
this advisory, and contains a kernel patch implementing a workaround for a
more broad class of vulnerabilities. However, prior to those changes, no
workaround is available.

V. Solution

Perform one of the following:

1) Upgrade your vulnerable system to 6-STABLE, or to the RELENG_6_4, or
RELENG_6_3 security branch dated after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 6.3 and 6.4.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/SA-09:13/pipe.patch
# fetch http://security.FreeBSD.org/patches/SA-09:13/pipe.patch.asc

b) Apply the patch.

# cd /usr/src
# patch < /path/to/patch

c) Recompile your kernel as described in
<URL:http://www.FreeBSD.org/handbook/kernelconfig.html> and reboot the
system.

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_6
src/sys/kern/kern_event.c 1.93.2.7
src/sys/kern/kern_fork.c 1.252.2.8
src/sys/kern/sys_pipe.c 1.184.2.6
src/sys/sys/event.h 1.32.2.1
src/sys/sys/pipe.h 1.29.2.1
RELENG_6_4
src/UPDATING 1.416.2.40.2.11
src/sys/conf/newvers.sh 1.69.2.18.2.13
src/sys/kern/kern_event.c 1.93.2.6.6.2
src/sys/kern/kern_fork.c 1.252.2.7.4.2
src/sys/kern/sys_pipe.c 1.184.2.4.2.3
src/sys/sys/event.h 1.32.12.2
src/sys/sys/pipe.h 1.29.16.2
RELENG_6_3
src/UPDATING 1.416.2.37.2.18
src/sys/conf/newvers.sh 1.69.2.15.2.17
src/sys/kern/kern_event.c 1.93.2.6.4.1
src/sys/kern/kern_fork.c 1.252.2.7.2.1
src/sys/kern/sys_pipe.c 1.184.2.2.6.3
src/sys/sys/event.h 1.32.10.1
src/sys/sys/pipe.h 1.29.12.1
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/6/ r197715
releng/6.4/ r197715
releng/6.3/ r197715
- -------------------------------------------------------------------------

VII. References

http://svn.freebsd.org/viewvc/base?view=revision&revision=179243

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-SA-09:13.pipe.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iD8DBQFKxlthFdaIBMps37IRAlk2AJ9mUrNPd1RMztbzO4w7g+AxosqJzgCgmr5l
FKxrbF0G4v9P6SyyfAdVOFY=
=TWhC
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

European BSD conference - 2009 in Cambridge - early bird registration still open

2009-08-27T03:44:18Z

Dear all:

I hope to welcome you to Cambridge, UK this September for EuroBSDCon 2009!
We have an exciting set of talks and tutorials, and will be announcing further
invited talks over the next few weeks. Early bird registration remains open
until 2 September. See you here!

Robert Watson
FreeBSD Project

EuroBSDcon 2009
Friday 18th - Sunday 20th September,
University of Cambridge, UK

A day of tutorials followed by 2 days of conference talks
covering a wide variety of BSD related topics. This is the
European BSD Community's annual event to meet, share and
interact across the projects and between friends.

Covering areas from networking to security, big systems
and complex environments, ports to LVM, geom and kqueue,
this year's line up also features:
* ISC and *BSD
* OpenBSD malloc
* Kirk McKusick's FreeBSD 8.0
* NetBSD's LVM
* faster packets in OpenBSD
* How FreeBSD finds oil
* Wireless Mesh networks
* and more,

The current talk list and draft schedule: http://2009.euroBSDcon.org
Final talks will be announced by early September.

The conference dinner takes place on Saturday evening and is
sponsored by iXsystems. Thanks to conference sponsors The
FreeBSD Foundation, iXsystems, Google, NetApp &, Exonetric.

Discounted Early Bird registration runs until 2nd
September. Book your place now at:
http://2009.euroBSDcon.org

Final programme may be subject to alteration. EuroBSDcon
is a not-for-profit event open to everyone so please help
spread the word online and offline. Thanks for reading!

If you're interested enough to read this far, you can sign up for
future announcements about EuroBSDcons by sending an email to
eurobsdcon-announce-subscribe@... . Your address
will only be used to contact you about European BSD events.

EuroBSDcon 2009 : September 18-20th, Cambridge, England.

Book your tickets here:
http://www.ukuug.org/events/eurobsdcon2009/
o-
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

Deadline soon for Travel Grant Applications for EuroBSDCon 2009

2009-08-18T11:47:20Z

Dear FreeBSD Community,

Just a reminder that our application deadline is August 20. If you are
interested in a travel grant for attending EuroBSDCon 2009, please
submit your application by this date.

Thank you to everyone who has already submitted an application. You
should be hearing from us soon.

Sincerely,

Deb Goodkin
The FreeBSD Foundation

-------- Original Message --------
Subject: Accepting Travel Grant Applications for EuroBSDCon 2009
Date: Mon, 20 Jul 2009 13:30:58 -0600
From: Deb Goodkin <deb@...>
To: freebsd-announce@...

Calling all FreeBSD developers needing assistance with travel expenses
to EuroBSDCon 2009.

The FreeBSD Foundation will be providing a limited number of travel
grants to individuals requesting assistance. Please fill out and submit
the Travel Grant Request Application at
http://www.freebsdfoundation.org/documents/TravelRequestForm.pdf by
August 20, 2009 to apply for this grant.

How it works:

This program is open to FreeBSD developers of all sorts (kernel hackers,
documentation authors, bugbusters, system administrators, etc). In some
cases we are also able to fund non-developers, such as active community
members and FreeBSD advocates.

(1) You request funding based on a realistic and economical estimate of
travel costs (economy airfare, trainfare, ...), accommodations
(conference hotel and sharing a room), and registration or tutorial
fees. If there are other sponsors willing to cover costs, such as your
employer or the conference, we prefer you talk to them first, as our
budget is limited. We are happy to split costs with you or another
sponsor, such as just covering airfare or board.

If you are a speaker at the conference, we expect the conference to
cover your travel costs, and will most likely not approve your direct
request to us.

(2) We review your application and if approved, authorize you to seek
reimbursement up to a limit. We consider several factors, including our
overall and per-event budgets, and (quite importantly) the benefit to
the community by funding your travel.

Most rejected applications are rejected because of an over-all limit on
travel budget for the event or year, due to unrealistic or uneconomical
costing, or because there is an unclear or unconvincing argument that
funding the application will directly benefit the FreeBSD Project.
Please take these points into consideration when writing your application.

(3) We reimburse costs based on actuals (receipts), and by check or bank
transfer. We require you submit a report on your trip, which we may
show to current or potential sponsors, and may include in our quarterly
newsletter.

There's some flexibility in the mechanism, so talk to us if something
about the model doesn't quite work for you or if you have any questions.
The travel grant program is one of the most effective ways we can
spend money to help support the FreeBSD Project, as it helps developers
get together in the same place at the same time, and helps advertise and
advocate FreeBSD in the larger community.

Thank You,

The FreeBSD Foundation

_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

Be Counted!

2009-07-30T09:52:45Z

Dear FreeBSD Community,

Millions of systems run FreeBSD. Hundreds of volunteers contribute to
FreeBSD's success. But what is the size of FreeBSD's user base? This
simple question is very hard to answer, but its answer is vital to the
cause of promoting FreeBSD. It is extremely difficult to convince
businesses to invest time and money to add FreeBSD support to their
products based solely on vague estimates of the size of our community.
We should know - working to make FreeBSD a more widely supported
platform is a task the FreeBSD Foundation has worked on since its inception.

Please help us in our fight to promote FreeBSD. A donation to the
FreeBSD Foundation helps fund our work, but it also gives us strength
in numbers. Our count of unique donors is a vital indication of the
size and buying power of our community. However, we have never broken
even one thousand donors in any year. We know in our hearts that this
is a small fraction of our user base and of those who want to help
expand FreeBSD's presence.

So stand up and be counted! Make a donation. Encourage other FreeBSD
users to donate as well. No donation amount is too large or too small.
Just by becoming a donor you are making a powerful statement about the
strength of FreeBSD!

You can make a donation by going to:
http://www.freebsdfoundation.org/donate/.

To find out more about The FreeBSD Foundation, please visit
http://www.freebsdfoundation.org.

Thank You,

Justin T. Gibbs
President and Founder
The FreeBSD Foundation
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Security Advisory FreeBSD-SA-09:12.bind

2009-07-28T17:48:35Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-SA-09:12.bind Security Advisory
The FreeBSD Project

Topic: BIND named(8) dynamic update message remote DoS

Category: contrib
Module: bind
Announced: 2009-07-29
Credits: Matthias Urlichs
Affects: All supported versions of FreeBSD
Corrected: 2009-07-28 23:59:22 UTC (RELENG_7, 7.2-STABLE)
2009-07-29 00:14:14 UTC (RELENG_7_2, 7.2-RELEASE-p3)
2009-07-29 00:14:14 UTC (RELENG_7_1, 7.1-RELEASE-p7)
2009-07-29 00:13:47 UTC (RELENG_6, 6.4-STABLE)
2009-07-29 00:14:14 UTC (RELENG_6_4, 6.4-RELEASE-p6)
2009-07-29 00:14:14 UTC (RELENG_6_3, 6.3-RELEASE-p12)
CVE Name: CVE-2009-0696

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

NOTE: Due to this issue being accidentally disclosed early, updated
binaries are yet not available via freebsd-update at the time this
advisory is being published. Email will be sent to the freebsd-security
mailing list when the binaries are available via freebsd-update.

I. Background

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

Dynamic update messages may be used to update records in a master zone
on a nameserver.

II. Problem Description

When named(8) receives a specially crafted dynamic update message an
internal assertion check is triggered which causes named(8) to exit.

To trigger the problem, the dynamic update message must contains a
record of type "ANY" and at least one resource record set (RRset) for
this fully qualified domain name (FQDN) must exist on the server.

III. Impact

An attacker which can send DNS requests to a nameserver can cause it to
exit, thus creating a Denial of Service situation.

IV. Workaround

No generally applicable workaround is available, but some firewalls
may be able to prevent nsupdate DNS packets from reaching the
nameserver.

NOTE WELL: Merely configuring named(8) to ignore dynamic updates is NOT
sufficient to protect it from this vulnerability.

V. Solution

Perform one of the following:

1) Upgrade your vulnerable system to 6-STABLE, or 7-STABLE, or to the
RELENG_7_2, RELENG_7_1, RELENG_6_4, or RELENG_6_3 security branch
dated after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 6.3, 6.4,
7.1, and 7.2 systems.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/SA-09:12/bind.patch
# fetch http://security.FreeBSD.org/patches/SA-09:12/bind.patch.asc

b) Execute the following commands as root:

# cd /usr/src
# patch < /path/to/patch
# cd /usr/src/lib/bind
# make obj && make depend && make && make install
# cd /usr/src/usr.sbin/named
# make obj && make depend && make && make install
# /etc/rc.d/named restart

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_6
src/contrib/bind9/bin/named/update.c 1.1.1.2.2.5
RELENG_6_4
src/UPDATING 1.416.2.40.2.10
src/sys/conf/newvers.sh 1.69.2.18.2.12
src/contrib/bind9/bin/named/update.c 1.1.1.2.2.3.2.1
RELENG_6_3
src/UPDATING 1.416.2.37.2.17
src/sys/conf/newvers.sh 1.69.2.15.2.16
src/contrib/bind9/bin/named/update.c 1.1.1.2.2.2.2.1
RELENG_7
src/contrib/bind9/bin/named/update.c 1.1.1.5.2.3
RELENG_7_2
src/UPDATING 1.507.2.23.2.6
src/sys/conf/newvers.sh 1.72.2.11.2.7
src/contrib/bind9/bin/named/update.c 1.1.1.5.2.2.2.1
RELENG_7_1
src/UPDATING 1.507.2.13.2.10
src/sys/conf/newvers.sh 1.72.2.9.2.11
src/contrib/bind9/bin/named/update.c 1.1.1.5.2.1.4.1
HEAD
src/contrib/bind9/bin/named/update.c 1.4
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
head/ r195936
stable/6/ r195934
releng/6.4/ r195935
releng/6.3/ r195935
stable/7/ r195933
releng/7.2/ r195935
releng/7.1/ r195935
- -------------------------------------------------------------------------

VII. References

https://www.isc.org/node/474
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538975
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0696

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-SA-09:12.bind.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iD8DBQFKb5koFdaIBMps37IRAglLAKCFGXI+MAsksnK5TZB/8L3UFhPS1gCgl7q5
6fCpOeBcf7f83dVfKRDVF0I=
=akJW
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

The FreeBSD Foundation 2009 Semi-Annual Newsletter

2009-07-28T14:59:33Z

Dear FreeBSD Community,

We are pleased to announce the publication of The FreeBSD Foundation's
Semi-Annual Newsletter.

Go to http://www.freebsdfoundation.org/press/2009Jul-newsletter.shtml
to find out how we have supported the FreeBSD Project and community this
year.

Sincerely,

The FreeBSD Foundation

_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

Accepting Travel Grant Applications for EuroBSDCon 2009

2009-07-20T12:30:58Z

Calling all FreeBSD developers needing assistance with travel expenses
to EuroBSDCon 2009.

The FreeBSD Foundation will be providing a limited number of travel
grants to individuals requesting assistance. Please fill out and submit
the Travel Grant Request Application at
http://www.freebsdfoundation.org/documents/TravelRequestForm.pdf by
August 20, 2009 to apply for this grant.

How it works:

This program is open to FreeBSD developers of all sorts (kernel hackers,
documentation authors, bugbusters, system administrators, etc). In some
cases we are also able to fund non-developers, such as active community
members and FreeBSD advocates.

(1) You request funding based on a realistic and economical estimate of
travel costs (economy airfare, trainfare, ...), accommodations
(conference hotel and sharing a room), and registration or tutorial
fees. If there are other sponsors willing to cover costs, such as your
employer or the conference, we prefer you talk to them first, as our
budget is limited. We are happy to split costs with you or another
sponsor, such as just covering airfare or board.

If you are a speaker at the conference, we expect the conference to
cover your travel costs, and will most likely not approve your direct
request to us.

(2) We review your application and if approved, authorize you to seek
reimbursement up to a limit. We consider several factors, including our
overall and per-event budgets, and (quite importantly) the benefit to
the community by funding your travel.

Most rejected applications are rejected because of an over-all limit on
travel budget for the event or year, due to unrealistic or uneconomical
costing, or because there is an unclear or unconvincing argument that
funding the application will directly benefit the FreeBSD Project.
Please take these points into consideration when writing your application.

(3) We reimburse costs based on actuals (receipts), and by check or bank
transfer. We require you submit a report on your trip, which we may
show to current or potential sponsors, and may include in our quarterly
newsletter.

There's some flexibility in the mechanism, so talk to us if something
about the model doesn't quite work for you or if you have any questions.
The travel grant program is one of the most effective ways we can
spend money to help support the FreeBSD Project, as it helps developers
get together in the same place at the same time, and helps advertise and
advocate FreeBSD in the larger community.

Thank You,

The FreeBSD Foundation

_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

Foundation Project Announcement

2009-07-17T12:41:00Z

Dear FreeBSD Community,

The FreeBSD Foundation is pleased to announce another funded project!

Ed Schouten has been awarded a grant to write a new console driver for
the FreeBSD project. We are excited to support Ed in providing a more
efficient and user friendly console driver.

This project will allow Ed to add an additional abstraction layer to the
kernel. This new layer, the terminal layer will be a layer that sits
between the TTY layer, the kernel console (cngetc, cnputc) and the
actual console driver. Right now we have a terminal emulator (libteken)
that is part of Syscons. This terminal emulator will be moved into this
terminal layer.

The advantage of having such a layer, is that the console driver itself
does not have to care about any TTY semantics, streams of bytes,
processing escape sequences, etc. It will just receive a set of
character drawing, filling and copying actions. This should also make it
easier to implement Unicode.

"During this project I'm going to continue the work I did with the TTY
layer, by developing a new console driver for the FreeBSD kernel," said
Ed Schouten, FreeBSD Developer. "By moving towards a graphics mode
console driver, it will be much easier to make the boot process look
nice on desktop systems (i.e. PC-BSD). It will also make it possible to
support the industry-standard Unicode character sets by default."

This project will be completed by the end of December.

Sincerely,

The FreeBSD Foundation

_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

Announcing EuroBSCon 2009

2009-07-13T06:18:43Z

EuroBSDcon 2009
Friday 18th - Sunday 20th September,
University of Cambridge, UK

A day of tutorials followed by 2 days of conference talks
covering a wide variety of BSD related topics. This is the
European BSD Community's annual event to meet, share and
interact across the projects and between friends.

This year's line up features...
* ISC and *BSD
* OpenBSD malloc
* How FreeBSD finds oil
* NetBSD's LVM
* faster packets in OpenBSD
* Wireless Mesh networks
* Kirk McKusick's FreeBSD Guide
* and more,

The full talk list and schedule: http://2009.euroBSDcon.org

Discounted Early Bird registration runs until 2nd
September. Book your place now at
http://2009.euroBSDcon.org

Final programme may be subject to alteration. EuroBSDcon
is a not for profit event open to everyone so please help
spread the word online and offline. Thanks for reading!

If you're interested to read this far, you can sign up for
future announcements about EuroBSDcons by sending an email to
eurobsdcon-announce-subscribe@... . Your address
will only be used to contact you about European BSD events.

EuroBSDcon 2009 : September 18-20th, Cambridge, England.

http://www.ukuug.org/events/eurobsdcon2009/

EuroBSDcon is grateful to our sponsors; Premier Sponsor iXsystems.com,
and The FreeBSD Foundation, NetApp and Google.

_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

BSD Router Project (bsdrp)

2009-07-05T22:40:34Z

Olivier Cochard-Labbé, founder of FreeNAS, has released the first
alpha (0.1) image of his new project: BSD Router Project -
http://bsdrp.net

bsdrp is an open source, customised distribution of FreeBSD dedicated
to offering IP routing services for small ISP's.

The release 0.1 of BSDRP is a fully working prototype, to be used on
real or virtual machines that boot from ATA device only (not usb).

This first release includes:

- Base FreeBSD 8.0-CURRENT system (NanoBSD) for i386
- Customized script (config, upgrade, help, command completion, etc…)
- Quagga ready to use (OSPFv2, OSPFv3, RIP, RIPng and BGP)

You may ask, what is the difference between BSDRP and m0n0wall of pfSense.

The main goal of BSDRP is not firewalling but routing. If you need a
firewall don't use BSDRP: Use m0n0wall or pfSense.
BSDRP is not for a home use, but for compagny use (small ISP's for example).
BSDRP doesn't have a Web GUI: It's to be configured from a CLI only
(like Cisco or Juniper)
pfSense can be used for routing, but Olivier wanted to set up a Cisco
or Juniper like project just for routing.

Source: www.freebsdnews.net
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Errata Notice FreeBSD-EN-09:04.fork

2009-06-23T22:44:29Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-EN-09:04.fork Errata Notice
The FreeBSD Project

Topic: Deadlock in a multi-threaded program during fork(2)

Category: core
Module: libc
Announced: 2009-06-24
Credits: Konstantin Belousov <kib@...>,
Max Brazhnikov <makc@...>
Affects: FreeBSD 7.2
Corrected: 2009-05-03 17:51:38 (RELENG_7, 7.2-STABLE)
2009-06-24 05:28:09 (RELENG_7_2, 7.2-RELEASE-p2)

For general information regarding FreeBSD Errata Notices and Security
Advisories, including descriptions of the fields above, security
branches, and the following sections, please visit
<URL:http://security.freebsd.org/>.

I. Background

fork(2) is a system call which causes creation of a new process.
FreeBSD supports invoking the malloc(3) function during the fork(2) in
a process running in threaded mode which involves locking of the memory
allocator.

II. Problem Description

A lock order reversal has been found in the interaction between the
malloc(3) implementation and threading library. When a multi-threaded
process calls the fork(2) system call in a thread and the malloc(3)
function in another thread it can cause a deadlock in the child
process.

III. Impact

A multi-threaded program that calls fork(2) in a thread and malloc(3)
in another thread can make the child process stop unintentionally.
There is no direct impact on the other processes or the kernel.

IV. Workaround

No workaround is available.

V. Solution

Perform one of the following:

1) Upgrade your vulnerable system to 7-STABLE or to the RELENG_7_2
security branch dated after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 7.2 system.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/EN-09:04/fork.patch
# fetch http://security.FreeBSD.org/patches/EN-09:04/fork.patch.asc

b) Execute the following commands as root:

# cd /usr/src
# patch < /path/to/patch
# cd /usr/src/lib/libc
# make obj && make depend && make && make install

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_7
src/lib/libc/stdlib/malloc.c 1.147.2.7
RELENG_7_2
src/UPDATING 1.507.2.23.2.5
src/sys/conf/newvers.sh 1.72.2.11.2.6
src/lib/libc/stdlib/malloc.c 1.147.2.6.2.2
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/7/ r191767
releng/7.2/ r194808
- -------------------------------------------------------------------------

VII. References

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-EN-09:04.fork.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkpBvBsACgkQFdaIBMps37LnLQCeNw8Es9R9X8QySoZni2JQ9Kma
N+8An3Ff/bB4l3dvgfAa0rAA+TjbfQBV
=8YtE
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Errata Notice FreeBSD-EN-09:03.fxp

2009-06-23T22:44:27Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-EN-09:03.fxp Errata Notice
The FreeBSD Project

Topic: Poor TCP performance of fxp(4)

Category: core
Module: sys/dev
Announced: 2009-06-24
Credits: Bjoern Koenig <bkoenig@...>
Pyun YongHyeon <yongari@...>
Affects: FreeBSD 7.2
Corrected: 2009-05-07 01:14:59 (RELENG_7, 7.2-STABLE)
2009-06-24 05:28:09 (RELENG_7_2, 7.2-RELEASE-p3)

For general information regarding FreeBSD Errata Notices and Security
Advisories, including descriptions of the fields above, security
branches, and the following sections, please visit
<URL:http://security.freebsd.org/>.

I. Background

fxp(4) is a network device driver which provides support for Ethernet
adapters based on the Intel i82557, i82558, i82559, i82550, and i82562
chips. It supports TCP segmentation offload (TSO) for IPv4 on i82550
and i82551.

II. Problem Description

When a TSO option is enabled, fxp(4) always sets the length of outgoing IP
packets as the interface MTU (Maximum Transmission Unit). This could
could cause the packet to be lost when the TCP receiver advertises a smaller
MSS (Maximum Segment Size) than the interface MTU on the sender side.

III. Impact

TCP connections via fxp(4) can cause significantly poor performance
when the TSO option is enabled due to packet loss. Note that the loss
depends on the receiver side's MSS.

IV. Workaround

Disable TSO of fxp(4) interfaces on your system. There are two ways
to do this:

(disable TSO of a specific interface; "fxp0" in the below example)
# ifconfig fxp0 -tso

(disable TSO of all interfaces on the system)
# sysctl net.inet.tcp.tso=0

V. Solution

Perform one of the following:

1) Upgrade your vulnerable system to 7-STABLE or to the RELENG_7_2
security branch dated after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 7.2 system.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/EN-09:03/fxp.patch
# fetch http://security.FreeBSD.org/patches/EN-09:03/fxp.patch.asc

b) Apply the patch.

# cd /usr/src
# patch < /path/to/patch

c) Recompile your kernel as described in
<URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot
the system.

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_7
src/sys/dev/fxp/if_fxp.c 1.266.2.15
RELENG_7_2
src/UPDATING 1.507.2.23.2.5
src/sys/conf/newvers.sh 1.72.2.11.2.6
src/sys/dev/fxp/if_fxp.c 1.266.2.14.2.2
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/7/ r191867
releng/7.2/ r194808
- -------------------------------------------------------------------------

VII. References

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-EN-09:03.fxp.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkpBvA0ACgkQFdaIBMps37IKbACfdnwjftNf/f/3c+hvxOKGz7eg
osQAmwRaCBV/a2A3Pdxt/FxGwg+bHXM7
=rUkc
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Errata Notice FreeBSD-EN-09:02.bce

2009-06-23T22:44:24Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-EN-09:02.bce Errata Notice
The FreeBSD Project

Topic: bce(4) does not work with lagg(4) LACP mode

Category: core
Module: sys/dev
Announced: 2009-06-24
Credits: Pete French <petefrench@...>
David Christensen
Affects: FreeBSD 7.2
Corrected: 2009-05-20 21:13:49 (RELENG_7, 7.2-STABLE)
2009-06-24 05:28:09 (RELENG_7_2, 7.2-RELEASE-p2)

For general information regarding FreeBSD Errata Notices and Security
Advisories, including descriptions of the fields above, security
branches, and the following sections, please visit
<URL:http://security.freebsd.org/>.

I. Background

bce(4) is a network device driver for Broadcom NetXtreme II
(BCM5706/5708/5709/5716) PCI/PCIe Gigabit Ethernet adapters. The
lagg(4) driver is a pseudo network interface driver which allows
aggregation of multiple network interfaces as one virtual interface
for the purpose of providing fault-tolerance and high-speed links.

II. Problem Description

The bce(4) driver used an incorrect total packet length calculation. This
bug was accidentally added just after 7.1-RELEASE.

III. Impact

When adding a bce(4) interface on the system as a lagg(4) member with
the LACP aggregation protocol enabled network communication via the
bce(4) interface stops completely. Although the bce(4) interface
works if it is not a lagg(4) member, the incoming traffic statistics
which can be found in netstat(1) output will be incorrect because
every packet is recognized as full-sized one.

IV. Workaround

No workaround is available.

V. Solution

Perform one of the following:

1) Upgrade your vulnerable system to 7-STABLE or to the RELENG_7_2
security branch dated after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 7.2 system.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/EN-09:02/bce.patch
# fetch http://security.FreeBSD.org/patches/EN-09:02/bce.patch.asc

b) Apply the patch.

# cd /usr/src
# patch < /path/to/patch

c) Recompile your kernel as described in
<URL:http://www.freebsd.org/handbook/kernelconfig.html> and reboot
the system.

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_7
src/sys/dev/bce/if_bce.c 1.34.2.8
src/sys/dev/bce/if_bcereg.c 1.16.2.3
RELENG_7_2
src/UPDATING 1.507.2.23.2.5
src/sys/conf/newvers.sh 1.72.2.11.2.6
src/sys/dev/bce/if_bce.c 1.34.2.7.2.2
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/7/ r192477
releng/7.2/ r194808
- -------------------------------------------------------------------------

VII. References

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-EN-09:02.bce.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkpBu9cACgkQFdaIBMps37IyrgCeKorJrpSXubynKzNJ2ld4j1K3
RqoAnAjhR8Fld9c8gJUIP/BuQ0wx2atT
=oSkz
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

Foundation Project Announcement

2009-06-17T11:57:31Z

Dear FreeBSD Community,

The FreeBSD Foundation is pleased to announce another funded project!

Mark Linimon has been awarded a grant to prototype a new problem
reporting system for the FreeBSD project. This project will allow Mark
to define the features, look-and-feel, and architecture of a future
replacement of the project's current GNATs based system. Once the
prototype is complete, it will be used to garner input from the FreeBSD
community before a production system is implemented.

"One of the most frequently requested improvements from the FreeBSD
developer community is an improved bug tracking system," said Mark
Linimon. He also added, "The design goals of this prototype are
to incorporate such features as markedly improved workflow, better
categorization, customizable email notifications, and redesigned web
pages to make searching and browsing easier."

"Once the prototype is completed," Mark added, "it will be circulated
amongst the developer community for feedback. I am happy to have the
Foundation's support to work on this project."

"Problem reporting software is a critical tool for getting feedback
from the FreeBSD user community, recording information about defects
and missing features in the system, and making our volunteer developers
productive," said Justin Gibbs, Founder of the FreeBSD Foundation.
"Mark has used manpower and sheer will to overcome the deficiencies
in the current problem reporting system, and to make it work for the
project. But our GNATs isn't fully utilized because of missing features
and a clumsy user interface. We're very excited to help address these
problems in a core piece of the FreeBSD project's infrastructure."

This project will be completed by the end of June.

Sincerely,

The FreeBSD Foundation

_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Security Advisory FreeBSD-SA-09:09.pipe

2009-06-10T03:41:54Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-SA-09:09.pipe Security Advisory
The FreeBSD Project

Topic: Local information disclosure via direct pipe writes

Category: core
Module: kern
Announced: 2009-06-10
Credits: Pieter de Boer
Affects: All supported versions of FreeBSD.
Corrected: 2009-06-10 10:31:11 UTC (RELENG_7, 7.2-STABLE)
2009-06-10 10:31:11 UTC (RELENG_7_2, 7.2-RELEASE-p1)
2009-06-10 10:31:11 UTC (RELENG_7_1, 7.1-RELEASE-p6)
2009-06-10 10:31:11 UTC (RELENG_6, 6.4-STABLE)
2009-06-10 10:31:11 UTC (RELENG_6_4, 6.4-RELEASE-p5)
2009-06-10 10:31:11 UTC (RELENG_6_3, 6.3-RELEASE-p11)

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

I. Background

One of the most commonly used forms of interprocess communication on
FreeBSD and other UNIX-like systems is the (anonymous) pipe. In this
mechanism, a pair of file descriptors is created, and data written to
one descriptor can be read from the other.

FreeBSD's pipe implementation contains an optimization known as "direct
writes". In this optimization, rather than copying data into kernel
memory when the write(2) system call is invoked and then copying the
data again when the read(2) system call is invoked, the FreeBSD kernel
takes advantage of virtual memory mapping to allow the data to be copied
directly between processes.

II. Problem Description

An integer overflow in computing the set of pages containing data to be
copied can result in virtual-to-physical address lookups not being
performed.

III. Impact

An unprivileged process can read pages of memory which belong to other
processes or to the kernel. These may contain information which is
sensitive in itself; or may contain passwords or cryptographic keys
which can be indirectly exploited to gain sensitive information or
access.

IV. Workaround

No workaround is available, but systems without untrusted local users
are not vulnerable. System administrators are reminded that even if a
system is not intended to have untrusted local users, it may be possible
for an attacker to exploit some other vulnerability to obtain local user
access to a system.

V. Solution

Perform one of the following:

1) Upgrade your vulnerable system to 6-STABLE, or 7-STABLE, or to the
RELENG_7_2, RELENG_7_1, RELENG_6_4, or RELENG_6_3 security branch
dated after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 6.3, 6.4,
7.1, and 7.2 systems.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/SA-09:09/pipe.patch
# fetch http://security.FreeBSD.org/patches/SA-09:09/pipe.patch.asc

b) Apply the patch.

# cd /usr/src
# patch < /path/to/patch

c) Recompile your kernel as described in
<URL:http://www.FreeBSD.org/handbook/kernelconfig.html> and reboot the
system.

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_6
src/sys/kern/sys_pipe.c 1.184.2.5
RELENG_6_4
src/UPDATING 1.416.2.40.2.9
src/sys/conf/newvers.sh 1.69.2.18.2.11
src/sys/kern/sys_pipe.c 1.184.2.4.2.2
RELENG_6_3
src/UPDATING 1.416.2.37.2.16
src/sys/conf/newvers.sh 1.69.2.15.2.15
src/sys/kern/sys_pipe.c 1.184.2.2.6.2
RELENG_7
src/sys/kern/sys_pipe.c 1.191.2.5
RELENG_7_2
src/UPDATING 1.507.2.23.2.4
src/sys/conf/newvers.sh 1.72.2.11.2.5
src/sys/kern/sys_pipe.c 1.191.2.3.4.2
RELENG_7_1
src/UPDATING 1.507.2.13.2.9
src/sys/conf/newvers.sh 1.72.2.9.2.10
src/sys/kern/sys_pipe.c 1.191.2.3.2.2
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/6/ r193893
releng/6.4/ r193893
releng/6.3/ r193893
stable/7/ r193893
releng/7.2/ r193893
releng/7.1/ r193893
- -------------------------------------------------------------------------

VII. References

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-SA-09:09.pipe.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkovjN0ACgkQFdaIBMps37JkXwCgmLcEMOMAEIXRoJ220zwZhMKn
f+gAn1bZyLMhfZU7TI0xxhizwetDwMVI
=J37B
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Security Advisory FreeBSD-SA-09:10.ipv6

2009-06-10T03:41:49Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-SA-09:10.ipv6 Security Advisory
The FreeBSD Project

Topic: Missing permission check on SIOCSIFINFO_IN6 ioctl

Category: core
Module: netinet6
Announced: 2009-06-10
Credits: Hiroki Sato
Affects: All supported versions of FreeBSD.
Corrected: 2009-06-10 10:31:11 UTC (RELENG_7, 7.2-STABLE)
2009-06-10 10:31:11 UTC (RELENG_7_2, 7.2-RELEASE-p1)
2009-06-10 10:31:11 UTC (RELENG_7_1, 7.1-RELEASE-p6)
2009-06-10 10:31:11 UTC (RELENG_6, 6.4-STABLE)
2009-06-10 10:31:11 UTC (RELENG_6_4, 6.4-RELEASE-p5)
2009-06-10 10:31:11 UTC (RELENG_6_3, 6.3-RELEASE-p11)

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

I. Background

IPv6 is a new Internet Protocol, designed to replace (and avoid many of
the problems with) the current Internet Protocol (version 4). Many
properties of the FreeBSD IPv6 network stack can be configured via the
ioctl(2) interface.

II. Problem Description

The SIOCSIFINFO_IN6 ioctl is missing a necessary permissions check.

III. Impact

Local users, including non-root users and users inside jails, can set
some IPv6 interface properties. These include changing the link MTU
and disabling interfaces entirely. Note that this affects IPv6 only;
IPv4 functionality cannot be affected by exploiting this vulnerability.

IV. Workaround

No workaround is available, but systems without local untrusted users
are not vulnerable.

V. Solution

Perform one of the following:

1) Upgrade your vulnerable system to 6-STABLE, or 7-STABLE, or to the
RELENG_7_2, RELENG_7_1, RELENG_6_4, or RELENG_6_3 security branch
dated after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 6.3, 6.4,
7.1, and 7.2 systems.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

[FreeBSD 6.x]
# fetch http://security.FreeBSD.org/patches/SA-09:10/ipv6-6.patch
# fetch http://security.FreeBSD.org/patches/SA-09:10/ipv6-6.patch.asc

[FreeBSD 7.x]
# fetch http://security.FreeBSD.org/patches/SA-09:10/ipv6.patch
# fetch http://security.FreeBSD.org/patches/SA-09:10/ipv6.patch.asc

b) Apply the patch.

# cd /usr/src
# patch < /path/to/patch

c) Recompile your kernel as described in
<URL:http://www.FreeBSD.org/handbook/kernelconfig.html> and reboot the
system.

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_6
src/sys/netinet6/in6.c 1.51.2.13
RELENG_6_4
src/UPDATING 1.416.2.40.2.9
src/sys/conf/newvers.sh 1.69.2.18.2.11
src/sys/netinet6/in6.c 1.51.2.12.2.2
RELENG_6_3
src/UPDATING 1.416.2.37.2.16
src/sys/conf/newvers.sh 1.69.2.15.2.15
src/sys/netinet6/in6.c 1.51.2.11.2.1
RELENG_7
src/sys/netinet6/in6.c 1.73.2.7
RELENG_7_2
src/UPDATING 1.507.2.23.2.4
src/sys/conf/newvers.sh 1.72.2.11.2.5
src/sys/netinet6/in6.c 1.73.2.6.2.2
RELENG_7_1
src/UPDATING 1.507.2.13.2.9
src/sys/conf/newvers.sh 1.72.2.9.2.10
src/sys/netinet6/in6.c 1.73.2.4.2.2
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/6/ r193893
releng/6.4/ r193893
releng/6.3/ r193893
stable/7/ r193893
releng/7.2/ r193893
releng/7.1/ r193893
- -------------------------------------------------------------------------

VII. References

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-SA-09:10.ipv6.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkovjOUACgkQFdaIBMps37IFxwCgj0o1r4IQMIEvp3y4oIqhQwxe
cI8AoIlxweqjakKxu/A/Z4+xjoGmqUdF
=/kNi
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

FreeBSD Security Advisory FreeBSD-SA-09:11.ntpd

2009-06-10T03:41:45Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=============================================================================
FreeBSD-SA-09:11.ntpd Security Advisory
The FreeBSD Project

Topic: ntpd stack-based buffer-overflow vulnerability

Category: contrib
Module: ntpd
Announced: 2009-06-10
Credits: Chris Ries
Affects: All supported versions of FreeBSD.
Corrected: 2009-06-10 10:31:11 UTC (RELENG_7, 7.2-STABLE)
2009-06-10 10:31:11 UTC (RELENG_7_2, 7.2-RELEASE-p1)
2009-06-10 10:31:11 UTC (RELENG_7_1, 7.1-RELEASE-p6)
2009-06-10 10:31:11 UTC (RELENG_6, 6.4-STABLE)
2009-06-10 10:31:11 UTC (RELENG_6_4, 6.4-RELEASE-p5)
2009-06-10 10:31:11 UTC (RELENG_6_3, 6.3-RELEASE-p11)
CVE Name: CVE-2009-1252

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

I. Background

The ntpd(8) daemon is an implementation of the Network Time Protocol (NTP)
used to synchronize the time of a computer system to a reference time
source.

Autokey is a security model for authenticating Network Time Protocol
(NTP) servers to clients, using public key cryptography.

II. Problem Description

The ntpd(8) daemon is prone to a stack-based buffer-overflow when it is
configured to use the 'autokey' security model.

III. Impact

This issue could be exploited to execute arbitrary code in the context of
the service daemon, or crash the service daemon, causing denial-of-service
conditions.

IV. Workaround

Use IP based restrictions in ntpd(8) itself or in IP firewalls to
restrict which systems can send NTP packets to ntpd(8).

Note that systems will only be affected if they have the "autokey" option
set in /etc/ntp.conf; FreeBSD does not ship with a default ntp.conf file,
so will not be affected unless this option has been explicitly enabled by
the system administrator.

V. Solution

Perform one of the following:

1) Upgrade your vulnerable system to 6-STABLE, or 7-STABLE, or to the
RELENG_7_2, RELENG_7_1, RELENG_6_4, or RELENG_6_3 security branch
dated after the correction date.

2) To patch your present system:

The following patches have been verified to apply to FreeBSD 6.3, 6.4,
7.1, and 7.2 systems.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

[FreeBSD 6.3]
# fetch http://security.FreeBSD.org/patches/SA-09:11/ntpd63.patch
# fetch http://security.FreeBSD.org/patches/SA-09:11/ntpd63.patch.asc

[FreeBSD 6.4 and 7.x]
# fetch http://security.FreeBSD.org/patches/SA-09:11/ntpd.patch
# fetch http://security.FreeBSD.org/patches/SA-09:11/ntpd.patch.asc

b) Execute the following commands as root:

# cd /usr/src
# patch < /path/to/patch
# cd /usr/src/usr.sbin/ntp/ntpd
# make obj && make depend && make && make install
# /etc/rc.d/ntpd restart

VI. Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch Revision
Path
- -------------------------------------------------------------------------
RELENG_6
src/contrib/ntp/ntpd/ntp_crypto.c 1.1.1.3.8.3
RELENG_6_4
src/UPDATING 1.416.2.40.2.9
src/sys/conf/newvers.sh 1.69.2.18.2.11
src/contrib/ntp/ntpd/ntp_crypto.c 1.1.1.3.8.1.2.2
RELENG_6_3
src/UPDATING 1.416.2.37.2.16
src/sys/conf/newvers.sh 1.69.2.15.2.15
src/contrib/ntp/ntpd/ntp_crypto.c 1.1.1.3.20.2
RELENG_7
src/contrib/ntp/ntpd/ntp_crypto.c 1.1.1.3.18.3
RELENG_7_2
src/UPDATING 1.507.2.23.2.4
src/sys/conf/newvers.sh 1.72.2.11.2.5
src/contrib/ntp/ntpd/ntp_crypto.c 1.1.1.3.18.2.2.1
RELENG_7_1
src/UPDATING 1.507.2.13.2.9
src/sys/conf/newvers.sh 1.72.2.9.2.10
src/contrib/ntp/ntpd/ntp_crypto.c 1.1.1.3.18.1.2.2
- -------------------------------------------------------------------------

Subversion:

Branch/path Revision
- -------------------------------------------------------------------------
stable/6/ r193893
releng/6.4/ r193893
releng/6.3/ r193893
stable/7/ r193893
releng/7.2/ r193893
releng/7.1/ r193893
- -------------------------------------------------------------------------

VII. References

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1252

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-SA-09:11.ntpd.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAkovjOwACgkQFdaIBMps37KRpwCfaQF9q8KhElv6LqgFv3DX2h9c
hbEAn2Q0X8Qv8r5OySnhlAw2pMxlxkXK
=Mh2u
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."

HotCloud '09 Registration Now Open

2009-05-28T10:14:11Z

We'd like to invite you to the Workshop on Hot Topics in Cloud
Computing (HotCloud '09), taking place in San Diego, CA, June 15, 2009.

HotCloud '09 will discuss challenges in the Cloud Computing paradigm,
including the design, implementation, and deployment of virtualized
clouds.

Join academics and practitioners in sharing experiences, leveraging each
other's perspectives, and identifying new and emerging "hot" trends in
this area.

The program includes sessions on:
* Cloud Platforms and Architectures
* Elastic Clouds and Resource Management
* Storage Cloud and Appliances
* Map Reduce and Cloud Applications
* Panel on Cloud Computing

The full program can be found at
http://www.usenix.org/events/hotcloud09/tech/

Don't miss this opportunity to engage in dynamic discussion on
key topics in the cloud computing community. Register today at
http://www.usenix.org/hotcloud09/proga

HotCloud will be co-located with the 2009 USENIX Annual Technical
Conference (USENIX '09), June 14-19:
http://www.usenix.org/events/usenix09/

Multiple Conference Savings: Go to both HotCloud '09 and USENIX '09 and
save $100 off your USENIX '09 registration.
Contact the Conference Department at conference@... to receive
your priority discount code.

NOTE: If you're already registered for USENIX '09, contact the
Conference Department at the email address above to receive your $100
refund.

We look forward to seeing you in San Diego!

Sambit Sahu, IBM T.J. Watson Research Center
Prashant Shenoy, University of Massachusetts Amherst
HotCloud '09 Program Chairs

----------------------------------
Workshop on Hot Topics in Cloud Computing (HotCloud '09)
June 15, 2009
San Diego, CA
Sponsored by USENIX: The Advanced Computing Systems Association
Register online by Monday, June 8, 2009, noon PDT
http://www.usenix.org/hotcloud/proga
----------------------------------
_______________________________________________
freebsd-announce@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@..."