News for hackers. Stuff that matters.
Re:MSI's (In)Secure Boot by jeroenhd on Monday January 16, 2023 @06:44PM (#34407124)
Most people are going to install Windows and Windows works out of the box with secure boot enabled. Most other people will use a popular distribution like Ubuntu or Fedora which work out of the box with secure boot enabled.

I doubt people installing their OS will run into this. Even still, the firmware contains the ability to prompt the user about secure boot failures, so if you're going to neuter it, at least pick that as the default option so people notice.

Instead, my suspicion is that these policies are in place so non-OS firmware can run, such as firmware update tools for upgrading the BIOS itself or perhaps management chips/HDDs/SSDs/peripheral controllers. If I were to lock down my previous laptop with secure boot, HP's firmware updates would no longer be able to run without enrolling their signature keys.

Re:MSI's (In)Secure Boot by ollien on Monday January 16, 2023 @07:00PM (#34407272)
> Most other people will use a popular distribution like Ubuntu or Fedora which work out of the box with secure boot enabled.

I installed Fedora on a Thinkpad recently and it most definitely did not work OOTB. I had to enable the third party cert in the BIOS. Not sure about other vendors

Re:MSI's (In)Secure Boot by wmf on Monday January 16, 2023 @07:24PM (#34407489)
Yeah, unfortunately Lenovo has moved on from secure boot to super-secure Windows-only boot.
Re:MSI's (In)Secure Boot by Conan_Kudo on Monday January 16, 2023 @08:25PM (#34408025)
It's a Microsoft thing. "Secured-core" PCs are becoming a thing, and Lenovo selling primarily to businesses became one of the first. If you haven't seen it yet from other OEMs, you will soon. :(
Re:MSI's (In)Secure Boot by zinekeller on Monday January 16, 2023 @07:22PM (#34407479)
It's just Lenovo to be honest.
Re:MSI's (In)Secure Boot by prmoustache on Tuesday January 17, 2023 @02:56AM (#34410140)
Aren't you sure what your talking about is not the key validation for the key used by the kernel to dynamically sign compiled DKMS modules ?
Re:MSI's (In)Secure Boot by Avamander on Tuesday January 17, 2023 @05:15AM (#34410911)
It's part of Secured Core spec to reject the 3rd party root. Same with other vendors implementing it.
Re:MSI's (In)Secure Boot by gjsman-1000 on Monday January 16, 2023 @06:46PM (#34407140)
> If I were to lock down my previous laptop with secure boot, HP's firmware updates would no longer be able to run without enrolling their signature keys.

Well that's... really dumb and shows why OEM's are terrible at security, as there isn't a reason I am aware of on why Secure Boot can't trust two keys simultaneously (one for OS and one for vendor). Heck, Microsoft themselves seems to do it with "Windows + 3rd Party UEFI CA."

Re:MSI's (In)Secure Boot by jeroenhd on Monday January 16, 2023 @08:08PM (#34407889)
I suppose I _could_ sign the extracted UEFI loader manually to make the updates work, but that pretty much breaks the automated process and requires me shuffling the boot order manually after the failed boot. Not a great solution and that assumes the UEFI image doesn't do something weird like its own signature.

It makes sense to use UEFI programs to update the UEFI, but secure boot adds a layer of complexity on top of that which requires taking special notice.

Re:MSI's (In)Secure Boot by vladvasiliu on Monday January 16, 2023 @11:46PM (#34409256)
I'm not one to praise my HP machines, but this is one area where I've had zero issues with them.

Are you by chance using "consumer" models? My "enterprise" level PCs, starting with models of the intel 6th gen era, up to 12th gen, have been smooth-sailing secure-boot wise. I didn't interact with any older model.

I run Arch (which isn't signed by MS like Ubuntu / Fedora) and sign the bootloader with my own key that I've generated myself. On some computers where I need to dual-boot with Windows, I've signed MS's Windows key (not the third-party one) with my key. Everything has always worked fine, including automatically upgrading the UEFI over the network from the UEFI itself, installing Windows 11, etc.

I never needed to disable Secure Boot (apart from initial Arch install) or sign any HP-specific key. The only thing that "breaks", but that's expected and HP warns you during the update, is that whatever relies on measuring the UEFI image will break. That's typically the case with BitLocker (mentioned specifically) and LUKS.

Re:MSI's (In)Secure Boot by iforgotpassword on Tuesday January 17, 2023 @02:40AM (#34410061)
Can't say anything about secure boot, but we have HP at work and the BIOS is the most brain damaged thing ever.

Just the built-in update process... It doesn't always find the latest version, ie lags behind the website by weeks sometimes. Then when it checks for updates and finds there isn't a new version available, it offers you to downgrade to the previous version but apart from the text being a bit different, the blue button below still says "UPGRADE", so the first time I accidentally started a downgrade. So it started flashing the BIOS, then something like the nic firmware, then came to the Intel ME firmware and suddenly said "uh no, I cannot downgrade that" and just aborted the whole update process. No idea if it would've kept flashing other stuff after the ME, and evidently it didn't break anything, but holy crap that looks like a half-arsed feature.

Re:MSI's (In)Secure Boot by jeroenhd on Tuesday January 17, 2023 @04:28PM (#34419502)
HP Probook 450 G2, I believe that's part of the business lineup. I run it as a home server these days and after many years they finally stopped making updates for that thing, so I can't say I care too much.

There's a very good chance they changed their update procedures, but when I last ran the update I needed to run a special .efi file that would handle the flashing.

For what it's worth, I consider the HP Probook line to be excellent in terms of both durability and support. They may not be three millimetres thick like their competition but design wise they're quite alright, the machines are quite sturdy for their weight class. Their repair guide has very detailed step by step instructions on how to replace parts as well as listings of known replacement part product numbers which are great for finding replacement fans.

I think I've received at least seven years of UEFI updates, which is about 6 more than I expected for the price. HP graphics drivers actually got updates and they offer a way to keep track of updates through email without having any crapware installed. The UEFI itself is also one of the best I've used, miles ahead of the Lenovo one. The ability to browse EFI partitions and navigate to an image of your choice is excellent and I can't believe I haven't seen this on other brands.

Enrolling keys, however, required clearing the certificate cache. I could reset it back to factory settings and load the default Microsoft keys, but for their custom updaters I would need to disable secure boot or find the key they used and import it. Hardly a deal breaker, that's just how Secure Boot is supposed to work, but still something to think about when designing an updater process.

Re:MSI's (In)Secure Boot by vladvasiliu on Wednesday January 18, 2023 @01:56AM (#34424120)
Interesting, I have a 430 G2 I occasionally use as a media player, and it's the only one on which I never attempted to install anything else besides Ubuntu or Windows, so never had to deal with Secure Boot. I actually don't even know if it's on or off.

On newer models, you also have to "clear the certificate cache" to enroll your own keys. But there's an option on the same page like "reset to factory defaults", which reloads the MS keys and such.

The manual UEFI update is indeed a bit cumbersome, especially since the downloaded archive seems to be some windows executable. And, in my case, I don't remember I could navigate in the partitions, it would just complain that it couldn't find the update if it wasn't in the right directory.

Re:MSI's (In)Secure Boot by marcosdumay on Monday January 16, 2023 @07:49PM (#34407733)
> Most people are going to install Windows and Windows works out of the box with secure boot enabled.

Hum... I can't recall a single person that brought a personal computer and then installed Windows on it on the last 2 decades.

That happens with corporate computers, sure. But sysadmins know how to enable secureboot.

Re:MSI's (In)Secure Boot by gambiting on Monday January 16, 2023 @08:21PM (#34407992)
I work in tech(professional programmer) and I frankly don't know anyone who runs anything other than Windows. I guess it just depends what area of tech you're in. And yes, myself and all my friends built our PCs by hand and installed windows on them ourselves - I'm glad secure boot wasn't getting in the way of that.
Re:MSI's (In)Secure Boot by greyw on Tuesday January 17, 2023 @05:39AM (#34411024)
Must really depend on the field. People around me are mostly running gnu/linux or macos (roughly 80/20 split). I think some have dual-boot with windows.
Re:MSI's (In)Secure Boot by jeroenhd on Monday January 16, 2023 @08:11PM (#34407906)
All my friends, even developers, use their PC's mostly for gaming and "office" work (text editing for work and hobbies). Most of them are capable enough to run Linux, but most of them prefer Window as the default. They often run Linux at work for development, but stick to good ol' Windows 10 at home. I can't fault them for their preferences, even though I'm definitely Linux-first myself.
Re:MSI's (In)Secure Boot by jonathanstrange on Tuesday January 17, 2023 @05:06AM (#34410864)
What he meant is that people don't install Windows, it's almost always pre-installed. Most PC nowadays don't even come with a physical copy of Windows, only with the pre-installed OEM image.
Re:MSI's (In)Secure Boot by jeroenhd on Tuesday January 17, 2023 @04:33PM (#34419581)
The people I was referring to built their own PC. The people who do that are a minority for sure, but they're going to be the customer for most of these specially branded MSI boards.
Re:MSI's (In)Secure Boot by NavinF on Tuesday January 17, 2023 @02:30AM (#34410011)
> I can't recall a single person that brought a personal computer and then installed Windows on it on the last 2 decades.

Interesting bubble. 50% of the programmers I know installed Windows and the rest use prebuilts that came with Windows. Same 50/50 statistics for gamers in my bubble.

Re:MSI's (In)Secure Boot by sokoloff on Tuesday January 17, 2023 @03:44AM (#34410408)
> Even still, the firmware contains the ability to prompt the user about secure boot failures, so if you're going to neuter it, at least pick that as the default option so people notice.

People don’t read error messages. By this I don’t mean that no one ever in the history of the universe has, but rather that a high percentage will just contact tech support or RMA the board as broken. I can’t really blame mobo manufacturers from making the choice that minimizes tech support costs from consumers who won’t read and understand an error message.

Re:MSI's (In)Secure Boot by mmis1000 on Tuesday January 17, 2023 @09:17AM (#34412599)
> Most people are going to install Windows and Windows works out of the box with secure boot enabled.

Any windows version after windows 10 isn't going to work nicely without extra process if you want to do a usb install. Because the ISO file already exceed FAT 32 4GB limit.

And DVD burner? Who still have them these days?

So most people will going to use one of these 3 party tools. And some of them will use an old version tool, fail, going into support queue.

Re:MSI's (In)Secure Boot by smileybarry on Tuesday January 17, 2023 @09:23AM (#34412679)
It will because Microsoft’s own Media Creation Tool splits the .WIM installation image accordingly since Windows 10 came out.[1]

1: This is what the media creation tool essentially does, but automatically: https://learn.microsoft.com/en-us/windows-hardware/manufactu...

Re:MSI's (In)Secure Boot by jeroenhd on Tuesday January 17, 2023 @04:32PM (#34419557)
My default method of installing Windows is extracting the ISO file to a FAT partition and that has always worked without trouble for me. The official Microsoft tool does some extra magic to the drive (I think it also fixes the partition table for you) but I've rarely needed to run that.

You don't need to store the entire ISO file on the drive as a 4GiB+ file, as long as the contents can be extracted onto FAT32 the installer can be booted.