Use this tool to learn about websites, specifically the one you just entered.
If you find some aspect of it inappropriate it is not our fault.
If you are the owner of this website: yes we are a real search engine, we do have a real web crawler called FyberSpider and you can block it if you feel the urge.
Is It Cataloged?
We are in the process of updating this tool. Until we are done just use our search results to check the inclusion status of your site.
Find out if your site has been cataloged by top search engines for only $8.99.
Below you will see site info taken directly from the URL you entered in real time. This is also known as our URL Breakdown tool and can be used independently of our site info tool.
Page Title
Why Making Developers Liable For Security Vulnerabilities Won't Work Techdirt
Stripped Text Content
This is just a sample of the content found on this website. Please visit the website to read the entire page.
"Techdirt
About
Contact Us
Sign In
Register
My Preferences
Main
Submit a Story
Advertise
<< Throw Your Dirty Dishes Away; You'll Just Make New Ones At Dinner Spammer On The Run Keeps On Spamming >>
Predictions
by Mike Masnick Wed, Oct 12th 2005 8:48am Share This
Permalink.
Why Making Developers Liable For Security Vulnerabilities Won't Work from the it's-a-problem dept
It seems you can't go a few months before someone, somewhere brings up the question of whether or not developers of software products should be liable for the security vulnerabilities in their products. The frustration level is high with buggy software, and so out come the suggestions that lemon laws should apply and execs at companies that make buggy software should go to jail . The problem, though, is that software will remain insecure no matter what's done, and adding liability might actually make the problem worse. However, along comes Howard Schmidt saying instead of companies being held responsible, the actual developers of products should be held liable for security vulnerabilities. This is the same Howard Schmidt who announced 10 months ago that technology would solve the phishing problem in a year . He's got two months to go, and last we checked, phishing was still a growing problem. Should we hold him liable for falsely claiming that phishing would be gone? That's the crux of the problem. No matter how careful a developer is, there are always going to b"
....
read entire page
