> I'm about to import bind 8.2.2.p5 into src/contrib/bind and fix up the
> broken parts of the tree as I go. I will disable the named (and associated
> tools) build for the duration. If you want to do some make worlds or
> releases in the next 8 hours or so, do a cvsup pronto!
Thanks Peter!
N
Peter Wemm wrote:
> I'm about to import bind 8.2.2.p5 into src/contrib/bind and fix up the
> broken parts of the tree as I go. I will disable the named (and associated
> tools) build for the duration. If you want to do some make worlds or
> releases in the next 8 hours or so, do a cvsup pronto!
I'm about to import bind 8.2.2.p5 into src/contrib/bind and fix up the
broken parts of the tree as I go. I will disable the named (and associated
tools) build for the duration. If you want to do some make worlds or
releases in the next 8 hours or so, do a cvsup pronto!
Cheers,
-Peter
To Unsu
-BEGIN PGP SIGNED MESSAGE-
In message <[EMAIL PROTECTED]> TrouBle writes:
: just a quick note, where do i find the information needed about the bind
: problem i face in 3.3-RELEASE if any ??
You can find it at the BIND web site.
FreeBSD has Bind 8.1.2.
- From the chart at
http
-BEGIN PGP SIGNED MESSAGE-
In message <[EMAIL PROTECTED]> Ben Rosengart
writes:
: I'd be happier if you said the message was *from* the security officer. :-)
I am the security officer. :-) That's why I get the
secuirty-officer's mail :-). I've not verified the information by
inspecti
On Wed, 17 Nov 1999, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Forrest Aldrich writes:
> : So wouldn't be the impact if a server was compromized in the absence
> : of an available fix :)
>
> A message to the security officer indicated that we don't have the
> root hole in -current or -
In message <[EMAIL PROTECTED]> Forrest Aldrich writes:
: So wouldn't be the impact if a server was compromized in the absence
: of an available fix :)
A message to the security officer indicated that we don't have the
root hole in -current or -stable, but are vulnerable to the DoS
attacks.
Warne
So wouldn't be the impact if a server was compromized in the absence
of an available fix :)
At 02:46 PM 11/16/99 +0800, Peter Wemm wrote:
>Ben Rosengart wrote:
> > On Mon, 15 Nov 1999, Forrest Aldrich wrote:
> >
> > > Will we be updating 4.0-current to the latest BIND-8.22-P5?
> >
> > Or -stable
Ben Rosengart wrote:
> On Mon, 15 Nov 1999, Forrest Aldrich wrote:
>
> > Will we be updating 4.0-current to the latest BIND-8.22-P5?
>
> Or -stable for that matter? I believe these changes are eminently
> qualified, being bugfixes.
The changes are most definately not "just" bugfixes. The imp
On Mon, 15 Nov 1999, Forrest Aldrich wrote:
> Will we be updating 4.0-current to the latest BIND-8.22-P5?
Or -stable for that matter? I believe these changes are eminently
qualified, being bugfixes.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscrib
Will we be updating 4.0-current to the latest BIND-8.22-P5?
_F
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
11 matches
Mail list logo