From 207c66fc5287cfcfe20191088cc96d2a55ed8a3f Mon Sep 17 00:00:00 2001 From: arnout Date: Wed, 25 Oct 2023 18:06:08 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Katrina Prosise --- source/user-guide/el2g.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/source/user-guide/el2g.rst b/source/user-guide/el2g.rst index 2a983d5eb..59887383e 100644 --- a/source/user-guide/el2g.rst +++ b/source/user-guide/el2g.rst @@ -234,8 +234,9 @@ EdgeLock 2GO Concepts Installing Additional Secure Objects ------------------------------------ -Any additional Secure Objects that are defined in EdgeLock 2GO and provisioned into the secure element when the device registers. -Additionally, keypairs and certificates are loaded into PKCS#11 so they are accessible to e.g. OpenSSL. +Additional Secure Objects can be defined in EdgeLock 2GO through the API. +These objects are provisioned into the Secure Element when the device registers. +On top of this, keypairs and certificates are loaded into PKCS#11 so they are accessible, e.g., OpenSSL. The convention is that the keypair secure object has an even-numbered OID (e.g. 0x10000010) and the corresponding certificate has an OID one higher (e.g. 0x10000011). To enable automatic loading of the keypair and certificate, the ``GENERIC_KEYPAIRS`` variable must be set in ``/etc/default/lmp-el2go-auto-register`` e.g.,