Active Entries
- 1: Advent, day 5
- 2: Today's programming silliness
- 3: The highly inaccurate guide to the Eurovision Song Contest 2022 results!
- 4: Bang!
- 5: How not to get people to use a new feature
- 6: Misty creek and eerie fog
- 7: Remember...
- 8: Brexit means arrows?
- 9: boggyb's highly inaccurate guide to Eurovision: Shine a Light 2
- 10: Brighton again
Style Credit
- Style: Neutral Good for Practicality by
Expand Cut Tags
No cut tags
no subject
Date: 2012-06-08 06:39 pm (UTC)On x86 at least, I think the intention is that if you want to use secure boot with your own kernel then you'll be expected to generate a suitable certificate (self-signed would work) and use that. Since the average user isn't going to a) want to do that, or even b) know how, Fedora have chosen to ship kernels signed with a certificate that is in turn signed by the MS certificate as then they have a kernel which will work without requiring any BIOS changes. I think they intend other distributions to either get their own signed certificate (Redhat and CentOS will likely do this), use a self-signed one and require the user to install the certificate if they want to use secure boot, or just expect the end user to deal with it all (Slackware will likely do that).