From: Jesse Pollard <jesse@cats-chateau.net>
To: Doug McNaught <doug@wireboard.com>, Gerhard Mack <gmack@innerfire.net>
Cc: Bob Lorenzini <hwm@newportharbornet.com>, linux-kernel@vger.kernel.org
Subject: Re: [OT] Linux Worm (fwd)
Date: Sat, 24 Mar 2001 11:11:50 -0600 [thread overview]
Message-ID: <01032411170201.03927@tabby> (raw)
In-Reply-To: <Pine.LNX.4.10.10103231028250.9403-100000@innerfire.net> <m3ae6c48v4.fsf@belphigor.mcnaught.org>
In-Reply-To: <m3ae6c48v4.fsf@belphigor.mcnaught.org>
On Fri, 23 Mar 2001, Doug McNaught wrote:
>Gerhard Mack <gmack@innerfire.net> writes:
>
>> On Fri, 23 Mar 2001, Bob Lorenzini wrote:
>>
>> > I'm annoyed when persons post virus alerts to unrelated lists but this
>> > is a serious threat. If your offended flame away.
>>
>> This should be a wake up call... distributions need to stop using product
>> with consistently bad security records.
>
>Is there an alternative to BIND that's free software? Never seen
>one.
Not one that is Open Source....
Bind itself has been proven over many years. This is the first major
problem found. If you want a fix, get bind v9. Besides handling IP version
4, it also handles version 6.
The only current limitation is the inability to control sort order of
hosts with multiple interfaces. I think this is due to the new IP v 6
resource handling.
Bind 9 works well (see ISC web page http://www.isc.org/products/BIND/)
>
>-Doug (who doesn't think this is a Good Thing)
It really isn't, but the new bind may be. There is even an update
to bind 8 that contains a fix for the problem.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: jesse@cats-chateau.net
Any opinions expressed are solely my own.
next prev parent reply other threads:[~2001-03-24 17:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 17:49 Linux Worm (fwd) Bob Lorenzini
2001-03-23 18:30 ` [OT] " Jonathan Morton
2001-03-23 18:31 ` Gerhard Mack
2001-03-23 18:51 ` [OT] " Doug McNaught
2001-03-23 19:39 ` Michael Bacarella
2001-03-23 22:19 ` Herbert Xu
2001-03-24 0:39 ` Edward S. Marshall
2001-03-24 17:11 ` Jesse Pollard [this message]
2001-03-24 17:50 ` Edward S. Marshall
2001-03-24 19:02 ` Sandy Harris
2001-03-23 18:56 ` Dax Kelson
2001-03-23 19:08 ` Jeremy Jackson
2001-03-23 20:30 ` Michael H. Warfield
2001-03-26 15:07 ` Richard B. Johnson
2001-03-26 15:24 ` Gregory Maxwell
2001-03-26 16:02 ` Bob_Tracy
2001-03-26 16:11 ` offtopic " John Jasen
2001-03-27 1:14 ` Drew Bertola
2001-03-26 18:53 ` Ben Ford
2001-03-26 15:40 ` David Weinehall
2001-03-26 16:51 ` Bob Lorenzini
2001-03-26 16:51 ` Henning P. Schmiedehausen
2001-03-26 18:32 ` Stephen Satchell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01032411170201.03927@tabby \
--to=jesse@cats-chateau.net \
--cc=doug@wireboard.com \
--cc=gmack@innerfire.net \
--cc=hwm@newportharbornet.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox