** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571691
Title:
linux: MokSBState is ignored
To manage
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
** Tags removed: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571691
Title:
linux: MokSBState is ignored
To manage notifications about this bug go to:
This bug was fixed in the package linux - 3.13.0-92.139
---
linux (3.13.0-92.139) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1597060
[ Josh Boyer ]
* SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
This bug was fixed in the package linux - 3.19.0-65.73
---
linux (3.19.0-65.73) vivid; urgency=low
[ Ben Romer ]
* Release Tracking Bug
- LP: #1596631
[ Josh Boyer ]
* SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP:
This bug was fixed in the package linux - 4.2.0-42.49
---
linux (4.2.0-42.49) wily; urgency=low
[ Ben Romer ]
* Release Tracking Bug
- LP: #1597053
[ Josh Boyer ]
* SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP:
** Tags removed: verification-needed-wily
** Tags added: verification-done-wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571691
Title:
linux: MokSBState is ignored
To manage notifications
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571691
Title:
linux: MokSBState is ignored
To manage notifications
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571691
Title:
linux: MokSBState is ignored
To manage
** Also affects: linux (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Status: New => In Progress
** Changed in: linux (Ubuntu Wily)
Status: New => In
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
@adubinsky
Make sure you have efivarfs mounted read-write and the mokutil command is run
with root permission.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571691
Title:
linux: MokSBState is
`mokutil --disable-validation` doesn't work for me. It gave the same
"Failed to request new MokSB state" message, but upon reboot I did not
get any prompt to re-enter the password. Had to disable secureboot in
the bios.
Why was this even enabled when Canonical-provided drivers like
nvidia-361
Yes, that message indicates that your kernel is _not_ in secure boot
mode, i.e., it _will_ load any (appropriately compiled) module.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571691
Title:
re-read the initial description.
So if I get "[0.00] Secure boot MOKSBState disabled", this is exactly
what I want?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571691
Title:
linux:
1. asks for a password
2. Setting SB State Failed
3. nothing says I should reboot
4. upon reboot configuration screen pops up and asks random characters from the
password entered before
5. allows me to disable verification
in case the above is the correct user story, I have the following
remark:
Try 'sudo apt-get install mokutil; sudo mokutil --disable-validation'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571691
Title:
linux: MokSBState is ignored
To manage notifications about this
I have issues with this on trusty.
The log says "Secure boot enabled" and consequently the nvidia DKMS module can
not be loaded.
At which point should I have been asked to select the secure boot
behavior?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package linux - 4.4.0-21.37
---
linux (4.4.0-21.37) xenial; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1571791
* linux: MokSBState is ignored (LP: #1571691)
- SAUCE: (noup) MODSIGN: Import certificates from UEFI Secure Boot
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571691
Title:
linux: MokSBState is ignored
To manage notifications
Tested using a Qemu instance with ovmf installed. Looks to be doing what
is expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571691
Title:
linux: MokSBState is ignored
To manage
** Description changed:
Ubuntu-4.4.0-20.36 was released with signed module enforcement enabled,
- but contained no way of disabling secure boot for DKMS.
+ but contained no way of disabling secure boot for DKMS. Without this
+ kernel patch it is possible to get your machine in an unbootable
** Description changed:
Ubuntu-4.4.0-20.36 was released with signed module enforcement enabled,
but contained no way of disabling secure boot for DKMS.
+
+ This patch set implements the ability to disable secure boot on demand
+ from user space (with some password shennaigans). If one boots
25 matches
Mail list logo
