Ignore Hash Verification

[Jonas Strunz]

Hi!

We've started to activate the hash verification in our software components. For some legacy devices in the field, the update now  fails because hash verification was not activated in the swupdate service:
ERROR core/parser.c : check_hash_absent : 52 : hash verification not enabled but hash supplied for onboarding.service
ERROR core/stream_interface.c : extract_files : 165 : Compatible SW not found
Image invalid or corrupted. Not installing ...

Can we make our legacy devices accept the swupdate packages with hash verification without changing the swupdate service configuration?

Best regards, 
Jonas Strunz

[Stefano Babic]

Hi Jonas,

On 25.04.24 17:58, Jonas Strunz wrote:
>
> Hi!
>
> We've started to activate the hash verification in our software
> components. For some legacy devices in the field, the update now  fails
> because hash verification was not activated in the swupdate service:
> ERROR core/parser.c : check_hash_absent : 52 : hash verification not
> enabled but hash supplied for onboarding.service

It cannot work - if hash is provided, update is considered faulty if not
verified.

> ERROR core/stream_interface.c : extract_files : 165 : Compatible SW not
> found
> Image invalid or corrupted. Not installing ...
>
> Can we make our legacy devices accept the swupdate packages with hash
> verification without changing the swupdate service configuration?

You have to build a SWU from the same artifacts (that is, it contains a
swupdate able to compute hashes), and this is accepted by all devices.

A later version could be deployed with hashes in sw-description.

Best regards,
Stefano Babic

[Jonas Strunz]

Hi Stefano,

thanks for the quick answer.

 

So you would recommend to update swupdate service with an swupdate package? did I understand it correctly?

Best regards,

Jonas

[Stefano Babic]

On 25.04.24 18:23, Jonas Strunz wrote:
> Hi Stefano,
>
> thanks for the quick answer.
> So you would recommend to update swupdate service with an swupdate
> package? did I understand it correctly?

You have to update first with a version containing a SWupdate that can.
How this is done, it is your choice. You can update a full rootfs (==>
new version of software), that is ready to accept hash verification in
future.

Best regards,
Stefano

> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/swupdate/4648c28d-5c2e-4aff-8401-7067d2e5ffbfn%40googlegroups.com <https://groups.google.com/d/msgid/swupdate/4648c28d-5c2e-4aff-8401-7067d2e5ffbfn%40googlegroups.com?utm_medium=email&utm_source=footer>.