From 5519ef9473ea18d3ea7517128d35b7aae4ddd550 Mon Sep 17 00:00:00 2001 From: Christopher Head Date: Wed, 10 Sep 2025 22:40:46 -0700 Subject: [PATCH] ukify: fix backend/option applicability docs The `SecureBootPrivateKey` and `SecureBootCertificate` options are used by the `systemd-sbsign` backend, not just the `sbsign` backend. (cherry picked from commit fafe447dcdf13a61ef262f16015130b21453ef6a) --- man/ukify.xml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/man/ukify.xml b/man/ukify.xml index 15cd35bcf5a..d3cfc0a4f72 100644 --- a/man/ukify.xml +++ b/man/ukify.xml @@ -490,7 +490,8 @@ SigningEngine=/ or SigningProvider=/ option is used, this may also be an engine or provider specific designation. This option is required by - SecureBootSigningTool=sbsign/. + SecureBootSigningTool=sbsign/ and + SecureBootSigningTool=systemd-sbsign/. @@ -503,7 +504,8 @@ SigningEngine=/ or SigningProvider=/ option is used, this may also be an engine or provider specific designation. This option is required by - SecureBootSigningTool=sbsign/. + SecureBootSigningTool=sbsign/ and + SecureBootSigningTool=systemd-sbsign/. -- 2.47.3