All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Axtens <dja@axtens.net>
To: grub-devel@gnu.org
Cc: rashmica.g@gmail.com, alastair@d-silva.org,
	Daniel Axtens <dja@axtens.net>
Subject: [PATCH v2 02/18] docs/grub: --pubkey has been supported for some time
Date: Wed, 28 Oct 2020 12:57:19 +1100	[thread overview]
Message-ID: <20201028015735.1131291-3-dja@axtens.net> (raw)
In-Reply-To: <20201028015735.1131291-1-dja@axtens.net>

--pubkey is supported, so we can now document it.

Signed-off-by: Daniel Axtens <dja@axtens.net>
---
 docs/grub.texi | 12 +++---------
 1 file changed, 3 insertions(+), 9 deletions(-)

diff --git a/docs/grub.texi b/docs/grub.texi
index 6cbd753d12fd..6bac37728042 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -5821,15 +5821,9 @@ verified with a public key currently trusted by GRUB
 validation fails, then file @file{foo} cannot be opened.  This failure
 may halt or otherwise impact the boot process.
 
-@comment Unfortunately --pubkey is not yet supported by grub-install,
-@comment but we should not bring up internal detail grub-mkimage here
-@comment in the user guide (as opposed to developer's manual).
-
-@comment An initial trusted public key can be embedded within the GRUB
-@comment @file{core.img} using the @code{--pubkey} option to
-@comment @command{grub-mkimage} (@pxref{Invoking grub-install}).  Presently it
-@comment is necessary to write a custom wrapper around @command{grub-mkimage}
-@comment using the @code{--grub-mkimage} flag to @command{grub-install}.
+An initial trusted public key can be embedded within the GRUB
+@file{core.img} using the @code{--pubkey} option to
+@command{grub-install} (@pxref{Invoking grub-install}).
 
 GRUB uses GPG-style detached signatures (meaning that a file
 @file{foo.sig} will be produced when file @file{foo} is signed), and
-- 
2.25.1



  parent reply	other threads:[~2020-10-28  1:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28  1:57 [PATCH v2 00/18] Verify appended signatures from grub Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 01/18] docs/grub: grub-install is no longer a shell script Daniel Axtens
2020-11-18 18:10   ` Daniel Kiper
2020-10-28  1:57 ` Daniel Axtens [this message]
2020-11-18 18:12   ` [PATCH v2 02/18] docs/grub: --pubkey has been supported for some time Daniel Kiper
2020-10-28  1:57 ` [PATCH v2 03/18] dl: provide a fake grub_dl_set_persistent for the emu target Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 04/18] verifiers: factor unsafe module handling out of shim_lock Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 05/18] pgp: factor out rsa_pad Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 06/18] crypto: move storage for grub_crypto_pk_* to crypto.c Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 07/18] posix_wrap: tweaks in preparation for libtasn1 Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 08/18] libtasn1: import libtasn1-4.16.0 Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 09/18] libtasn1: disable code not needed in grub Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 10/18] libtasn1: changes for grub compatibility Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 11/18] libtasn1: compile into asn1 module Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 12/18] test_asn1: test module for libtasn1 Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 13/18] grub-install: support embedding x509 certificates Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 14/18] appended signatures: import GNUTLS's ASN.1 description files Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 15/18] appended signatures: parse PKCS#7 signedData and X.509 certificates Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 16/18] appended signatures: support verifying appended signatures Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 17/18] appended signatures: verification tests Daniel Axtens
2020-10-28  1:57 ` [PATCH v2 18/18] appended signatures: documentation Daniel Axtens
2020-11-18 18:18 ` [PATCH v2 00/18] Verify appended signatures from grub Daniel Kiper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201028015735.1131291-3-dja@axtens.net \
    --to=dja@axtens.net \
    --cc=alastair@d-silva.org \
    --cc=grub-devel@gnu.org \
    --cc=rashmica.g@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.