mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: "Diego González" <dggonz@gmail.com>
To: rauc@pengutronix.de
Subject: [RAUC] problems verifying a bundle
Date: Tue, 28 Apr 2020 19:55:16 +0200	[thread overview]
Message-ID: <CACV1ZzK52HEJ3Hq9JWTOJvrpzU2Knz36oz=0VJRVx5E_H-w6RA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1744 bytes --]

Hello,

I am having issues when I try to verify a bundle downloaded on the device.
I am using rauc 1.3 through the meta-rauc for Yocto.

I am running *rauc info [name of the bundle].raucb* on the device. The
output I get is the following:

rauc-Message: 17:24:54.156: Debug log domains: 'all'
(rauc:528): rauc-DEBUG: 17:24:54.165: input bundle:
/var/1/rauc-bundle-raspberrypi3-64.raucb
(rauc:528): rauc-DEBUG: 17:24:54.166: No value for key
"max-bundle-download-size" in [system] defined - using default value of
8388608 bytes.
(rauc:528): rauc-DEBUG: 17:24:54.166: No mount prefix provided, using
/mnt/rauc/ as default
rauc-Message: 17:24:54.167: Reading bundle:
/var/1/rauc-bundle-raspberrypi3-64.raucb
(rauc:528): GLib-GIO-DEBUG: 17:24:54.170: _g_io_module_get_default: Found
default implementation local (GLocalVfs) for ?gio-vfs?
rauc-Message: 17:24:54.173: Verifying bundle...
*signature verification failed: Verify error:unsupported certificate
purpose*

I don't really know how to get past this issue. I have included in a file
the root certificate, intermediate certificate and the certificate that
corresponds to they key used to sign the bundle. And I point to that file
with path=/etc/rauc/firmware-keyring.pem in the system.conf file.

previous to doing that I was getting:
[...]
*signature verification failed: Verify error:unable to get local issuer
certificate*

With regards to the environment variables this is what I am using:

RAUC_KEY_FILE="/h4-work/certs/rauc/firmware-key.pem"
RAUC_CERT_FILE="/h4-work/certs/rauc/firmware.pem"
RAUC_KEYRING_FILE="firmware-keyring.pem" (which is the file that I am using
on the device)

I don't really know how to get past this issue, any points would be highly
appreciated.

Cheers,
Diego

[-- Attachment #1.2: Type: text/html, Size: 2231 bytes --]

[-- Attachment #2: Type: text/plain, Size: 66 bytes --]

_______________________________________________
RAUC mailing list

             reply	other threads:[~2020-04-28 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 17:55 Diego González [this message]
2020-04-29  6:53 ` Jan Lübbe

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='CACV1ZzK52HEJ3Hq9JWTOJvrpzU2Knz36oz=0VJRVx5E_H-w6RA@mail.gmail.com' \
    --to=dggonz@gmail.com \
    --cc=rauc@pengutronix.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