[RAUC] Errors in Using Rauc

[RAUC] Errors in Using Rauc

[gurpartap singh]

I installed RAUC with --disable-network option because of libcurl dependency issues.
I have done below steps so far:
Created manifest.raucm like this
[update]
compatible=rauc-demo-x86
version=2015.04-1

[image.rootfs]
sha256=4c03d5be6780e64a604e94222a2da50e671698b9c1d764f1bbc617558de80f98
size=11376640
filename=rauc.img

MY /etc/rauc/system.conf is:

[system]
compatible=rauc-demo-x86
bootloader=uboot
mountprefix=/mnt/rauc


[slot.rootfs.0]
device=/dev/mmcblk0p1
type=raw
bootname=A

But when I try to install this update using:
./rauc install -d update.raucb
it shows following log:
Domains: 'rauc'
(rauc:21307): rauc-DEBUG: install started
(rauc:21307): rauc-DEBUG: input bundle: /home/rauc/update.raucb
Error creating proxy: Error calling StartServiceByName for de.pengutronix.rauc: Timeout was reached
D-Bus error while installing `/home/rauc/update.raucb`
Previously I have done:
./autogen.sh
./configure --disable-network
make
make install

service rauc start

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


QUESTION 2:
How to use it with uboot? Can u please elaborate how to install library to modify u-boot variables and environment.


Regards
Gurpartap Singh
Embedded Software Engineer
Terron Microsystems Pvt. Ltd
New Delhi

_______________________________________________
RAUC mailing list

Re: [RAUC] Errors in Using Rauc

[Enrico Joerns]

Hi,

On 03/09/2017 12:13 PM, gurpartap singh wrote:
> I installed RAUC with --disable-network option because of libcurl dependency issues.
> I have done below steps so far:
> Created manifest.raucm like this
> [update]
> compatible=rauc-demo-x86
> version=2015.04-1
>
> [image.rootfs]
> sha256=4c03d5be6780e64a604e94222a2da50e671698b9c1d764f1bbc617558de80f98
> size=11376640
> filename=rauc.img

this one looks ok.

> MY /etc/rauc/system.conf is:
>
> [system]
> compatible=rauc-demo-x86
> bootloader=uboot
> mountprefix=/mnt/rauc
>
>
> [slot.rootfs.0]
> device=/dev/mmcblk0p1
> type=raw
> bootname=A

this one will require a second rootfs partition to allow you installing 
updates when running from the productive one.

> But when I try to install this update using:
> ./rauc install -d update.raucb
> it shows following log:
> Domains: 'rauc'
> (rauc:21307): rauc-DEBUG: install started
> (rauc:21307): rauc-DEBUG: input bundle: /home/rauc/update.raucb
> Error creating proxy: Error calling StartServiceByName for de.pengutronix.rauc: Timeout was reached
> D-Bus error while installing `/home/rauc/update.raucb`

There seems to be a communication issue between the command line client 
and the service. Did you try to start the service. Do you have the d-bus 
config installed? Could you get any log data from the service itself?

> Previously I have done:
> ./autogen.sh
> ./configure --disable-network
> make
> make install
>
> service rauc start

This looks ok so far.

> 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.

>
> QUESTION 2:
> How to use it with uboot? Can u please elaborate how to install library to modify u-boot variables and environment.

In the documentation there is the chapter `Interfacing with the bootloader`:

http://rauc.readthedocs.io/en/latest/integration.html#interfacing-with-the-bootloader

Did you already try what is described in there? If there is some 
information missing please let us know. The subsection "U-Boot" also 
points you to the u-boot example script located in the `contrib/` 
folder. This should be a good starting point.


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

Re: [RAUC] Errors in Using Rauc

[gurpartap singh]

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

