public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andreas Dannenberg <dannenberg@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] doc: clarify openssl-based key and certificate generation process
Date: Wed, 23 Mar 2016 18:24:10 -0500	[thread overview]
Message-ID: <1458775450-25358-1-git-send-email-dannenberg@ti.com> (raw)

Add some basic clarification that the dev.key file generated by OpenSSL
contains both the public and private key, and further highlight that
the certificate generated here contains the public key only.

Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
---
 doc/uImage.FIT/signature.txt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/uImage.FIT/signature.txt b/doc/uImage.FIT/signature.txt
index b2f89fc..e487401 100644
--- a/doc/uImage.FIT/signature.txt
+++ b/doc/uImage.FIT/signature.txt
@@ -62,14 +62,14 @@ placed alongside rsa.c, and its functions added to the table in image-sig.c
 also.
 
 
-Creating an RSA key and certificate
------------------------------------
-To create a new public key, size 2048 bits:
+Creating an RSA key pair and certificate
+----------------------------------------
+To create a new public/private key pair, size 2048 bits:
 
 $ openssl genpkey -algorithm RSA -out keys/dev.key \
     -pkeyopt rsa_keygen_bits:2048 -pkeyopt rsa_keygen_pubexp:65537
 
-To create a certificate for this:
+To create a certificate for this containing the public key:
 
 $ openssl req -batch -new -x509 -key keys/dev.key -out keys/dev.crt
 
-- 
2.6.4

             reply	other threads:[~2016-03-23 23:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 23:24 Andreas Dannenberg [this message]
2016-04-02  1:56 ` [U-Boot] doc: clarify openssl-based key and certificate generation process Tom Rini

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=1458775450-25358-1-git-send-email-dannenberg@ti.com \
    --to=dannenberg@ti.com \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox