shim 15+1552672080.a4a1fbe-0ubuntu1 source package in Ubuntu
Changelog
shim (15+1552672080.a4a1fbe-0ubuntu1) eoan; urgency=medium * New upstream snapshot 15+1552672080.a4a1fbe. * debian/patches/VLogError-Avoid-NULL-pointer-dereferences-in-V-Sprin.patch, debian/patches/fixup_git.patch: drop patches included in upstream. * debian/patches/MokManager-avoid-unaligned.patch: Fix compilation with GCC9: avoid -Werror=address-of-packed-member errors in MokManager. * debian/patches/tpm-correctness-1.patch, debian/patches/tpm-correctness-2.patch: fix issues in TPM calls to ensure the measurements are consistent with what is entered in the TPM event log. * debian/patches/tpm-correctness-3.patch: Don't log duplicate identical TPM events. * debian/patches/MokManager-hidpi-support.patch: Do a little bit more to try to get a more usable screen resolution for MokManager when running on HiDPI screens; by trying to detect such cases and switching to mode 0. * debian/rules: update COMMIT_ID explicitly for this new snapshot. -- Mathieu Trudel-Lapierre <email address hidden> Fri, 11 Oct 2019 16:32:32 -0400
Upload details
- Uploaded by:
- Mathieu Trudel-Lapierre
- Uploaded to:
- Eoan
- Original maintainer:
- Ubuntu Developers
- Architectures:
- amd64 arm64
- Section:
- admin
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
shim_15+1552672080.a4a1fbe.orig.tar.gz | 1.2 MiB | adcd1e0112f0f979860227feadeaadb47ad2f3f5d94e3d58a2d33ca3e1b2ffe9 |
shim_15+1552672080.a4a1fbe-0ubuntu1.debian.tar.xz | 18.0 KiB | a90311e824a425d8d91d9fa19cb987cff5e86ab6a1838e70ecf206927a6e3475 |
shim_15+1552672080.a4a1fbe-0ubuntu1.dsc | 2.1 KiB | 90719d15fb5ab78c1b44396ffd36b1ca22a7c2ceabaff31427d669cda417d1b7 |
Available diffs
Binary packages built by this source
- shim: boot loader to chain-load signed boot loaders under Secure Boot
This package provides a minimalist boot loader which allows verifying
signatures of other UEFI binaries against either the Secure Boot DB/DBX or
against a built-in signature database. Its purpose is to allow a small,
infrequently-changing binary to be signed by the UEFI CA, while allowing
an OS distributor to revision their main bootloader independently of the CA.