If the chipicopwn logo appears the vulnerability should still be there?

[flecke-m]

Hi,

this is more a question than an issue.

I haven't soldered so far the UART to reach the console output, because I just wanted to check if my device (mfg date 04/2022) still has the vulnerability in u-boot. With the code from the fw-2022_01 branch the chipicopwn logo appears on the nest hub (so I though, hey it is still working).

Also it seems that the fatload command at least gets executed, because when I swap the pico to the USB Stick with the Ubuntu image and updated boot images, the screen turns black, the G logo appears but then nothing happens afterwards. It takes quite some time then the screen turns black and that its.

Could it be that there is another check on the signature of the new boot images being implemented?

I will get the UART Shell in the next couple of weeks, but maybe there is some experience already available.

Thank you.