Previous
Developers 'should be accountable' for security holes
Talkback Well this will certainly have the effect of getting rid of security holes. Security holes are often the function not of developers work but of managements, and/or software integrators. The code works as its supposed to, the problem is that...
About: Developers 'should be accountable' for security holes
[October 12, 2005, 16:36]
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. Look at the players in the FEMA debacle for example. Holding developers liable is ridiculous.
About: Developers 'should be accountable' for security holes
[October 12, 2005, 18:33]
Developers 'should be accountable' for security holes
Talkback Consumers should be (and ultimately are, through lower security) held liable for security holes in software. The fact of the matter is, many security holes exist because companies need to be first to market with a particular idea, or risk not...
About: Developers 'should be accountable' for security holes
[October 12, 2005, 16:27]
OpenOffice patches three security holes
Talkback "OpenOffice patches three security holes" I assume this is only on the windows version, since it can gain access to the entire system. Linux isn't integrated" like M$ is, so is not as vulnerable or as buggy as M$ .
About: OpenOffice patches three security holes
[July 5, 2006, 14:23]
Security holes exposed in several major browsers
Talkback these freakin M$ Corp adverts at the side of this panel really piss me off big time bunch of 5 knuckle shuffle merchants they are .any how gripe out the way . If more time and effort was spent catching the little twits that spend there time...
About: Security holes exposed in several major browsers
[October 21, 2004, 23:06]
Developers 'should be accountable' for security holes
Talkback We are always compromising functionality, security, performance, and staffing all to fit within a given timeframe and budget. Mr. Howard Schmidt has no clue about software development and the dynamics that go into developing a system.
About: Developers 'should be accountable' for security holes
[October 12, 2005, 17:45]
Developers 'should be accountable' for security holes
Talkback As much as I'd like to be accountable, the level of security is one of many variables in the specification of software. If the software isn't intended to be in a security concious environment the security aspects are often left out for cost reasons.
About: Developers 'should be accountable' for security holes
[November 15, 2005, 19:19]
Nokia admits multiple Bluetooth security holes
Talkback Shouldn't a refund be in order?
About: Nokia admits multiple Bluetooth security holes
[February 10, 2004, 13:49]
Nokia admits multiple Bluetooth security holes
Talkback Unfortunately, the only way to 'fix' this bug is to disable the Bluetooth on the phone. Setting the phone to non-discoverable does not help, as tools such as @stake's Redfang or Shmoo Group's Bluesniff can still find the phone.
About: Nokia admits multiple Bluetooth security holes
[February 10, 2004, 13:11]
Nokia admits multiple Bluetooth security holes
Talkback I have a Nokia 6310i. It seems ok that there are few of us out there who might be affected, but Nokia's this kind of treatment of its customers cannot be fair. Nokia 6310i is the high end of its class and I have paid more to purchase this high-end...
About: Nokia admits multiple Bluetooth security holes
[July 19, 2004, 16:33]
Nokia admits multiple Bluetooth security holes
Talkback So if you are in public, don't use bluetooth! why would anyone want to take their mobile phone into public? just leave it at home and use a pay phone.
About: Nokia admits multiple Bluetooth security holes
[February 10, 2004, 12:46]
Developers 'should be accountable' for security holes
Talkback Mr.Schmidt proposed "solution" is at best simplistic and at worst shows utter ignorance about the subject of software security. So going by Mr. Schmidt's logic, if tomorrow there is a manufacturing defect in, say, an automobile component from a...
About: Developers 'should be accountable' for security holes
[October 13, 2005, 0:03]
Developers 'should be accountable' for security holes
Talkback But they don't want to deal with security systems that can lock them out of their systems, they can't remember passwords, and don't like stiff restrictions on the use of their own software. When people pay a premium for security, and make the...
About: Developers 'should be accountable' for security holes
[October 13, 2005, 0:57]
Developers 'should be accountable' for security holes
Talkback Seeing that lawyers have squeezed every drop of live out of doctors, they need a new target. What better than the growth industry of our generation? With this effort, there can be limitless lawsuits and endless hours of billing.
About: Developers 'should be accountable' for security holes
[October 13, 2005, 2:09]
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". Likewise, security consulting companies generally only issue "verifable...
About: Developers 'should be accountable' for security holes
[October 13, 2005, 2:39]
Developers 'should be accountable' for security holes
Talkback Negligent Software Developers are not the only cause of security holes. Likewise, it is appropriate to hold software companies, not software developers, liable for security holes. As a professional software engineer, I strongly disagree with the...
About: Developers 'should be accountable' for security holes
[October 13, 2005, 4:12]
Developers 'should be accountable' for security holes
Talkback Security is moving target dumber. He is a cowboy. It is never completly secure, if it is toda, it will not be tomorrow. The only way a machine can be secure is to turn it off and put it in 10 meter thick box, send it to space.
About: Developers 'should be accountable' for security holes
[October 13, 2005, 7:41]
Developers 'should be accountable' for security holes
Talkback But if he is willing to put his name on the line, and since he has a security consulting firm, I would expect that if ANY recommendation he makes to a client does not provide 100% security for that client, he will provide FULL restitution for any...
About: Developers 'should be accountable' for security holes
[October 13, 2005, 10:53]
Nokia admits multiple Bluetooth security holes
Talkback It would be a start if the phones did not have bluetooth setting as default 'on' mode!
About: Nokia admits multiple Bluetooth security holes
[February 10, 2004, 9:42]
Developers 'should be accountable' for security holes
Talkback Are they equally liable for not finding security holes? Does he believe that developers have the ultimate decision making authority to release software into the marketplace? What about the role of Software QA Engineers?
About: Developers 'should be accountable' for security holes
[November 4, 2005, 21:04]
