Advertising
seattlepi.com
Subscribe | Contact Us | Seattle Post-Intelligencer
Jump to:  Weather | Traffic | Webtowns | Mariners | Seahawks | Sonics | Calendar
BUSINESS ?

OUR AFFILIATES
NWsource
KOMO
MSNBC
digitalcity
seattlepi.com Microsoft Blog

September 16, 2003

Readers' virus responses

To close the loop on this for the time being, here’s a quick recap of reader response to our story last week on the question of liability for software flaws and computer viruses. I went back through the voice-mail and e-mail messages I received, as well as the comments posted on this weblog, and attempted to put them into categories based on the sentiments they expressed.

Aside from this being a completely unscientific sample of public opinion, putting the responses into categories is also an inexact undertaking, because of the nuances of the debate. Keep that in mind as you read these rough totals:

* Sixteen people, or 32 percent of the approximately 50 people who responded, generally favored increasing the exposure of Microsoft and other software makers to liability for flaws exploited by writers of viruses and worms. Here’s an excerpt of one message from this camp, left by a reader on my voice mail:

"I thought (the article) was a little easy on them. First of all they’ve known about this danger for many years. They know it far better than the hackers do. ... There is nothing that can be made absolutely safe, not even a tire, however Microsoft has completely over the years neglected safety considerations."

* Eighteen people, or 36 percent, said holding Microsoft liable would be inappropriate, given that a criminal is the one ultimately causing the problem. Many people on this side of the debate took serious issue with the Firestone tires analogy used by software security expert Bruce Schneier, as quoted in our story. They included reader Peter Duniho, who sent this e-mail message:

When Firestone can be held liable for tire failure after someone punctures it intentionally with a knife, then it will make sense to start holding software companies liable for failures that occur after someone intentionally breaches the security safeguards.

How secure is the lock on your door? If a burglar picks the lock and steals your TV, do you think it will be reasonable to sue the lock company for not protecting you against the burglar?

The only thing newsworthy about this issue is that so many people are willing to ignore common sense and take out their frustrations on an innocent party. That’s just human nature of course, but it doesn’t make it right.

* The remaining 16 people offered various comments without taking specific stands on the question of liability. One reader, for example, asked who would be held accountable for security problems in open-source software created by a larger community and not necessarily backed by a corporate entity. Another wrote that he wasn’t sure whether Microsoft should be held liable for the effects of viruses, but that computer users should actively seek out alternatives to Microsoft products to alert the company to the severity of consumer concerns over security.

Which e-mail service did this reader use to send this message? Microsoft Hotmail, of course.

Posted by Todd Bishop at September 16, 2003 01:49 PM
Comments

After reading the in general responses to this report, I still find it amazing that people want to put the blame on Microsoft. After I finished booting up my W/XP, I headed for the W/Update page and downloaded 16 patches. Since then I have downoladed two more. Now this does not sound like a company that is being irresponsable to their program. They find a problem and fix it. Then it is up to us, the consumer to take the appropriate action.
Since there will always be people that like to cause one kind of a problem or an other, it is up to us to keep the program that we bought secure from them.
OR, we can whine and complain and get zapped. Our choice!!!!!
Nadine

Posted by: Nadine Taylor at September 16, 2003 05:03 PM

You admit that you had to download 16 patches, and you're not blaming Microsoft for the need for those patches? Microsoft might not make the virus, but they are repeatively making defects in their products. As Bruce Schneier put it "Liability is how we figure out what portion of the responsibility falls on the software company. It's certainly not 100 percent, but it's just as certainly not 0 percent. .... What liability does is ensure that the companies in the best position to fix the problem have the financial incentive to do so." Imagine software makers who being liable actually made software that *wasn't* defective.

Posted by: Kuwanger at September 27, 2003 04:34 PM
Post a comment









Remember personal info?







  ARCHIVES
November 2005
S M T W T F S
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30      

Monthly archive
· September 2005
· August 2005
· July 2005
· June 2005
· May 2005
· April 2005
· March 2005
· February 2005
· January 2005
· December 2004
· November 2004
· October 2004
· September 2004
· August 2004
· July 2004
· June 2004
· May 2004
· April 2004
· March 2004
· February 2004
· January 2004
· December 2003
· November 2003
· October 2003
· September 2003

