diff options
| -rw-r--r-- | meta-oe/classes/signing.bbclass | 6 |
1 files 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 @@ | |||
| 6 | 6 | ||
| 7 | # This class provides a common workflow to use asymmetric (i.e. RSA) keys to | 7 | # This class provides a common workflow to use asymmetric (i.e. RSA) keys to |
| 8 | # sign artifacts. Usually, the keys are either stored as simple files in the | 8 | # sign artifacts. Usually, the keys are either stored as simple files in the |
| 9 | # file system or on a HSM (Hardware Security Module). While files are easy to | 9 | # file system or on an HSM (Hardware Security Module). While files are easy to |
| 10 | # use, it's hard to verify that no copies of the private have been made and | 10 | # use, it's hard to verify that no copies of the private key have been made |
| 11 | # only authorized persons are able to use the key. Use of an HSM addresses | 11 | # and only authorized persons are able to use the key. Use of an HSM addresses |
| 12 | # these risks by only allowing use of the key via an API (often PKCS #11). The | 12 | # these risks by only allowing use of the key via an API (often PKCS #11). The |
| 13 | # standard way of referring to a specific key in an HSM are PKCS #11 URIs (RFC | 13 | # standard way of referring to a specific key in an HSM are PKCS #11 URIs (RFC |
| 14 | # 7512). | 14 | # 7512). |