[nsp-sec] List of vulnerable DNS resolvers

[Barry Raveendran Greene]

First, Ack for 10458 & 14203. 

Second, if the goal is to start knocking on doors, then there are ways of
really mobilizing. Vendors do have sales and support teams. These sales and
support teams can be mobilized. I know I can do something where I sit now
(Juniper - but not sure how effective it would be). I also know there are
other teams out there that can be activated. 

Niels, if you would like to explore this, let me know. 

One day of work could really turn things around. I'm willing to put that
time in to make this happen.

> -----Original Message-----
> From: nsp-security-bounces at puck.nether.net 
> [mailto:nsp-security-bounces at puck.nether.net] On Behalf Of 
> Niels Provos
> Sent: Tuesday, July 22, 2008 4:46 PM
> To: Smith, Donald
> Cc: nsp-security at puck.nether.net
> Subject: Re: [nsp-sec] List of vulnerable DNS resolvers
> 
> ----------- nsp-security Confidential --------
> 
> On Tue, Jul 22, 2008 at 4:32 PM, Smith, Donald 
> <Donald.Smith at qwest.com> wrote:
> > Neils, I think the right thing to do is notify these 
> customers do you want credit, or do we sanitize or  ...?
> 
> Please, reach out to your customers.  My hope is that we can help fix
> the Internet.   I don't care for credit.   So, you could either
> sanitize or not, depending on what you think would work better.
> 
> Thank you,
>  Niels.
> 
> 
> _______________________________________________
> nsp-security mailing list
> nsp-security at puck.nether.net
> https://puck.nether.net/mailman/listinfo/nsp-security
> 
> Please do not Forward, CC, or BCC this E-mail outside of the 
> nsp-security community. Confidentiality is essential for 
> effective Internet security counter-measures.
> _______________________________________________
>