Previous
AOL not liable for unauthorised e-books
News In a ruling that further clarifies whether Internet service providers are responsible for material on their networks, a federal judge ruled that America Online is not liable for the unauthorised posting of some e-books on its Web servers.
[March 19, 2002, 10:40]
IT managers 'should be liable for harbouring cyberterrorists'
News Negligent IT managers in the UK should be liable for harbouring information terrorists, a cyberwarfare expert at the Butler Group said on Thursday. The upcoming US laws will make IT managers legally accountable for leaving vulnerable systems open...
[October 26, 2001, 18:03]
developers not liable
Talkback However, due to the nature and interaction with different software on the same system that leads to insecure situation we should not be held liable. As an example -- door maker built a most secure door possible, but the hinges that were used were...
[January 22, 2007, 6:34]
Companies 'not liable' for Code Red attacks
News Companies that inadvertently spread the Code Red worm to other corporate servers cannot be held liable for causing an Internet attack, say British legal experts. The self-propagating worm, which resurfaced on Wednesday, had raised concerns that...
[August 2, 2001, 14:18]
Law Lords: Banks liable for overseas purchases
News The Law Lords have upheld a Court of Appeal decision that banks and credit companies should be liable for overseas purchases where the goods fail to arrive or are faulty. Business people and consumers purchasing goods from foreign websites, or...
[November 1, 2007, 15:21]
EC wants software makers held liable for code
Talkback I have long been an advocate of software companies being held responsible for their code. Will it happen? I doubt it. OS makers in particular should be accountable for the security of their product. Imagine if windows had any concern for security...
[May 11, 2009, 11:06]
Everyone's liable to make mistakes
Talkback I've been in software development for over 25 years. I've been doing software QA for the last five years. Defects are controllable and are strictly a matter of how the development organization decides to do things.
[October 15, 2005, 4:49]
Everyone's liable to make mistakes
Talkback I am NOT a programmer,nor any sort of technical geek;just a longtime homeuser but my opinion is that outfits like Microsoft or anyone else is simply not careful enough with the creation of their product.NOW--we have a situation where Microsoft is...
[October 14, 2005, 4:49]
software makes should not be held liable
Talkback One question, are you a software developer? I would guess not. Anyone who writes software for Windows will now how hard it is to make software run on all possible software/hardware configurations. This is why anyone who sells software will have a...
[May 11, 2009, 17:41]
Everyone's liable to make mistakes
Talkback Perhaps we should not hold the aircraft or engine -company liable for such problems but rather find out who actually assembled or designed the engine or delivered the material. interesting idea, but then the programmer would have to be the one who...
[October 12, 2005, 18:39]
Viruses: Could your business be liable?
News Could your business be liable? This greatly increases the risk that a business which fails to implement adequate antivirus measures could find itself liable for passing the virus and emails on to another user.
[January 6, 2004, 9:25]
EC wants software makers held liable for code
News Software companies could be held responsible for the security and efficacy of their products, if a new European Commission consumer protection proposal becomes law. Commissioners Viviane Reding and Meglena Kuneva have proposed that EU consumer...
[May 8, 2009, 16:29]
Tories liable to compensate ID scheme vendors
News A Conservative government would have to compensate suppliers of the National Identity Scheme for lost profits as well as costs if it cancelled the project. To guarantee these payments knowing that a future Conservative government has already said...
[May 29, 2008, 8:48]
Everyone's liable to make mistakes
Leader When software goes wrong, it's natural to look for a culprit — especially when the wrong software has caused very bad things. Howard Schmidt, who used to advise the American government on computer security, has an answer: make the developers...
[October 12, 2005, 15:10]
Google cleared in defamation suit
News The high court has ruled Google is not liable for defamatory comments found in its search results, saying the company facilitates access to the information but is not its publisher. The school argued that a posting on the Digital Trends forums...
[July 21, 2009, 15:13]
Like it
Talkback : I can't say I agree with the idea of software developers being liable for software they've constructed It is the organisation who are actually selling the software and saying it will do xyz, that are liable for whether the software does what it...
[May 12, 2009, 8:34]
Developers 'should be accountable' for security holes
Talkback Anyone who works in software security (and has a clue) would never put themselves in a position of being personally liable for certifying a piece of software as being "secure". While he's at it he should demand that automotive engineers certify...
[October 13, 2005, 2:39]
Developers 'should be accountable' for security holes
Talkback If Developers should be liable for security holes then individuals at ALL levels of government should be liable for failures of their departments. Holding developers liable is ridiculous. Look at the players in the FEMA debacle for example.
[October 12, 2005, 18:33]
Judge dismisses suit against eBay
News A California state judge ruled on Thursday that eBay is not liable for the sale of fake sports memorabilia on its auction site. The group argued that eBay was liable under a California law that requires sellers of sports memorabilia to provide...
[January 19, 2001, 9:50]
Developers 'should be accountable' for security holes
Talkback The company should be liable for flaws -- and not only security flaws. It does not make sense to make developers liable for many reasons, one of the most important being that to come up with secure and bug free code you need a good organization...
[October 12, 2005, 15:47]
