Jan Lübbe

Setting [CURLOPT_SSL_VERIFYHOST](https://curl.se/libcurl/c/CURLOPT_SSL_VERIFYHOST.html) to 0 would accept any valid certificate, making MitM attacks very easy. Accordingly we don't intend to support this, as you could also just use plain HTTP. Instead,...

We have the necessary information in the slot status file (ideally in a shared data partition with `data-directory=/data/rauc` or `statusfile=/data/central.raucs`). That information is already available via D-Bus. With the refactoring...

The best place to add it would likely be in `prepare_environment()` here: https://github.com/rauc/rauc/blob/master/src/install.c#L586

@obbardc Perhaps #1400 can also handle your requirements?

The `readonly` flag lets rauc know about the slot, but it will never write to it. This is also the trigger for the Installation error you see. As a installing...

Closing this as done. If there is still something missing, please reopen.

HTTP streaming is supported since [version v1.7](https://github.com/rauc/rauc/releases/tag/v1.7), see https://rauc.readthedocs.io/en/latest/advanced.html#http-streaming for details.

We don't have plans to implement this and have not seen other requests for this feature. Currently, D-Bus support is deeply integrated with RAUC's service part, so adding another RPC...

For raw and tar images, we now have fine-grained progress information thanks to #1093. With regards to casync, there is currently no real activity, so we don't have concrete plans...

We've seen bugs in the kernel drivers for other crypto accelerators, so perhaps you could disable the `atmel-sha` driver (`CRYPTO_DEV_ATMEL_SHA`) and use the software implementation instead. That should help you...