http://www.theregister.co.uk/2012/05/17/dns_changer_blackouts/
-Henry
father of bind? that's news.
dnschanger gonna be a mess? that's not news.
randy
Paul certainly knows how to manipulate the press.
/bill
father of bind? that's news.
<http://boingboing.net/2012/03/29/paul-vixies-firsthand-accoun.html>
He was there, and Put The Fix In, to down the network.
I gather he's the one pulling it out on the appointed day as well.
dnschanger gonna be a mess? that's not news.
Agreed.
Aloha,
Michael.
Certainly news to Phil Almquist and the entire BIND development team
at UCB. Paul was at DECWRL and cut his teeth on pre-existing code.
While he (and ISC) have since revised, gutted, tossed all the orginal
code, rebuilt it twice - and others have done similar for their DNS
software, based on the BIND code base, implementation assumptions, and
with little or no ISC code, and they call it BIND as well, it would be
a HUGE leap of faith to call Paul Vixie the father of
BIND - The Berkeley Internet Naming Daemon.
As for being there and "Put The Fix In"... Makes for great PR but
in actual fact, its a bandaid that is not going to stem the tide.
An actual fix would really need to change the nature of the creaky
1980's implementation artifacts that this community loves so well.
/bill
As for being there and "Put The Fix In"... Makes for great PR but in
actual fact, its a bandaid that is not going to stem the tide.
maybe we could wad up the sensationalist and self-aggrandizing newspaper
articles and use them to plug the dike?
randy
father of bind? that's news.
<http://boingboing.net/2012/03/29/paul-vixies-firsthand-accoun.html>
He was there, and Put The Fix In, to down the network.
Certainly news to Phil Almquist and the entire BIND development team
at UCB. Paul was at DECWRL and cut his teeth on pre-existing code.
While he (and ISC) have since revised, gutted, tossed all the orginal
code, rebuilt it twice - and others have done similar for their DNS
software, based on the BIND code base, implementation assumptions, and
with little or no ISC code, and they call it BIND as well, it would be
a HUGE leap of faith to call Paul Vixie the father of
BIND - The Berkeley Internet Naming Daemon.
Methinks we're talking at cross purposes.
As for being there and "Put The Fix In"... Makes for great PR but
in actual fact, its a bandaid that is not going to stem the tide.
An actual fix would really need to change the nature of the creaky
1980's implementation artifacts that this community loves so well.
I don't think we're talking about the same thing at all.
Paul was there to shut down the DNS changer system and replace it with something that restored functionality to the infected machines.
And I gather Paul will be one of the people who will turn the lights out on it.
Your other comments are non-sequitur to the main issue.
When those servers are turned off, Customer Support folks at many ISPs will prolly want to take their accrued vacation.
Aloha,
Michael.
>>
>>
>>> father of bind? that's news.
>>
>> <http://boingboing.net/2012/03/29/paul-vixies-firsthand-accoun.html>
>>
>> He was there, and Put The Fix In, to down the network.
>
> Certainly news to Phil Almquist and the entire BIND development team
> at UCB. Paul was at DECWRL and cut his teeth on pre-existing code.
> While he (and ISC) have since revised, gutted, tossed all the orginal
> code, rebuilt it twice - and others have done similar for their DNS
> software, based on the BIND code base, implementation assumptions, and
> with little or no ISC code, and they call it BIND as well, it would be
> a HUGE leap of faith to call Paul Vixie the father of
> BIND - The Berkeley Internet Naming Daemon.Methinks we're talking at cross purposes.
maybe... 
my comment was refering to the "father of bind" statement.
> As for being there and "Put The Fix In"... Makes for great PR but
> in actual fact, its a bandaid that is not going to stem the tide.
> An actual fix would really need to change the nature of the creaky
> 1980's implementation artifacts that this community loves so well.I don't think we're talking about the same thing at all.
Paul was there to shut down the DNS changer system and replace it with something that restored functionality to the infected machines.
And I gather Paul will be one of the people who will turn the lights out on it.
He didn't "shut down" DNS Changer, he put up an equivalent system to hijack
DNS traffic and direct it to the "right" place... SO folks didn't see any
problem and the DNS Changer infection grew and got worse. When he is legally
required to take his "bandaide" out of service, then the problem will resolve
by folks who will have to clean their systems.
As for "turning the lights out" - that will only happen when the value of
DNS hijacking drops. As it is now, ISC has placed DNS hijacking code
into their mainstream code base... because DNS hijacking is so valuable to
folks. In a modestly favorable light, ISC looks like an arms dealer (DNS redirection)
to the bad guys -AND- (via DNSSEC) the good guys. Either way, they make money.
And yes, I think I agree with you. Paul will be there to turn things off when
they no longer make money for his company.
Your other comments are non-sequitur to the main issue.
Perhaps I am not a member of the Paul Vixie cult of personality.
When those servers are turned off, Customer Support folks at many ISPs will prolly want to take their accrued vacation.
Amen. And there will be thousands more of them when the court order expires than
existed when the Feds called him in.
/bill
When those servers are turned off, Customer Support folks at many
ISPs will prolly want to take their accrued vacation.Amen. And there will be thousands more of them when the court order
expires than existed when the Feds called him in.
they could extend the court order, or prolong the do-gooder hack longer
under some other pretext, increasing the underlying problem further.
more infected machines and more job creation for front line support when
the whitewash finally stops.
randy
According to the pretty graphs, the number of machines querying the aforementioned infrastructure is going down.
Just not as fast as pretty much everyone would prefer…
and the DOJ is footing the bill, and grows tired of it.
So at some point, the lights are gonna be turned off.
It's a shame the ISPs who have the infected users have done less to mitigate the issue.
And many solutions were suggested, but all of them ended up being … perceived to be worse than just shutting it down.
Or so I recall the presentation that Paul gave to a bunch of us in San Francisco back in February.
Aloha,
Michael.
Indeed, even the ISC history of the BIND project here:
http://www.isc.org/software/bind/history
shows that Paul's involvement began somewhere in the 4.9 timeframe.
One could, however, argue that he is the father of modern BIND implementations.
Owen
my thought "looks like a reasonably successful alternate root operator".
i mention kevin dunlap as well as bill's mention of phil almquist, and
there's another 4th floor of evans hall name i nay recall when caffinated.
-e
Hi,
dnschanger gonna be a mess? that's not news.
Is there anywhere a page where one can type an ASN or a CIDR block and then the whois contacts get a list of IPs that still contact the unintended servers?
(I had done ACL with log on borders, and resolvers did show up too.
So maybe some NS pointing towards those "bad" blocks?)
Thanks,
Frank
a message of 13 lines which said:
Is there anywhere a page where one can type an ASN or a CIDR block
and then the whois contacts get a list of IPs that still contact the
unintended servers?
To be fair, and take issue with this, it's not all on the ISPs, is it?
I've been seeing our counts decrease for months, but there are some who will not/cannot get it.
I am sadistically looking forward to the shutdown, admittedly.
You don't know journalists very well, do you?
Paul almost certainly (p > 0.995) had nothing to do with the writer's
chosen appellation, and wouldn't have been able to change it if he had.
Cheers,
-- jra
It makes for a more sensational story.
"Berkeley Internet Name Domain", in fact.
http://www.eecs.berkeley.edu/Pubs/TechRpts/1984/CSD-84-182.pdf
Joe
In a message written on Wed, May 23, 2012 at 12:35:05PM +0900, Randy Bush wrote:
father of bind? that's news.
I believe the error is in Paul Vixie's Wikipedia page, and I don't
do Wikipedia editing so I won't be fixing it.
"In 1988, while employed by DEC, he started working on the popular
internet domain name server BIND, of which he was the primary author and
architect, until release 8."
ISC has spent some effort on properly documenting the history of
BIND, and the result of that effort is located at:
http://www.isc.org/software/bind/history
You'll note there are two full paragraphs and a dozen folks involved
before Paul had anything to do with BIND.
ISC is always interested in updating the history if folks have any
additional information. Feel free to e-mail me if you think you have
something important to add.
So at some point, the lights are gonna be turned off.
It's a shame the ISPs who have the infected users have done less to mitigate the issue.To be fair, and take issue with this, it's not all on the ISPs, is it?
Agreed.
By definition, the numbers have been falling.
So somewhere, someone is doing something to lessen the coming /facepalm
I've been seeing our counts decrease for months, but there are some who will not/cannot get it.
I am sadistically looking forward to the shutdown, admittedly.
You have your time off approved I trust?
Aloha,
Michael.