Jan Lübbe

> I made a test where I tried to print the key. When I fetched the key from file in userspace and printed it from rauc code, it printed fine....

> The current test-suite only uses PKCS#11 for signing, while decryption is only tested with files. It should be relatively easy to extend that to decyption. I've added a test...

> I'd like to contribute on this one... anything I need to be aware of before starting work? From the user's perspective, it could probably look like `rauc -c base-system.conf...

This would need to be rebased, as https://github.com/rauc/rauc/pull/1636 has split the bootloader backends into different files.

Hmm. I would have thought that we already have something like this... We could resolve the path during config loading and store it in a new field of `RaucSlot`. This...

Can't you use verity format bundles, which don't need the access check mitigation?

Are you encountering this issue on the target device during installation or on your development host?

I've implemented the requested changes.

I've force pushed (https://github.com/rauc/rauc/compare/a87e8bd17478..80a8852a573d) to fix the test case when running it separately. The `callback_counter` must be reset for this test case as well.

Thanks for the fixes. Rebased on master.