search for: shimmed

This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that is, the one from the latest installation media. I am running on an x86_64 architecture (see uname -i). Please use the correct shim file for your architecture

><snip> > > I'll post here again once we have pushed the EL8 and CentOS Stream updates. > >OK .. I have also now pushed the CentOS Linux 8 update .. you should see >an update to SHIM .. the new versions are: > >PowerTools/x86_64/os/Packages/shim-unsigned-x64-15-8.el8.x86_64.rpm >BaseOS/x86_64/os/Packages/shim-ia32-15-15.el8_2.x86_64.rpm

At 06:10 AM 8/2/2020, you wrote: >On 8/2/20 8:04 AM, david wrote: > > > >> <snip> > > > > > > > >> > I'll post here again once we have pushed the EL8 and CentOS Stream > >> updates. > >> > >> OK .. I have also now pushed the CentOS Linux 8 update .. you should see > >> an update to SHIM .. the new

At 06:37 AM 8/2/2020, Johnny Hughes wrote: >On 8/2/20 8:30 AM, david wrote: > > At 06:10 AM 8/2/2020, you wrote: > >> On 8/2/20 8:04 AM, david wrote: > >> > > >> >> <snip> > >> > > >> > > >> > > >> >> > I'll post here again once we have pushed the EL8 and CentOS Stream > >>

Hello all-- These instructions are somewhat OK but my messed up box is the only one I've got basically to help with this problem. Where can we find "correction" instructions using a "rescue" CD or flash drive? I understand RedHat provided detailed instructions to supported customers. Thanks. _______________________ Sent from MzK's phone. ---------- Forwarded message

On 8/2/20 2:04 AM, Alessandro Baggi wrote: > > Il 01/08/20 22:03, Greg Bailey ha scritto: >> On 8/1/20 6:56 AM, david wrote: >>> At 02:54 AM 8/1/2020, Alessandro Baggi wrote: >>>> Hi Johnny, >>>> thank you very much for clarification. >>>> >>>> You said that in the centos infrastructure only one server got the >>>>

Hello all-- These instructions are somewhat OK but my messed up box is the only one I've got basically to help with this problem. Where can we find "correction" instructions using a "rescue" CD or flash drive? I understand RedHat provided detailed instructions to supported customers. Thanks. _______________________ Sent from MzK's phone. ---------- Forwarded message

On 8/2/20 8:30 AM, david wrote: > At 06:10 AM 8/2/2020, you wrote: >> On 8/2/20 8:04 AM, david wrote: >> > >> >> <snip> >> > >> > >> > >> >> > I'll post here again once we have pushed the EL8 and CentOS Stream >> >> updates. >> >> >> >> OK .. I have also now pushed the CentOS Linux

On 8/2/20 8:47 AM, david wrote: > At 06:37 AM 8/2/2020, Johnny Hughes wrote: >> On 8/2/20 8:30 AM, david wrote: >> > At 06:10 AM 8/2/2020, you wrote: >> >> On 8/2/20 8:04 AM, david wrote: >> >> > >> >> >> <snip> >> >> > >> >> > >> >> > >> >> >> > I'll post here

> Am 02.08.2020 um 14:34 schrieb Johnny Hughes <johnny at centos.org>: > > ?On 8/2/20 6:59 AM, Johnny Hughes wrote: >>> On 8/2/20 2:04 AM, Alessandro Baggi wrote: >>> >>> Il 01/08/20 22:03, Greg Bailey ha scritto: >>>> On 8/1/20 6:56 AM, david wrote: >>>>> At 02:54 AM 8/1/2020, Alessandro Baggi wrote: >>>>>>

On 8/2/20 8:04 AM, david wrote: > >> <snip> > > > >> > I'll post here again once we have pushed the EL8 and CentOS Stream >> updates. >> >> OK .. I have also now pushed the CentOS Linux 8 update .. you should see >> an update to SHIM .. the new versions are: >> >>

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

Hi, On Thu, Oct 19, 2017 at 09:43:41AM +1100, Damien Miller wrote: > You've got this exactly backwards. We don't want a shim that allows > OpenSSL-1.1 to present a OpenSSL-1.0 API. We want a shim that allows > us to use the OpenSSL-1.1 API when using OpenSSL-1.0, so we don't have > to maintain a forest of #ifdefs. For obvious reasons this shim cannot exist. If the

Once upon a time, Johnny Hughes <johnny at centos.org> said: > The issues should now be resolved. > > If you just mount /mnt/sysimage, set an ip address and upgrade (to get > th new shim) .. then: > > yum reinstall <latest-version> I'm curious - why does the kernel need to be reinstalled? The shim-x64 package installs its files directly to the EFI partition

From: "Richard W.M. Jones" <rjones@redhat.com> Do not use LD_LIBRARY_PATH to locate the VDDK library. Setting this always causes problems because VDDK comes bundled with broken replacements for system libraries, such as libcrypto.so and libstdc++.so. Two problems this causes which we have seen in the real world: (1) User does ‘export LD_LIBRARY_PATH=vmware-vix-disklib-distrib’

On 8/2/20 6:59 AM, Johnny Hughes wrote: > On 8/2/20 2:04 AM, Alessandro Baggi wrote: >> >> Il 01/08/20 22:03, Greg Bailey ha scritto: >>> On 8/1/20 6:56 AM, david wrote: >>>> At 02:54 AM 8/1/2020, Alessandro Baggi wrote: >>>>> Hi Johnny, >>>>> thank you very much for clarification. >>>>> >>>>> You said

CentOS Errata and Bugfix Advisory 2019:C001 This is a bug fix for for the following CentOS Bug: https://bugs.centos.org/view.php?id=15522 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 0ae55996308b507ba878377b35b71225c1fa28d4fb453c938a0d5dc9568501cc mokutil-15-2.el7.centos.x86_64.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hello everybody, ? ? I saw that another discussion about OpenSSL 1.1 support started on this list, and I'd like to know what is the current status about this. >From what I understand, at least ?one patch set already exists: ? ? a github PR [1] from , Kurt Roeckx announced on the list in september 2016 [2] ? and which also exist as a fedora patch [3]? (I haven't checked the details,

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