Friday, September 05, 2008
Another Google Chrome Security Flaw Identified
Another Google Chrome Security Flaw Identified: "critical buffer-overflow"
For Pete's sake. We were talking about this just last weekend when the Bixby Creek gang got together at Donner Lake for the long weekend.
The question then was, "Why don't the software engineers at Microsoft check for buffer overflows when they're designing their software? Especially now when they should be overly aware that they have an ongoing problem?" Followed by, "Why don't the QA mavens at Microsoft check to make sure the software engineers have checked for buffer overflows?"
For. Pete's. Sake. People. Microsoft. Google. Anyone writing code.
This is a known issue with known solutions.
Sheesh.
For Pete's sake. We were talking about this just last weekend when the Bixby Creek gang got together at Donner Lake for the long weekend.
The question then was, "Why don't the software engineers at Microsoft check for buffer overflows when they're designing their software? Especially now when they should be overly aware that they have an ongoing problem?" Followed by, "Why don't the QA mavens at Microsoft check to make sure the software engineers have checked for buffer overflows?"
For. Pete's. Sake. People. Microsoft. Google. Anyone writing code.
This is a known issue with known solutions.
Sheesh.
Labels: app, internet, webstuff
: views from the Hill
Bertold Brecht:
Everything changes. You can make
A fresh start with your final breath.
But what has happened has happened. And the water
You once poured into the wine cannot be
Drained off again.
Everything changes. You can make
A fresh start with your final breath.
But what has happened has happened. And the water
You once poured into the wine cannot be
Drained off again.