content: Its not.  This was caused by a bug in the firmware, not new firmware.  Most people, (even a lot of IT/ tech savvy people) don't really understand what UEFI is exactly or the issues with it.  UEFI is a specification for a booting protocol (and I suppose API).  Created by Intel in the early 00's, it was intended to replace the old "IBM compatible" boot sequence.  There really isn't much to complain about, (other than it's slightly more complex than the old boot it someways, although its easier in others.) Where most people take issue is that Microsoft got Safeboot added to the spec.  They then strong armed the motherboard manufactures to implement safeboot or they couldn't use the "Ready for windows 8" (or w/e the fuck it said) sticker.  It's all about certification.  It is left up to the firmware implementer which non-microsoft signatures they ship will (the spec is only to make sure you run signed content, could do same thing with linux/BSD), and if they let the user disable this feature.  Asus, afaik, always does, and the instructions are mentioned in the article.  Asus also lets users and OEMs add their own keys if they choose.