Linked by Howard Fosdick on Thu 6th Dec 2012 05:26 UTC
Permalink for comment 544521
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2011-01-28
bornagainenguin,
Implementation bugs can be a problem. I was actually referring to how we effectively have one key (microsoft's) controlling the hardware/firmware secure features on every consumer computer from now on is an inherently poor security design. This is not something a competent standards security engineer could have signed off on unless there were ulterior motives. Of course they were working for microsoft so there you go.
I agree that finding an implementation vulnerability will be an embarrassment, but realistically what do we think will happen? I believe they'll just fix the implementation & release patches, and then continue down the same path.
Edited 2012-12-07 16:00 UTC