Skip to content

Commit 337f818

Browse files
docs: add note about new Secure Boot key (#88)
1 parent 5156d9f commit 337f818

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

content/FAQ.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,7 @@ permalink: /faq
4545
- [How do I change my DE?](#change-de)
4646
- [Why doesn't DRM content (spotify, netflix etc.) work in Trivalent?](#trivalent-protected-content)
4747
- [How do I enable kernel modules?](#enable-kernel-modules)
48+
- [Why am I being asked to enroll a Secure Boot key?](#new-key)
4849

4950

5051
### [Why secureblue?](#secureblue)
@@ -301,3 +302,12 @@ DRM-protected content is available in trivalent, however it is disabled by defau
301302
{: #enable-kernel-modules}
302303

303304
Some functionality requires you to enable extra kernel modules that are disabled by default in secureblue. Modules can be enabled by running `ujust override-enable-module`. For instance, mounting SMB shares requires the `cifs` and `netfs` kernel modules. To load them, simply run `ujust override-enable-module cifs` and `ujust override-enable-module netfs` then reboot.
305+
306+
### [Why am I being asked to enroll a Secure Boot key?](#new-key)
307+
{: #new-key}
308+
309+
As part of a move to unify our supply chain, secureblue is moving off of [uBlue](https://universal-blue.org)'s kernel cache and akmods. This has both practical and security advantages, and paves the way towards further kernel security improvements in the future. This change includes a transition to a new secureblue Secure Boot key. You must enroll this new key to prevent issues loading kernel modules:
310+
311+
```
312+
ujust enroll-secureblue-secure-boot-key
313+
```

0 commit comments

Comments
 (0)