Sw version based downgrade prevention #1239
Conversation
mateo-ligne-netatmo
force-pushed
the
SW-version-Based-downgrade-prevention
branch
from
70cef4b to
61f392a
Compare
mateo-ligne-netatmo
force-pushed
the
SW-version-Based-downgrade-prevention
branch
from
61f392a to
d214fde
Compare
| @@ -22,8 +22,8 @@ | |||
| #include "bootutil/bootutil_log.h" | |||
| #include <usb/usb_device.h> | |||
|
|
|||
| #if defined(CONFIG_BOOT_SERIAL_UART) && defined(CONFIG_UART_CONSOLE) | |||
| #error Zephyr UART console must been disabled if serial_adapter module is used. | |||
| #if DT_SAME_NODE(DT_CHOSEN(zephyr_uart_mcumgr), DT_CHOSEN(zephyr_console)) | |||
There was a problem hiding this comment.
This check is here for prevent an ademption to usage the same uart device concurrently by diffrent software entities.
There is nothing bad in having the same node for already disabled console for instance.
There was a problem hiding this comment.
Yes, but what about the case where we want to have UART console and DFU over UART on two separate UART device ? As far as I understood this check disallow this possibility, whereas my changes enable it if console UART and MCUmgr UART are 2 differents devices.
There was a problem hiding this comment.
@de-nordic Can you take a look on this and the next line?
mateo-ligne-netatmo
force-pushed
the
SW-version-Based-downgrade-prevention
branch
from
d214fde to
efcbd14
Compare
mateo-ligne-netatmo
force-pushed
the
SW-version-Based-downgrade-prevention
branch
from
efcbd14 to
558148e
Compare
mateo-ligne-netatmo
force-pushed
the
SW-version-Based-downgrade-prevention
branch
from
558148e to
0a246dc
Compare
|
Hello, I have rebased my PR with current MCUboot main especially following #1255. It turns out that on a failed firmware update (for too low SW version for instance), stored binary won't be overwritten but it will be decrypted a second time which will break the applicative. To counter that, I've just had a return code check before decryption. |
This commit purpose is to allow the use of UART console and Serial
recovery UART in a same firmware as long as they are associated to two
separate UART devices.
To ensure this we compare following devices defined in dts file :
zephyr_uart_mcumgr : UART associated to DFU process
zephyr_console : UART used for console
Signed-off-by: Mateo Ligne <[email protected]>
In a serial recovery configuration, software based downgrade prevention option cannot be used for now as it is designed to trigger a software version comparison only before a swap in a 2 slots MCUboot configuration In fact, serial recovery update will overwrite 1st slot on every update, so this check won't be done on the reception of a new firmware. This commit tackles this issue as it implements the comparison of software versions on the reception of the first update chunk (which contains the image header). So, if CONFIG_MCUBOOT_DOWNGRADE_PREVENTION option is selected, a comparison will be done between stored and incoming firmware. If the stored firmware version is strictly superior to incoming one, flash writing will be bypassed and an error code will be sent to upgrade sender. Otherwise, the update process is done and stored firmware is overwritten. Signed-off-by: Mateo Ligne <[email protected]>
Signed-off-by: Mateo Ligne <[email protected]>
mateo-ligne-netatmo
force-pushed
the
SW-version-Based-downgrade-prevention
branch
from
0a246dc to
9f81652
Compare
|
I believe @utzig concerns have been addressed. |
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
Hello everyone,
This PR follow a previous issue where I express my need of having a software version comparison before loading a new firmware through Recovery uart in a Single application slot configuration.
The firmware update will be monitored by MCUmgr, and in order to stop the update from it, I defined a new error type that will stop update process. This MCUmgr feature is the following open PR
I also added a commit allowing to use 2 UART peripheral at the same time one for Logs and the other for MCUmgr communication.
It's my first MCUBoot upload so don't hesitate to make feedbacks or suggestions, I will take them into account !