Re: http protocol and a unknown image type causes a reboot

> I don't know exactly what the problem is here, but one point worth noting 
> is that the behaviour for 'unknown' images (i.e. images without any 
> recognisable magic) will be affected by the presence or otherwise of PXE 
> support.  Since PXE images are just raw binary executables, with no 
> headers, checksums or other magic that can be used to recognise them, the 
> PXE loader will claim to recognise any files.

I know, I know, that's why I have to disable PXE so that the file I'm
loading is recogniced as unknown, otherwhise it would be recogniced as PXE.

> This means that the behaviour when downloading an unknown image should be
> 
> (a) fail with an error message, if PXE support is not present, or

This is the one that is failing, it gives the message:
"error: not a valid image" and then the machine reboots, instead of
rebooting it should output the message "Unable to load file." and then get
you back to the prompt to retry booting.

It only fails (reboots) if you try booting with http, and works ok if you
try to boot via tftp.

> Therefore, if PXE support is present, then downloading an unknown image is
> likely to result in a reboot, since you will start executing random code
> while in ring 0.  It sounds as though you are somehow managing to obtain
> the exact opposite behaviour, which is puzzling.

Nope, I was not talking about the case with PXE support present, but the
one without PXE support.

Is it clear now? or do I have to try to explain again?

Sorry for not being able to make myself clearer.

Regards...
-- 
Manty/BestiaTester -> http://manty.net


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf