{"id":28481,"date":"2023-01-21T13:02:14","date_gmt":"2023-01-21T12:02:14","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=28481"},"modified":"2023-01-21T13:02:14","modified_gmt":"2023-01-21T12:02:14","slug":"bios-bug-on-msi-boards-prevents-secure-boot","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2023\/01\/21\/bios-bug-on-msi-boards-prevents-secure-boot\/","title":{"rendered":"BIOS Bug on MSI Boards prevents Secure Boot"},"content":{"rendered":"

\"Sicherheit[German<\/a>]Small addendum from this week about a bug on a mainboard from MSI. A bug in the BIOS\/UEFI of various board models prevents Secure Boot from being used – even if the BIOS setting is set to On. The Polish student Dawid Potocki recently came across this bug. Users have to change the default BIOS\/UEFI setting in order for Secure Boot to work correctly and actually meet Microsoft's requirements for Windows 11.<\/p>\n

<\/p>\n

Microsoft Secure Boot<\/h2>\n

\"\"According to Microsoft, Secure Boot<\/a> is an important security feature that prevents malware from loading when the PC boots. The security standard was supposedly developed by the PC industry to ensure that a device only boots with software that the OEM (Original Equipment Manufacturer) has deemed trustworthy.<\/p>\n

When the PC is booted, the firmware checks the signature of each start-up software component, including the UEFI firmware drivers (also called option ROMs), the EFI applications and the operating system. If the signatures are valid, the PC boots and the firmware passes control to the operating system.<\/p>\n

The OEM can use the firmware manufacturer's instructions to create \"Secure Boot\" keys and store them in the PC firmware. If UEFI drivers are added, ensure that they are signed and included in the Secure Boot database.<\/p>\n

Microsoft has made Secure Boot mandatory for Windows 11. Critics describe the function as a trap to lock out unwelcome operating systems from computers and to favour Microsoft's Windows. There is always the danger that a faulty signature will prevent devices from booting.<\/p>\n

Voodoo Secure Boot at MSI<\/h2>\n

MSI has now made a mistake with this \"important\" function of Secure Boot, and the incident shows once again that the whole thing is pretty much voodoo. The whole thing became public a few days ago. A blog reader had pointed out the neowin.net article in the discussion area – but the issue had already come to my attention. The following tweet<\/a> links to the article MSI's (in)Secure Boot<\/a> by Dawid Potocki.<\/p>\n

\"MSI<\/a><\/p>\n

In a nutshell: On the affected MSI mainboards there is the option Secure Boot<\/em>, which is supposed to switch on this feature required by Windows 11. The default value is Image Execution Policy -> Always Execute<\/em>.<\/p>\n

\"MSI<\/p>\n

The problem, however, is that there is no check of the operating system images to be booted. It is therefore also possible to boot unsigned components. Dawid Potock writes about this:<\/p>\n

When we open the menu, we can see the disappointing default settings. There is no verification. It is useless. It is only there to meet the requirements of Windows 11. The operating system has no idea that Secure Boot does nothing, it only knows that it is \"enabled\".<\/p><\/blockquote>\n

In plain language: Microsoft's Windows 11 learns \"Secure Boot is enabled\" and is satisfied. Windows 11 is not interested in whether manipulated drivers or loaders have already passed through in the boot sequence and interrupted the security chain (security only exists on paper anyway and Secure Boot is there to \"kneel them\" or cause trouble if something goes wrong with the signatures and machines no longer boot).<\/p>\n

Users can change the settings from \"Always Execute\" to \"Deny Execute\" for \"Removable Media\" and \"Fixed Media\". Then Secure Boot should check again. What is strange is that the options \"Allow Execute\" and \"Query User\" violate the UEFI specification. Potock is not sure what the difference is between \"Allow Execute\" and \"Always Execute\".<\/p>\n

Dawid Potock then discovered that not only his motherboard is affected, but also other models – possibly even from other manufacturers. Potoki has published a list of the allegedly affected MSI motherboards on GitHub<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Small addendum from this week about a bug on a mainboard from MSI. A bug in the BIOS\/UEFI of various board models prevents Secure Boot from being used – even if the BIOS setting is set to On. The Polish … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1319],"tags":[2768,220,69,194],"class_list":["post-28481","post","type-post","status-publish","format-standard","hentry","category-general","tag-msi","tag-secure-boot","tag-security","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/28481","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=28481"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/28481\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=28481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=28481"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=28481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}