similar to: CentOS 7.6.1810 UEFI/Shim issue .. feedback wanted !

When we consolidated all CentOS Distro builders in a new centralized setup, covering all arches (so basically x86_64, i386, ppc64le, ppc64, aarch64 and armhfp those days), we wanted also to add redundancy where it was possible to. The interesting "SecureBoot" corner case came on the table and we had to find a different way to build the following packages: - shim (both signed and

Am 16.06.20 um 22:04 schrieb Fabian Arrotin: > On 16/06/2020 15:06, Leon Fauster via CentOS wrote: >> Hi all, >> >> I updated a Dell XPS laptop from CentOS 8.1 (1911) to 8.2 (2004). >> >> Installed kernels are >> kernel-4.18.0-147.5.1.el8_1.x86_64 >> kernel-4.18.0-147.8.1.el8_1.x86_64 >> kernel-4.18.0-193.6.3.el8_2.x86_64 >> >>

At 04:18 PM 8/4/2020, you wrote: >Am 05.08.20 um 01:09 schrieb david: >>At 01:54 PM 8/4/2020, you wrote: >>>On Tue, 04 Aug 2020 13:44:05 -0700 >>>david wrote: >>> >>> > After all the updates, the system was NOT bootable. >>> >>>How long did you wait for it to boot, and what >>>did it do when it failed to boot?? What text

We are aware of the Boot Hole vulnerability in grub2 (CVE-2020-1073) and are working on releasing new packages for CentOS Linux 7, CentOS Linux 8 and CentOS Stream in response. These should make it out to a mirror near you shortly. /!\ Secureboot Systems - Please do a full update /!\ CentOS Linux 8 and CentOS Stream systems with secureboot enabled MUST update the kernel, grub2, and shim

On 07/08/2020 10:01, Johnny Hughes wrote: > On 8/7/20 3:46 AM, Nicolas Kovacs wrote: >> Le 07/08/2020 ? 09:40, Alessandro Baggi a ?crit?: >>> Probably many users have not updated their machines between the bug release and >>> the resolution (thanks to your fast apply in the weekend, thank you) and many >>> update their centos machines on a 2 months base (if not

Hi! I'm working currently on integration of UEFI/SecureBoot support into oVirt. And I have several questions about UEFI/SecureBoot support in libvirt. Can you please help me with them? For UEFI I add the following to the XML: <loader readonly="yes" secure="no" type="pflash"> /usr/share/OVMF/OVMF_CODE.secboot.fd </loader> <nvram

At 05:01 PM 8/4/2020, you wrote: >Am 05.08.20 um 01:27 schrieb david: >>At 04:18 PM 8/4/2020, you wrote: >>>Am 05.08.20 um 01:09 schrieb david: >>>>At 01:54 PM 8/4/2020, you wrote: >>>>>On Tue, 04 Aug 2020 13:44:05 -0700 >>>>>david wrote: >>>>> >>>>> > After all the updates, the system was NOT bootable.

On 8/7/20 2:40 AM, Alessandro Baggi wrote: > > Il 07/08/20 08:22, Johnny Hughes ha scritto: >>> "How on earth could this have passed Q & A ?" > > Hi Johnny, > Niki's question is spread, legit, in the thoughts in many and many users > so don't see this as an attack. Many and many users,though really "if > this was tested before

Hey, question if I could. What kind of support does syslinux have for UEFI? In particular I'm looking to use syslinux on Windows 8 systems.. I know I can leverage the shim to work through SecureBoot, but yeah, I couldn't find any documentation as to UEFI support otherwise. Thanks! -- Ian Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

On 1/22/2016 3:42 PM, Gordon Messmer wrote: > On 01/22/2016 02:38 PM, John R Pierce wrote: >> for that matter, what about a VM running on a service like Amazon AWS >> (or pick your virtual server environment) ? AWS provides a remote >> console, doesn't it? > > AWS doesn't offer UEFI Secure Boot, so I'm not sure how that's relevant. > > It

Le 07/08/2020 ? 09:40, Alessandro Baggi a ?crit?: > Probably many users have not updated their machines between the bug release and > the resolution (thanks to your fast apply in the weekend, thank you) and many > update their centos machines on a 2 months base (if not worst). I think also > that many users of CentOS user base have not proclamed their > disappointement/the issue on

At 01:54 PM 8/4/2020, you wrote: >On Tue, 04 Aug 2020 13:44:05 -0700 >david wrote: > > > After all the updates, the system was NOT bootable. > >How long did you wait for it to boot, and what did it do when it >failed to boot? What text messages showed up on the console? Any >reported errors when you ran the update or when you rebooted the >computer? If so, what

Am 16.06.20 um 22:04 schrieb Fabian Arrotin: > On 16/06/2020 15:06, Leon Fauster via CentOS wrote: >> Hi all, >> >> I updated a Dell XPS laptop from CentOS 8.1 (1911) to 8.2 (2004). >> >> Installed kernels are >> kernel-4.18.0-147.5.1.el8_1.x86_64 >> kernel-4.18.0-147.8.1.el8_1.x86_64 >> kernel-4.18.0-193.6.3.el8_2.x86_64 >> >>

On 8/7/20 3:46 AM, Nicolas Kovacs wrote: > Le 07/08/2020 ? 09:40, Alessandro Baggi a ?crit?: >> Probably many users have not updated their machines between the bug release and >> the resolution (thanks to your fast apply in the weekend, thank you) and many >> update their centos machines on a 2 months base (if not worst). I think also >> that many users of CentOS user

On 02/08/2020 16:26, Valeri Galtsev wrote: > > On the side note: it is Microsoft that signs one of Linux packages now. We seem to have made one more step away from ?our? computers being _our computers_. Am I wrong? > > Valeri > Microsoft are the Certificate Authority for SecureBoot and most SB-enabled hardware (most x86 hardware) comes with a copy of the Microsoft key

On 8/7/20 5:30 AM, Phil Perry wrote: > On 07/08/2020 10:01, Johnny Hughes wrote: >> On 8/7/20 3:46 AM, Nicolas Kovacs wrote: >>> Le 07/08/2020 ? 09:40, Alessandro Baggi a ?crit?: >>>> Probably many users have not updated their machines between the bug >>>> release and >>>> the resolution (thanks to your fast apply in the weekend, thank you)

Hi all, I updated a Dell XPS laptop from CentOS 8.1 (1911) to 8.2 (2004). Installed kernels are kernel-4.18.0-147.5.1.el8_1.x86_64 kernel-4.18.0-147.8.1.el8_1.x86_64 kernel-4.18.0-193.6.3.el8_2.x86_64 Unfortunately I can not boot into the latest kernel-4.18.0-193.6.3.el8_2.x86_64. After grub2 screen I only see following line: EFI stub: UEFI Secure Boot is enabled Booting into the older

Am 05.08.20 um 01:27 schrieb david: > At 04:18 PM 8/4/2020, you wrote: >> Am 05.08.20 um 01:09 schrieb david: >>> At 01:54 PM 8/4/2020, you wrote: >>>> On Tue, 04 Aug 2020 13:44:05 -0700 >>>> david wrote: >>>> >>>> > After all the updates, the system was NOT bootable. >>>> >>>> How long did you wait for it

Am 05.08.20 um 01:09 schrieb david: > At 01:54 PM 8/4/2020, you wrote: >> On Tue, 04 Aug 2020 13:44:05 -0700 >> david wrote: >> >> > After all the updates, the system was NOT bootable. >> >> How long did you wait for it to boot, and what did it do when it >> failed to boot?? What text messages showed up on the console?? Any >> reported errors

Hi All, I've been running Gentoo on a ZBook with great success for a couple years, but I've been stymied in my attempts to implement SecureBoot by an apparent problem with efifb to nouveaufb handoff, but only when external monitors are attached. The handoff works without issue when the BIOS is in Mixed EFI mode, with and without external monitors, and works in Native EFI mode without