public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
* [pve-devel] [PATCH docs] secure boot: mention proxmox-secure-boot-support metapackage
@ 2024-04-18 14:24 Stoiko Ivanov
  2024-04-18 20:12 ` [pve-devel] applied: " Thomas Lamprecht
  0 siblings, 1 reply; 2+ messages in thread
From: Stoiko Ivanov @ 2024-04-18 14:24 UTC (permalink / raw)
  To: pve-devel

Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
Just had the opportunity to try this on a testsystem - it worked flawlessly :)

I did consider dropping the explicit list of packages and replace it by the
metapackage only, but think that the additional explanation of how they
interact is worth keeping.

 system-booting.adoc | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/system-booting.adoc b/system-booting.adoc
index 9603fc0..3847354 100644
--- a/system-booting.adoc
+++ b/system-booting.adoc
@@ -378,7 +378,8 @@ Secure Boot
 Since {pve} 8.1, Secure Boot is supported out of the box via signed packages
 and integration in `proxmox-boot-tool`.
 
-The following packages need to be installed for Secure Boot to be enabled:
+The following packages needed for Secure Boot to work, are installed as
+dependency of `proxmox-secure-boot-support`:
 
 - `shim-signed` (shim bootloader signed by Microsoft)
 - `shim-helpers-amd64-signed` (fallback bootloader and MOKManager, signed by
@@ -404,9 +405,9 @@ well-tested backup of your {pve} host!**
 An existing UEFI installation can be switched over to Secure Boot if desired,
 without having to reinstall {pve} from scratch.
 
-First, ensure all your system is up-to-date. Next, install all the required
-pre-signed packages as listed above. GRUB automatically creates the needed EFI
-boot entry for booting via the default shim.
+First, ensure all your system is up-to-date. Next, install
+`proxmox-secure-boot-support`. GRUB automatically creates the needed EFI boot
+entry for booting via the default shim.
 
 .systemd-boot
 
-- 
2.39.2



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 2+ messages in thread

* [pve-devel] applied: [PATCH docs] secure boot: mention proxmox-secure-boot-support metapackage
  2024-04-18 14:24 [pve-devel] [PATCH docs] secure boot: mention proxmox-secure-boot-support metapackage Stoiko Ivanov
@ 2024-04-18 20:12 ` Thomas Lamprecht
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Lamprecht @ 2024-04-18 20:12 UTC (permalink / raw)
  To: Proxmox VE development discussion, Stoiko Ivanov

Am 18/04/2024 um 16:24 schrieb Stoiko Ivanov:
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> Just had the opportunity to try this on a testsystem - it worked flawlessly :)
> 
> I did consider dropping the explicit list of packages and replace it by the
> metapackage only, but think that the additional explanation of how they
> interact is worth keeping.
> 
>  system-booting.adoc | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
>

applied, with some slight rewording in a follow-up, thanks!


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-04-18 20:13 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-18 14:24 [pve-devel] [PATCH docs] secure boot: mention proxmox-secure-boot-support metapackage Stoiko Ivanov
2024-04-18 20:12 ` [pve-devel] applied: " Thomas Lamprecht

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal