| Message ID | 20171017070652.12280-1-martin.kaistra@linutronix.de |
|---|---|
| State | Accepted |
| Headers | show |
| Series | doc: fix typos | expand |
Hi Martin, On 17/10/2017 09:06, Martin Kaistra wrote: > Signed-off-by: Martin Kaistra <martin.kaistra@linutronix.de> > --- > doc/source/signed_images.rst | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/doc/source/signed_images.rst b/doc/source/signed_images.rst > index 43f563e..611ba02 100644 > --- a/doc/source/signed_images.rst > +++ b/doc/source/signed_images.rst > @@ -100,7 +100,7 @@ Signing the image is very simple: > > openssl dgst -sha256 -sign priv.pem sw-description > sw-description.sig > > -Usage with certificates ans CMS > +Usage with certificates and CMS > ------------------------------- > > Generating certificates > @@ -199,7 +199,7 @@ The example applies to a Beaglebone, installing Yocto images: > Running SWUpdate with signed images > ----------------------------------- > > -Verification is activated by setting CONFIG_SIGNED_IMAGE in SWUpdate's configuration. > +Verification is activated by setting CONFIG_SIGNED_IMAGES in SWUpdate's configuration. > If activated, SWUpdate will always check the compound image. For security reasons, > it is not possible to disable the check at runtime. The -k parameter (public key file) > is mandatory and the program stops if the public key is not passed. > Acked-by: Stefano Babic <sbabic@denx.de> Best regards, Stefano Babic
On 17/10/2017 09:06, Martin Kaistra wrote: > Signed-off-by: Martin Kaistra <martin.kaistra@linutronix.de> > --- > doc/source/signed_images.rst | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/doc/source/signed_images.rst b/doc/source/signed_images.rst > index 43f563e..611ba02 100644 > --- a/doc/source/signed_images.rst > +++ b/doc/source/signed_images.rst > @@ -100,7 +100,7 @@ Signing the image is very simple: > > openssl dgst -sha256 -sign priv.pem sw-description > sw-description.sig > > -Usage with certificates ans CMS > +Usage with certificates and CMS > ------------------------------- > > Generating certificates > @@ -199,7 +199,7 @@ The example applies to a Beaglebone, installing Yocto images: > Running SWUpdate with signed images > ----------------------------------- > > -Verification is activated by setting CONFIG_SIGNED_IMAGE in SWUpdate's configuration. > +Verification is activated by setting CONFIG_SIGNED_IMAGES in SWUpdate's configuration. > If activated, SWUpdate will always check the compound image. For security reasons, > it is not possible to disable the check at runtime. The -k parameter (public key file) > is mandatory and the program stops if the public key is not passed. > Applied to -master, thanks ! Best regards, Stefano Babic
diff --git a/doc/source/signed_images.rst b/doc/source/signed_images.rst index 43f563e..611ba02 100644 --- a/doc/source/signed_images.rst +++ b/doc/source/signed_images.rst @@ -100,7 +100,7 @@ Signing the image is very simple: openssl dgst -sha256 -sign priv.pem sw-description > sw-description.sig -Usage with certificates ans CMS +Usage with certificates and CMS ------------------------------- Generating certificates @@ -199,7 +199,7 @@ The example applies to a Beaglebone, installing Yocto images: Running SWUpdate with signed images ----------------------------------- -Verification is activated by setting CONFIG_SIGNED_IMAGE in SWUpdate's configuration. +Verification is activated by setting CONFIG_SIGNED_IMAGES in SWUpdate's configuration. If activated, SWUpdate will always check the compound image. For security reasons, it is not possible to disable the check at runtime. The -k parameter (public key file) is mandatory and the program stops if the public key is not passed.
Signed-off-by: Martin Kaistra <martin.kaistra@linutronix.de> --- doc/source/signed_images.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)