Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 938
    • Issues 938
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 29
    • Merge requests 29
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #17452

Figure out what to do with VirtualBox dkms modules vs. Secure Boot

Originally created by @intrigeri on #17452 (Redmine)

Presumably, all Tails started in VirtualBox won’t have Secure Boot enabled, either because they’re started from DVD (and we only support Secure Book when booting from USB and UEFI), or because VirtualBox does not support Secure Boot (does it?), so the unsigned VirtualBox dkms modules should be loaded just fine. Correct?
If that assumption is incorrect, then I don’t think we have to do anything here.
Else, we probably need to update some code and documentation.

Parent Task: #6560 (closed)

Related issues

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