5 Jun
2006
5 Jun
'06
3:09 p.m.
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.
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?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Making files is easy under the UNIX operating system. Therefore,
users tend to create numerous files using large amounts of file
space. It has been said that the only standard thing about all UNIX
systems is the message-of-the-day telling users to clean up their
files. -- System V.2 administrator's guide