|
From: <ebi...@ln...> - 2003-07-01 23:15:28
|
Anselm Martin Hoffmeister <an...@ho...> writes: > Hello list, > > > The Multiboot Specification may be ambiguous and misleading, > > but the example code in the Specification and the implementation > > in GRUB are different from Etherboot. > > > Eric's mkelfImage is based on Etherboot's implementation > > so it should also be fixed. > > As someone has to fiddle on this multiboot stuff at all... > Eric mentioned one could implement the SECURE_BOOT (as it should be > in 5.1 CVS for some month now) for ELF multiboot as well. ELF but not ELF multiboot. The multiboot specification is not extensible. It based on the assumption you are using a.out. > Requirements to the image would be to have 64 bytes available for > usage data (the md5-hash of the whole image including this > storage-region with all 64 bytes set to zero, then encrypted with the > private key which public counterpart is compiled into etherboot...) > For more information, please have look into the 5.1 contrib section, > the "safeboot" directory. The code is (at least the non-rsaeuro code) > fairly trivial. > Just a pity I don't understand where to put 64 bytes inside multiboot > images, but I didn't even dig deeply into the MultiBoot specs. > If you give me a hint, I can implement it myself. Just using a standard ELF not should be sufficient. I have been busy lately so I haven't had a chance to really look at that stuff yet. Eric |
