mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Enrico Joerns <ejo@pengutronix.de>
To: gurpartap singh <gurpartap.terron@yahoo.in>
Cc: "rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: Re: [RAUC] Errors in Using Rauc
Date: Tue, 23 May 2017 11:03:32 +0200	[thread overview]
Message-ID: <bc45f61e-4313-9f41-7161-680f53d4ce7d@pengutronix.de> (raw)
In-Reply-To: <fb7e50f6-44c5-ad3b-d224-d15685c20201@pengutronix.de>

On 03/13/2017 05:08 PM, Enrico Joerns wrote:
>> [...]
>> LOG of
>> ./rauc info -d update.raucb
>> Domains: 'rauc'
>> rauc-Message: Reading bundle: update.raucb
>> rauc-Message: Verifying bundle...
>> 3069734912:error:2E09D06D:CMS routines:CMS_verify:content verify
>> error:../crypto/cms/cms_smime.c:393:
>>
>> (rauc:21318): rauc-WARNING **: signature verification failed:
>> error:2E09A09E:CMS routines:CMS_SignerInfo_verify_content:verification
>> failure
>
> I assume you executed this on the target?
> Obviously, there is a certificate verification error. Did you set up the
> key, cert and keychain correctly? If you want to (for test-purpose)
> inspect the bundle without verification, you can use the `--no-verify`
> argument. But for installation the verification is mandatory thus it
> should work with `info`, too.

Just for reference, the encryption error might have also been triggered 
by this issue in RAUC when using OpenSSL 1.1.x:

   https://github.com/rauc/rauc/issues/115

This was resolved in

   https://github.com/rauc/rauc/pull/116

and is available since release 0.1.1 of RAUC

Best regards, Enrico

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


_______________________________________________
RAUC mailing list

      parent reply	other threads:[~2017-05-23  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1195414473.2379963.1489058037687.ref@mail.yahoo.com>
2017-03-09 11:13 ` gurpartap singh
2017-03-13 16:08   ` Enrico Joerns
2017-04-05  5:08     ` gurpartap singh
2017-04-05 10:21       ` Enrico Joerns
2017-05-23  9:03     ` Enrico Joerns [this message]

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=bc45f61e-4313-9f41-7161-680f53d4ce7d@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=gurpartap.terron@yahoo.in \
    --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