-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-11:06.bind Security Advisory
The FreeBSD Project
Topic:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-11:08.telnetdSecurity Advisory
The FreeBSD Project
Topic:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-11:09.pam_sshSecurity Advisory
The FreeBSD Project
Topic:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-11:10.pamSecurity Advisory
The FreeBSD Project
Topic:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
No, the Grinch didn't steal the FreeBSD security officer GPG key, and your eyes
aren't deceiving you: We really did just send out 5 security advisories.
The timing, to put it bluntly, sucks. We normally aim to release advisories on
On Fri, 23 Dec 2011, FreeBSD Security Officer wrote:
Unfortunately my hand was forced: One of the issues (FreeBSD-SA-11:08.telnetd)
is a remote root vulnerability which is being actively exploited in the wild;
bugs really don't come any worse than this. On the positive side, most people
have
On Fri, 23 Dec 2011, Colin Percival wrote:
On 12/23/11 09:08, Tim Zingelman wrote:
On Fri, 23 Dec 2011, FreeBSD Security Officer wrote:
Unfortunately my hand was forced: One of the issues (FreeBSD-SA-11:08.telnetd)
is a remote root vulnerability which is being actively exploited in the wild;
On 12/23/11, Peter Jeremy peterjer...@acm.org wrote:
On 2011-Dec-23 07:41:20 -0800, FreeBSD Security Officer
cperc...@freebsd.org wrote:
The timing, to put it bluntly, sucks.
Since it's Saturday here, at the start of an extended holiday season, I
would tend to agree. That said, thanks for
What ports, etc. must one recompile after applying this patch? It
appears to modify libc.
--Brett Glass
___
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to
