Linked by Howard Fosdick on Mon 22nd Oct 2012 04:51 UTC
Permalink for comment 539874
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2010-06-01
It was there for over 2 years and was due to developer laziness.
It was a misunderstanding, an error, do you know the exact circumstances around the issue to know for a fact that it was down to laziness ? From everything I have read about the incident it seems to be a misunderstanding rather than just laziness, shit happens and it happens in both closed and open platforms, that's reality, no such thing as perfect code, because humans are not perfect.
At least on open platforms if you stumble on shit you can clean it up, in the closed world if you stumble on shit, you have to wear it until the manufacturer cleans it up, that's the difference.
It pretty much puts the "many eyes" into the category of "Myth".
Bullshit !
How many cracks or system compromises were attributed to this ? afaik 0, none.
Sure after this had been revealed there was a lot of upgrading / key regenerations, but before it was known it looks like no one had stumbled across it, so in reality it neither proves or disproves either theory, but I love the fact that you think obscurity provides you better protection. Especially considering Windows your beloved platform of choice has been the most compromised platform on this planet and it is one of the most closed platforms.