public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [swupdate] Re: SWUpdate - U-Boot environment library dependency
Date: Wed, 21 Nov 2018 18:06:56 +0100	[thread overview]
Message-ID: <97f8b0ec-103b-e9b7-42ed-e1922f6d489a@gmail.com> (raw)
In-Reply-To: <e7751e81-610b-9cdd-e14d-04fc5b7a297f@gmail.com>

On 21.11.2018 16:48, Simon Goldschmidt wrote:
> On 21.11.2018 16:41, Wolfgang Denk wrote:
>> Dear Simon,
>>
>> In message <CAAh8qsyopV-HftdCWMbMu+fdcpqWWQtBnZDDyqFyv6iC1eoCDA@mail.gmail.com> you wrote:
>>>> Only if you use signed images.  With plain U-Boot, there is not even
>>>> a checksum for it...
>>> When SPL loads U-Boot from a legacy image, isn't there a CRC involved over
>>> the full image including the environment?
>> Yes, but when - for example - the compiled in default environment
>> gets corrupted while loading from the storage device or while
>> writing it to RAM, there will be zero check when reading it.
> Hmm, on my board, SPL loads U-Boot from NOR to SDRAM, then checks the
> uimage CRC. I'd say this is enough checks. That might not hold for all
> boards though.

Oops, I'll have to take that back. I just checked and SPL *does* boot 
the uImage U-Boot also if I deliberately corrupt the CRC of the image. 
So you're right, it seems to be not protected at all!

Is that expected behaviour or a bug?


Simon

  parent reply	other threads:[~2018-11-21 17:06 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 10:30 [U-Boot] SWUpdate - U-Boot environment library dependency Andreas Reichel
2018-11-20 21:11 ` Simon Goldschmidt
2018-11-20 23:10   ` Marek Vasut
2018-11-21  9:10     ` [U-Boot] [swupdate] " Stefano Babic
2018-11-21  9:20       ` Wolfgang Denk
2018-11-21 14:31         ` Marek Vasut
2018-11-21 14:56           ` Stefano Babic
2018-11-21 15:31             ` [U-Boot] " Simon Goldschmidt
2018-11-21 15:34               ` Marek Vasut
2018-11-21 16:23       ` [U-Boot] [swupdate] " Otavio Salvador
2018-11-21  8:31   ` [U-Boot] " Wolfgang Denk
2018-11-21  9:33     ` [U-Boot] [swupdate] " Stefano Babic
2018-11-21 10:14       ` Simon Goldschmidt
2018-11-21 10:22         ` Jan Kiszka
2018-11-21 10:49         ` Stefano Babic
2018-11-21 11:45           ` Wolfgang Denk
2018-11-21 11:56             ` Simon Goldschmidt
2018-11-21 12:22               ` Wolfgang Denk
2018-11-21 13:30             ` Stefano Babic
2018-11-21 14:27               ` Wolfgang Denk
2018-11-21 14:37                 ` Simon Goldschmidt
2018-11-21 15:01                   ` Stefano Babic
2018-11-21 15:41                   ` Wolfgang Denk
2018-11-21 15:48                     ` Simon Goldschmidt
2018-11-21 15:56                       ` Wolfgang Denk
2018-11-21 17:06                       ` Simon Goldschmidt [this message]
2018-11-22 14:22                         ` Wolfgang Denk
2018-11-22 14:41                           ` Simon Goldschmidt
2018-11-22 16:00                             ` Wolfgang Denk
2018-11-22 16:05                               ` Simon Goldschmidt
2018-11-21 11:38       ` Wolfgang Denk
2018-11-21 13:16         ` Stefano Babic
2018-11-21 14:23           ` Wolfgang Denk
2018-11-21 15:13             ` Simon Goldschmidt
2018-11-21  9:19   ` Stefano Babic
2018-11-21 10:02     ` Jan Kiszka
2018-11-21 10:21     ` Simon Goldschmidt
2018-11-21 11:05       ` Stefano Babic
2018-11-21 11:13         ` Simon Goldschmidt
2018-11-21 11:52           ` Stefano Babic
2019-03-04 16:26   ` Stefano Babic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=97f8b0ec-103b-e9b7-42ed-e1922f6d489a@gmail.com \
    --to=simon.k.r.goldschmidt@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox