Linked by Thom Holwerda on Fri 23rd Sep 2011 22:22 UTC, submitted by kragil
Permalink for comment 490682
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/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2009-05-30
Depends on your OEM still providing updates. justSomeGuy.
Its the number 1 step to load the bootloader latter on in the process there are some internet links.
The Platform Key is OEM hardware makers that protects the KEK that contains the OS bootloader and other need firmware parts that are approved.
Key issues here the power of updating the KEK goes to the hands of the Hardware maker.
So yes they can bust things. Allowed in KEK contain approved signing keys for bootloaders.
So yes Microsoft needs to update there signing key Hardware maker decides only to update on todays hardware. People get a service pack update that changes the boot loader their computer dies because UEFI no longer will load the Windows loader.
This is a god darn land mine. Customer needs to have the means to insert and remove allowed keys and see the allowed keys.
Change able as long as hardware maker is supporting the hardware you have. Reason why I said 5 years then screwed.
Other issue is black list. Disallowed malware hashes those should be inspect-able as well.