Skip to content, sitemap or skip to search.

Free Software Foundation

Personal tools
Join now
 
You are here: Home Campaigns Secure Boot vs Restricted Boot Restricted Boot Webcomic Contest winners

Restricted Boot Webcomic Contest winners

by Joshua Gay Contributions Published on Jul 03, 2012 06:27 PM
Congratulations to Erik Steinmann and our thanks to all of our contestants and judges!

The Winning Entry

First runner-up

Second runner-up

Creative Commons License
This work by Simon Giraudot is licensed under a Creative Commons Attribution ShareAlike 3.0 Unported License and derived from works geektionnerd.net.

Third runner-up

This work by Momcilo Medic is licensed under the GNU General Public License.

About Secure Boot vs Restricted Boot

When done correctly, Secure Boot is designed to protect against malware by preventing computers from loading unauthorized binary programs when booting. In practice, this means that computers implementing it won't boot unauthorized operating systems -- including initially authorized systems that have been modified without being re-approved. This could be a feature deserving of the name, as long as the user is able to authorize the programs she wants to use, so she can run free software written and modified by herself or people she trusts. However, we are concerned that Microsoft and hardware manufacturers will implement these boot restrictions in a way that will prevent users from booting anything other than Windows. In this case, we are better off calling the technology Restricted Boot, since such a requirement would be a disastrous restriction on computer users and not a security feature at all.
Document Actions

The FSF is a charity with a worldwide mission to advance software freedom — learn about our history and work.

fsf.org is powered by:

 

Send your feedback on our translations and new translations of pages to campaigns@fsf.org.