Recent Entries
· Microsoft executive pay
· Windows in a Palm
· Audio Extra: Gates, Ballmer on Microsoft's future
· Gates, Ballmer Q&A
· Xbox exec on Revolution
· PDC behind the scenes
· Mac BU in Microsoft reorg
· Ballmer Q&A: Online Extra
· Allchin on 'hard lessons'
· Major Microsoft reorg

What is this?

  FROM THE P-I
· Former Microsoft manager sentenced to 22 months for embezzlement
· Microsoft bets more online
· Yahoo blasts Microsoft acquisition effort as 'stupefying'
· Lawmakers look into Yahoo-Google ad partnership
· Netflix to stream live on Xbox 360
· Icahn again takes aim at Yahoo board
  LINKS

News and information:
· WinInfo
· Microsoft Watch
· Directions on Microsoft
· WinInsider
· ActiveWin
· KOMO News: Microsoft
· NetworkWorld: Microsoft
· Google News: Microsoft
· Yahoo News: Microsoft
· Microsoft Research News
· Microsoft PressPass
· Channel 9
· Anti-Microsoft News
· NewsForge: Linux News
· Linux Today
· Mac News Network
· Mac Daily News
· Washington Post Filter
· G.M. Silicon Valley
· OS News
· Gillmor Gang

Blogs about Microsoft:
· Microsoft Monitor
· Unofficial MSFT Blog
· IW Windows Weblog
· Xbox 2 Blog
· Inside Microsoft
· CNet Microsoft Blog

Computer Security:
· Microsoft Security
· Wash. Post Security Fix
· Microsoft Security Response Center Blog
· Be Careful Out There
· Security Awareness Blog
· Bruce Schneier's Blog
· eWeek Security News
· Larry Seltzer
· Symantec Security Resp.
· McAfee Virus Information
· CNet Security Blog
· Security Focus
· Kaspersky Lab Analyst's Weblog
· Michael Howard (MSFT)
· Stephen Toulouse (MSFT)
· Network World Security
· Planet Security

Microsoft employees:
· Employee Blog Portal
· MS Watch List
· S. Somasegar
· Raymond Chen
· Dare Obasanjo
· Brad Abrams
· Heather Leigh
· Korby Parnell
· Matt Goyer
· Robert Scoble
· Don Box
· Chris Anderson
· Joshua Allen
· Chris Sells
· John Porcaro
· John Montgomery
· Kevin Schofield
· Rick Schaut
· Marc Miller
· Sean Alexander
· Larry Hryb
· Gretchen and Zoë
· Harry Pierson
· Mini-Microsoft

Search-related sites:
· John Battelle
· Greg Linden
· Unofficial Google Blog
· Yahoo! Search Blog
· MSN Sandbox
· MSN Search Weblog
· Google Blog
· Search Engine Lowdown
· Search Engine Watch
· Google Like a Hawk

Browser-related sites:
· Internet Explorer team
· mozillaZine
· Surfin' Safari
· Opera news
· Browser News

Technology Weblogs:
· Dwight Silverman
· Charlene Li
· Joel Spolsky
· Engadget
· Gizmodo
· Corante Apple Blog
· Amy Wohl
· Dan Gillmor
· Simon Phipps
· Buzz Andersen
· Chris Seper
· Hiawatha Bray
· Paul Andrews
· Doc Searls
· Chris Pirillo
· Campbell & Swigart
· Longhorn Blogs
· PDC Bloggers

Antitrust info:
· FindLaw: Microsoft
· DOJ Microsoft site
· Microsoft legal site
· Findings of Fact
· ComputerWorld Report
· Sun legal page
· Dan Kegel's antitrust site

Additional sites:
· Google Microsoft Search
· About Microsoft
· Microsoft User Network
· Tablet PC Buzz
· Living Without Microsoft
· Lockergnome
· WSA
· WashTech
· CyberLodge
· Microsoft Permatemps
· Apache Foundation
· Librenex
· Electronic Frontier Foundation

 
Home | Site Map | About the P-I | Contact Us | P-I Jobs | Home Delivery
 
Seattle Post-Intelligencer
101 Elliott Ave. W.
Seattle, WA 98119
(206) 448-8000

Home Delivery: (206) 464-2121 or (800) 542-0820

Send comments to newmedia@seattlepi.com
©1996-2005 Seattle Post-Intelligencer
Terms of Service/Privacy Policy