Re: Kaminsky on djbdns bugs (fwd)

Dean Anderson <[email protected]>
Newsgroups gmane.network.djbdns
Message-ID <[email protected]>
Ahem.  We never did get the transcript of that "summit".  Think we can 
get that, now?  Now that the scam is exposed and fix discredited?

		--Dean

---------- Forwarded message ----------
Date: Fri, 08 Aug 2008 16:22:36 -0700
From: Rob <[email protected]>
To: [email protected]
Subject: Re: Kaminsky on djbdns bugs

Kevin Day wrote:
> 
> An announcement will be made as soon as possible about the scope and 
> details of what Dan Kaminsky is referring to. I'm trying to work with 
> djb and confirm everything with him this before making it public.
> 
> Patience guys, and relax - this isn't serious.
> 
> -- Kevin

<rant>

So now that the talk has been done and posted. We should also get the 
transcript of the "summit", so we can find out what really went on and if this 
"bug fix" is really a political concession made in order to appease people. In 
other words, is it a "well, this isn't really a bug, but we need to be able to 
make it look like DJB missed something, too - regardless of how small."
"relax - this isn't serious" makes it sounds as if it is exactly that.

Lack of transparency and central control suck no matter who is doing it and no 
matter how much it is "for our own good". I understand there was a need for 
secret central planning to pull off the fix before the talk but now there is 
no longer a need. The cat is out of the bag, the only possible reason to keep 
what went on a secret is to protect the egos of those who participated. And as 
  I am sure Dan K. knows, as any good reporter knows, if you don't protect 
those egos you will no longer have access to the inner circle. Sad that we 
have allowed our worldwide DNS infrastructure to be built on who can yell the 
loudest and gather the most cronies rather than build it by doing the right 
thing.

</rant>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.