From: Rohit Sharma <rohits79@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Secure Firmware + Firmware Upgrade?
Date: Mon, 05 Jun 2006 15:21:48 +0530 [thread overview]
Message-ID: <op.tan20mdsdfxu59@sys.t-mobile.de> (raw)
In-Reply-To: <20060605130906.3FCDA352655@atlas.denx.de>
On Mon, 05 Jun 2006 18:39:06 +0530, Wolfgang Denk <wd@denx.de> wrote:
> In message <op.tanxj1fkdfxu59@sys.t-mobile.de> you wrote:
>>
>> The only issue i see for now is that the image header structure won't
>> accomodate
>> the Digital signature string i.e. "image_header_t" and it has to be
>> appended at the
>> end of the firmware data blob.
>
> You could write the signature to a separate file and use a multi-file
> image to combine image and signature.
Thanks for the suggestion!!!
>> Due the nature of the product this is possible but than again the
>> warranty
>> would void if some one updates the software by themselves.
>
> The same is true if someone loads and runs an image that was not
> officially released - so why goong through all this effort just to
> make it more difficult to someone who *wants* to ignore the warranty?
Due to the very nature any corrupted image can be actually turn out to
be futile for the very person. Its for their safety only.
Thanks for your kind help.
Best Regards
rohit
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
prev parent reply other threads:[~2006-06-05 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 12:56 [U-Boot-Users] Secure Firmware + Firmware Upgrade? Rohit
2006-06-02 20:24 ` Wolfgang Denk
2006-06-05 1:43 ` Rohit Sharma
2006-06-05 8:57 ` Wolfgang Denk
2006-06-05 6:10 ` Rohit Sharma
2006-06-05 7:53 ` Rohit Sharma
2006-06-05 13:09 ` Wolfgang Denk
2006-06-05 9:51 ` Rohit Sharma [this message]
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=op.tan20mdsdfxu59@sys.t-mobile.de \
--to=rohits79@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