Linked by Thom Holwerda on Fri 23rd Sep 2011 22:22 UTC, submitted by kragil
Permalink for comment 490714
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/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



Member since:
2011-01-28
oiaohm,
"You need to read the the full extent of the protection. Boot loader validates everything else above it. Mandatory secure boot would not be a major annoyance as long as you can add the keys for your recovery LiveCD so yes just a minor annoyance. But yes if it left the way it is your recovery LiveCD could be worthless so a major annoyance. No system recovery without ripping harddrive out fun."
I think the threat of bootloader malware is rather exaggerated but I don't deny that it could be helpful in some cases and I don't mind such a feature being added *generically*. As you've said, what is controversial is hard coding MS/OEM keys into the system firmware, such that microsoft/OEMs will be the gatekeepers of this feature. Windows will be trusted by defacto, all other OSes will be hit and miss.
Also, for all the reservations linux users may have, they are the 800 pound guerrilla in comparison to some homebrew OS projects whose chances of getting their binaries signed by hardcoded MS/OEM keys are virtually nil.
Edited 2011-09-25 12:54 UTC