From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] ntldr support
Date: Mon, 10 Aug 2009 23:00:09 +0200 [thread overview]
Message-ID: <4A808A59.7080200@t-online.de> (raw)
In-Reply-To: <d7ead6de0908101255o5bd5a256w2dec7fc9598ceae6@mail.gmail.com>
Vladimir 'phcoder' Serbinenko wrote:
>> grub4dos checks for ntldr as follows:
>> - file starts with 0xe9, 0x??, 0x01,
>> - first sector does not end with bootsector signature 0x55,0xaa,
>> - file size exceeds 0x30000.
>>
> For me it sounds like a heuristic. I would prefer to trust user rather
> than introducing heuristics to check file type.
>
I agree that such a heuristic is not needed. Grub2 uses different
commands for different loaders (which is good) and therefore there is no
need to auto-detect the loader type.
But a simple health check (like in 'chainloader') would IMO make sense
for any load command. For 'ntldr': check that the file size is
reasonable and that code starts with a jmp instruction. Allow to
override the check with '--force'.
--
Regards,
Christian Franke
next prev parent reply other threads:[~2009-08-10 21:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 23:24 [PATCH] ntldr support Robert Millan
2009-08-04 18:36 ` Christian Franke
2009-08-04 19:27 ` Robert Millan
2009-08-04 20:09 ` Vladimir 'phcoder' Serbinenko
2009-08-05 5:35 ` Christian Franke
2009-08-07 10:58 ` Robert Millan
2009-08-07 11:17 ` Michal Suchanek
2009-08-07 11:43 ` Robert Millan
2009-08-07 22:55 ` Michal Suchanek
2009-08-08 21:44 ` Christian Franke
2009-08-08 11:45 ` Yves Blusseau
2009-08-08 11:55 ` Vladimir 'phcoder' Serbinenko
2009-08-08 21:57 ` Christian Franke
2009-08-10 11:52 ` Robert Millan
2009-08-10 18:57 ` Christian Franke
2009-08-10 19:55 ` Vladimir 'phcoder' Serbinenko
2009-08-10 21:00 ` Christian Franke [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-25 23:28 Nando
2009-10-26 1:05 ` Robert Millan
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=4A808A59.7080200@t-online.de \
--to=christian.franke@t-online.de \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.