Hi Enrico,I am facing problems with D-Bus service. 
1. Error creating proxy: Error calling StartServiceByName for de.pengutronix.rauc: Timeout was reached
> D-Bus error while installing `/home/rauc/update.raucb2.How to start D-Bus service and run rauc in Daemon mode.3.Please start some IRC chat so we can get live help from your team.
 Regards
Gurpartap SinghEmbedded Software EngineerTerron Microsystems Pvt. LtdNew Delhi 

    On Monday, 13 March 2017 9:38 PM, Enrico Joerns <ejo@pengutronix.de> wrote:
 

 Hi,

On 03/09/2017 12:13 PM, gurpartap singh wrote:
> I installed RAUC with --disable-network option because of libcurl dependency issues.
> I have done below steps so far:
> Created manifest.raucm like this
> [update]
> compatible=rauc-demo-x86
> version=2015.04-1
>
> [image.rootfs]
> sha256=4c03d5be6780e64a604e94222a2da50e671698b9c1d764f1bbc617558de80f98
> size=11376640
> filename=rauc.img

this one looks ok.

> MY /etc/rauc/system.conf is:
>
> [system]
> compatible=rauc-demo-x86
> bootloader=uboot
> mountprefix=/mnt/rauc
>
>
> [slot.rootfs.0]
> device=/dev/mmcblk0p1
> type=raw
> bootname=A

this one will require a second rootfs partition to allow you installing 
updates when running from the productive one.

> But when I try to install this update using:
> ./rauc install -d update.raucb
> it shows following log:
> Domains: 'rauc'
> (rauc:21307): rauc-DEBUG: install started
> (rauc:21307): rauc-DEBUG: input bundle: /home/rauc/update.raucb
> Error creating proxy: Error calling StartServiceByName for de.pengutronix.rauc: Timeout was reached
> D-Bus error while installing `/home/rauc/update.raucb`

There seems to be a communication issue between the command line client 
and the service. Did you try to start the service. Do you have the d-bus 
config installed? Could you get any log data from the service itself?

> Previously I have done:
> ./autogen.sh
> ./configure --disable-network
> make
> make install
>
> service rauc start

This looks ok so far.

> 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.

>
> QUESTION 2:
> How to use it with uboot? Can u please elaborate how to install library to modify u-boot variables and environment.

In the documentation there is the chapter `Interfacing with the bootloader`:

http://rauc.readthedocs.io/en/latest/integration.html#interfacing-with-the-bootloader

Did you already try what is described in there? If there is some 
information missing please let us know. The subsection "U-Boot" also 
points you to the u-boot example script located in the `contrib/` 
folder. This should be a good starting point.


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

   

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

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

_______________________________________________
RAUC mailing list

Re: [RAUC] Errors in Using Rauc

[Enrico Joerns]

Hi,

On 04/05/2017 07:08 AM, gurpartap singh wrote:
> Hi Enrico,
> I am facing problems with D-Bus service.
> 1. Error creating proxy: Error calling StartServiceByName for
> de.pengutronix.rauc: Timeout was reached
>> D-Bus error while installing `/home/rauc/update.raucb

yes, we discussed this issue on the list already. For reference, see
   https://www.mail-archive.com/rauc@pengutronix.de/msg00005.html

The issue here was that the non-systemd D-Bus activation of RAUC did not 
work due to an error in the D-Bus service file.

The fix for this is already upstream, so you can either build the latest 
version from the master branch or fix the service file manually.

 
https://github.com/rauc/rauc/commit/bd7afda21226318bd5ca21cd7009f0aa3a73d9f0

> 2.How to start D-Bus service and run rauc in Daemon mode.

Well this question mainly answers itself by the fix provided above. You 
have to install the generated service files on your target. Then you 
will be able to start the RAUC daemon with D-Bus activation.

If you prefer an explicit start of RAUC, use a service file of your 
preferred init process (we only support systemd out of the box).

> 3.Please start some IRC chat so we can get live help from your team.

Well, this is an Open Source project, right. Thus you are free to use it 
(and to contribute!) and people are willing to help you. But I would 
give you the helpful advice not to expect community channels to provide 
free full-time commercial support for you!
For now, I read your request as "Do you have an official IRC channel?" 
and have to answer "No, we don't have." That is simply because we cannot 
guarantee that there will be someone available for discussion in a 
period of time that would not frustrate the questioner.

For now I assume asynchronous mail communication or GitHub Issues/Pull 
Requests are the appropriate format for this project.

If you really need commercial support for you project, feel free to 
contact my company, Pengutronix.


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

Re: [RAUC] Errors in Using Rauc

[Enrico Joerns]

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