Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A archiso
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 42
    • Issues 42
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch Linux
  • archiso
  • Issues
  • #69
Closed
Open
Created Sep 27, 2020 by David Runge@dvzrvDeveloper

Provide Secure Boot support

As discussed in FS#53864 it would be beneficial to provide Secure Boot support out-of-the-box (for systems that are booted for the first time and have Secure Boot enabled or for systems where Secure Boot can not be disabled).

One of the outcomes of the above discussion has been that likely the only viable option for this use-case is to apply for a distribution certificate and use a signed shim (see this mailing list discussion by @diabonas for reference).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking