[How to] Zorin and Secure Boot

What is Secure Boot?
Secure Boot is a measure to secure the boot process against tampering.

How is it set up?
Zorin supports Secure Boot enrollment during installation. Make sure to set Secure Boot as enabled in the UEFI before starting the installation.
If you run into any problems, reset the UEFI and/or Secure Boot to factory defaults/clear any keys, and disable & re-enable Secure Boot. Make sure to enable the Microsoft certificate.

During the installation wizard, you'll be asked to provide a Secure Boot password, it needs to be 8-16 characters. It does not need to be complex or stored for a long time, however during the first reboot after installation you'll be greeted with a blue screen. After 10-15 seconds the machine might or might not continue booting, so it is important to 'catch' it in time.
The second option should read 'Enroll MOK', press Enter.
The first option should read 'view key 0', press Enter.
Here you can see the details about the key. Pressing Enter again brings you back to the previous screen.
The second option should read 'Continue', press Enter and confirm enrolling with [yes].
Type in the previously set password. After this, the password can be discarded.
Press [Reboot] and start using Zorin!

You can check the status of Secure Boot while logged in, by running mokutil --sb-state. It should return:
SecureBoot enabled
After enabling Secure Boot and finishing up your installation, make sure to disable booting from an external USB, and locking down the UEFI with a strong password to further reduce the attack surface.

2 Likes

Is this still correct?

I've installed Zorin on two devices, moving away from Windows, and have never seen an option to provide a Secure Boot password during installation.

I also couldn't find any documents on secure boot in the 'Zorin OS Desktop Guide' documentation.

1 Like

Hi and Welcome. For a good extensive look at Secure Boot I recommend reading this post:

and as Zorin 17_is based on Ubuntu 22.04:

1 Like

Secure boot is a Microsoft feature, and is not necessary or required for Linux, unless your operating a high security computer in the government sector. For a person who just operates a computer from home, all Secure Boot will do, is cause you loads of problems, where you will be pulling your hair out.


2 Likes

Much agreed with StarTreker - just to see if I could do it, I got it working with my laptop but.. every Nvidia update needed a password and then booting into the secure boot to proceed with the install and it was just an absolute headache..

Home users - definitely would suggest leaving SecureBoot off; it only causes more troubles than it helps.

4 Likes

The problem to the Secure Boot password not appearing during Zorin install was that, on boot, I booted from 'USB - [manufacturer]', instead of 'UEFI: [manufacturer], Partition 1'.

Once I booted using the UEFI option, the option to enter a Secure Boot password on Zorin install appeared.

Posters after me were right, though, in that I asked how to do this, not should I do this. All a part of the learning experience. Special thanks to @swarfendor437; the first link on EFI boot loaders was really educational.

2 Likes

I'm sorry but I'm pretty saddened that this myth is still doing its rounds.
Secure Boot is not a Microsoft feature. It is a general feature, Linux was just late to the game and there isn't any distro that has implemented it entirely yet. Zorin is very close, but no cigar at this point.

Everyone and their mother should use Secure Boot, (as well as Measured Boot, otherwise it is still incomplete and thus insecure), since a Linux desktop without it, is much less secure than any Windows installation, even with Full Disk Encryption enabled. This is because without SB&MB, it is trivial to infect the kernel and install a keylogger, which scoops up the FDE passphrase the next time the legitimate user boots the system. Yes, this requires at least physical access once, staying unnoticed, to the machine to manipulate it.

But with the advent of Artificial Intelligence, those kind of attacks are steadily moving from "knowledgeable hacker" to "script kiddie" and now lowering further to "random university dorm creep".
To my opinion, these attacks have never really been only reserved for nation state attackers. Especially with certain professions, like doctors, psychologists, lawyers or security researches, just using FDE is in my opinion insufficient, because it could be that a person is an interesting enough of a target to warrant such an attack. And as I mentioned, I only see the possibility of that increasing since it's becoming more and more available to the average person to execute such an attack.

Yes, Microsoft has a very strong foothold on SecureBoot, since hardware manufacturers basically only ship TPM-hardware with Microsoft keys by default. That is all. But Secure Boot is not Microsoft-exclusive, as Zorin proves this with very reliable MOK enrollment.

This kind of understanding and opinions on these security measures will keep Linux from achieving its full potential. I simply refuse to use an OS that is less secure than Windows, and I'm a nobody. I can already expect comments "you're not interesting enough, you don't need that".

Thank you for your opinion, but I lay those comments beside me. To my opinion, those statements also strongly undermine active Linux development to become an actually safe and mature desktop OS that is as secure, if not more secure than Windows. Because you directly or indirectly tell others, users and developers, that there is no need desire to have Secure Boot/Measured Boot on Linux, which has led to the situation where we are right now;

Linux is still 10 years behind Windows and Mac, while all the tools and methods are available to achieve this. It's just that no distro has fully implemented this, outside of Arch Linux maybe, if someone chooses to set it up that way. (I played around with Arch, and achieved Secure Boot + Measured Boot but I like a Debian-based distro more).

Zorin just needs to implement UKI, then it's basically there. I made a thread in the feedback section: Zorin is really good; it's only missing a Unified Kernel Image

Some closing remarks.

  • I'm aiming mainly for personal/professional desktop(laptop)/office use. If Zorin wants to become the Windows alternative for small and medium business, or local governments, this should be implemented. If not yet, I expect any CISO worth their salt to require this today or tomorrow.
  • Gaming for me is totally out of scope related to this security requirement. I know that makes a lot of stuff more difficult, but you can just game on a separate game PC with Windows or Bazzite or use a game console.
  • Same with Dual Boot or other requirements that make it more difficult to achieve.

MOK should be made password-less maybe though, to simplify software updates. Other than that, having to run another MOK enrollment, even once a month, after an update, is not a problem to me.

2 Likes

I am new to Linux but, I have to say I find a lot of helpful information on this blog and others . Thank you all . :+1: