Linked by Thom Holwerda on Sat 29th Dec 2012 16:37 UTC
Thread beginning with comment 546701
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, 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:
2006-10-08
Wow, really? Will it prevent malware running as my user from harvesting my data? Will it prevent malware running as my user from participate in a botnet? Will it prevent social engineering?
No? Fat lot of good it does, then. "
But it says "secure" on the box! So it's secure! You don't want to disable it, or you'll catch a virus! :-)
No, honestly: "Secure Boot" emphasizes security during the boot process only. If it would protect against common malware, virus infections, social engineering and human stupidity, it would require a different name, and as repeated in the article several times, "signed by Microsoft". :-)
Of course it adds some protection that may even be useful in MICROS~1 land, but remember that not everyone is using "Windows" or wants to use it, or even wants to deal with it (even if it's just for the purpose of getting rid of the restrictions it implies). The best way would of course be to have an option to revert the UEFI "back to normal" as "Secure Boot" isn't needed to perform an OS boot in the first place. Deals between MICROS~1 (with their idea of how "security" should work) and OEMs will probably prevent such a simple solution...