From: Luigi 'Comio' Mantellini <luigi.mantellini@idf-hit.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] New Image format: headers hashes.
Date: Thu, 27 Mar 2008 23:26:26 +0100 [thread overview]
Message-ID: <1206656786.13734.5.camel@localhost> (raw)
In-Reply-To: <1206634003.13666.14.camel@localhost>
Continuing my monologue:
An observation about the fit_image_check_hashes and fit_image_set_hashes
functions:
- The hashes protect only the data sections of the image nodes...
ignoring the others fields (like "load", "entry", etc...). I don't like
this :S I think that the hash values must protect all fields of a node
(like the "old" image format).
to be continue...
ciao
luigi
On gio, 2008-03-27 at 17:06 +0100, Luigi 'Comio' Mantellini wrote:
> On gio, 2008-03-27 at 12:13 +0100, Luigi 'Comio' Mantellini wrote:
> >
> >
> > - The mkimage calculate hashes before that timestamp is added to
> > image.
> > is it better exchange the order of these operations (before add
> > timestamp then calculate hashes)?
> > - Does the new format assure that the complete image (_all_
> > sections,
> > images, ramdisks, configurations, blobs) are covered by at least an
> > hash
> > value? should mkimage add at least a hash value for the root node?
> >
>
> In addition to the previous question:
>
> - I'm interested to calculate and store from U-boot code but the
> fit_image_set_hashes is compiled only when the USE_HOSTCC symbol is
> defined. Why? Is there a particular reason? I think that a lot of
> useful functions (ifdef-ed by USE_HOSTCC) should be available also in
> u-boot code, anyway the linker will drop the unused functions.
>
>
> Any comments?
>
> thanks
>
> luigi
--
______ Luigi Mantellini
.'______'. R&D - Software
(.' '.) Industrie Dial Face S.p.A.
( :=----=: ) Via Canzo, 4
('.______.') 20068 Peschiera Borromeo (MI), Italy
'.______.' Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
Ind. Dial Face Email: luigi.mantellini at idf-hit.com
www.idf-hit.com GPG fingerprint: 3DD1 7B71 FBDF 6376 1B4A
B003 175F E979 907E 1650
next prev parent reply other threads:[~2008-03-27 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 11:13 [U-Boot-Users] New Image format: headers hashes Luigi 'Comio' Mantellini
2008-03-27 16:06 ` Luigi 'Comio' Mantellini
2008-03-27 22:26 ` Luigi 'Comio' Mantellini [this message]
2008-04-03 9:31 ` Bartlomiej Sieka
2008-04-03 9:51 ` Luigi 'Comio' Mantellini
2008-04-03 11:48 ` Bartlomiej Sieka
2008-04-03 12:55 ` Luigi 'Comio' Mantellini
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=1206656786.13734.5.camel@localhost \
--to=luigi.mantellini@idf-hit.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