From 123c58693ac786c3cef8a74b03c1557a66dc0142 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ulrich=20=C3=96lmann?= Date: Tue, 5 Mar 2024 21:07:53 +0100 Subject: [PATCH] signing.bbclass: fix typos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Ulrich Ölmann Signed-off-by: Khem Raj --- meta-oe/classes/signing.bbclass | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/meta-oe/classes/signing.bbclass b/meta-oe/classes/signing.bbclass index ec076d9685..f52d861b76 100644 --- a/meta-oe/classes/signing.bbclass +++ b/meta-oe/classes/signing.bbclass @@ -6,9 +6,9 @@ # This class provides a common workflow to use asymmetric (i.e. RSA) keys to # sign artifacts. Usually, the keys are either stored as simple files in the -# file system or on a HSM (Hardware Security Module). While files are easy to -# use, it's hard to verify that no copies of the private have been made and -# only authorized persons are able to use the key. Use of an HSM addresses +# file system or on an HSM (Hardware Security Module). While files are easy to +# use, it's hard to verify that no copies of the private key have been made +# and only authorized persons are able to use the key. Use of an HSM addresses # these risks by only allowing use of the key via an API (often PKCS #11). The # standard way of referring to a specific key in an HSM are PKCS #11 URIs (RFC # 7512).