Comments on: Column: The man who changed Internet security
Future vulnerability disclosures should benefit from Dan Kaminsky's responsible handling of Tuesday's DNS flaw.
Future vulnerability disclosures should benefit from Dan Kaminsky's responsible handling of Tuesday's DNS flaw.
Web sites launch all the time, but they also shut their doors. We highlight 15 that bit the dust this year.
Let the debate begin: Was the iPhone more important than iTunes? Was anything bigger than Google finding a great business model? CNET offers its list of the 10 most important stories of the '00s.
Covering computer viruses and computer crime, Robert Vamosi goes beyond the hype to provide you with expert interviews of the top security researchers, as well as offering the hands-on, nontechnical advice you'll need to stay safe online.
Add this feed to your online news reader
Using telnet and going into various areas just exploring.
I went from my local library to MIT then onto NIST then onto some tokyo university BBS retracing mysteps it went all the way around the world through nasa then loggen back into my library.
Sad to see we can't do that anymore. No more wild jungle.
Let's find out who is making the money, this vulnerability is over hyped.
If they had not and Kaminsky hadn't disclosed it would have been irresponsible. The black hats would have found it eventually leaving everyone at the mercy of them.
Full disclosure is always better than those idiots who think there is any merit to security through obscurity.
BUT...if I do sit on it and a hacker finds the exploit and then I come out afterward, I get nailed for not sharing it. D-amned if I do and d-amned if I don't. The good guys always loose.
Another thing I have learned is usually the hacker will almost always win. All you can do is contain, eradicate, and learn from attacks and exploits to make it harder for them to break in. Not sharing your discoveries from the general public and only with vendors is most certainly NOT the way to resolve these issues however. I do not commend Dan Kaminsky for his actions, he is setting a BAD precedent. One that unfortunately Infragard, another organization with a history of one way traffic with information, follows.
The vendors have become pretty good at responding to stuff -- and, of course, if you do find something of technical value, please feel free to contact me and I will be happy to help. I'm trying to find a balancing point between not releasing (which leads to no patches, and/or no deployment of patches) and releasing in a problematic manner (i.e. even those places that are responsible, and do maintain their security, are still hit). Maybe this isn't perfect, but please give me the benefit of the doubt until you know just what I've found.
I think vendor response is again a matter of perspective. I work PCI vulnerabilities almost exclusively and you would be amazed when a vulnerability is discovered and the vendor considers it an "enhancement" and they want money to correct it!
I take care of my personal data because I know it is a free for all out there. But to be honest, I am not getting that meeting with Micro$oft. Ain't happening. I know people who have doing security work for 15+ years and have government experience. They are not getting access either. We get Bugtraq. So to be honest, I am not going to any sleep at night if AT&T's North American network drops if I post a vulnerability in some system on Bugtraq. Period. If I am to at the mercy of the free for all, I will play the game as a free for all.
On a side note, I do not have much of an issue with retaliation against attackers either. Then again, I might have a bit more flexible ethics and morals than most people. I think if the internet were viewed from this perspective, security WOULD be become everyone's business instead of a slogan on a poster.
Security is like any other field. It is a who knows who, political football, and "do we have the money to fix that" field.
I agree. It's only because the vendors were so amazingly responsive that this path could be taken at all. If they'd been lame, we'd be screaming at them for being so. So, they weren't lame, in all fairness they deserve some appreciation for that.
If he hadn't circled his disclosure around a profiteering security conference I wouldn't bash this **** so much.
Because he has circled his disclosure around a big security conference, I know his motivation is money.
I don't know who he has been shaking hands with and what money has been exchanged, but this is something for the government to wire tap on.
Your whole system is geared on making money.
How do you survive mate?
Dude, did you miss the fact that Defcon is like three days later? Black Hat is just practice for Defcon :) Seriously, the last big talk was Seattle Toorcon. Rickrolling the Internet isn't exactly profit source number one.
- by Seaspray0 July 19, 2008 5:31 PM PDT
- I admire Dan for doing the right thing. So often people only think of themselves. Dan did what was best for all of us. While it doesn't grab the emediate monetary benefits he could have gained, it shows great integrity and that does count when it comes to working relationships. It's hard to find people whom you can trust these days, and when you do, you will want to do business with them. Good luck to you, Dan.
- Like this Reply to this comment
-
(14 Comments)