Re: FreeBSD Security Advisory: FreeBSD-SA-01:18.bind

From: Alfred Perlstein (bright@wintelcom.net)
Date: 01/31/01


Date: Wed, 31 Jan 2001 14:04:47 -0800
From: Alfred Perlstein <bright@wintelcom.net>
To: Roman Shterenzon <roman@xpert.com>


* Roman Shterenzon <roman@xpert.com> [010131 13:56] wrote:
> On Wed, 31 Jan 2001, FreeBSD Security Advisories wrote:
>
> > =============================================================================
> > FreeBSD-SA-01:18 Security Advisory
> >
> > Topic: BIND remotely exploitable buffer overflow
> ..snip..
>
> Why not make it default in the base system?

It has been, but only for several days.

-- 
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
"I have the heart of a child; I keep it in a jar on my desk."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message


Relevant Pages

  • Re: FreeBSD Security Advisory FreeBSD-SA-03:18.openssl
    ... On Fri, 3 Oct 2003, FreeBSD Security Advisories wrote: ... statically linked against librypto or libssl in the base system? ... from what I can see no API is changed with this patch so wouldn't it be ... possible to recompile libssl/libcrypto and install only them instead of ...
    (FreeBSD-Security)
  • Re: FreeBSD Security Advisory FreeBSD-SA-02:38.signed-error
    ... FreeBSD Security Advisories wrote: ... This might be an obtuse question, but I'm going to risk it and ask anyway. ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • Re: FreeBSD Security Advisory FreeBSD-SA-02:21.tcpip
    ... At 01:23 PM 4/17/2002, FreeBSD Security Advisories wrote: ... >the RELENG_4_5 security branch dated after the respective correction ... On what server is 4.5-RELEASE-p3 located? ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • Re: FreeBSD Security Advisory FreeBSD-SA-02:43.bind
    ... > Hello, FreeBSD Security Advisories! ... > These instructions are incorrect, ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)