From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GRUB and the risk of block list corruption in extX
Date: Tue, 19 Feb 2013 16:48:18 +0100 [thread overview]
Message-ID: <51239EC2.5040203@gmail.com> (raw)
In-Reply-To: <512376DB.6000908@ts.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
On 19.02.2013 13:58, Martin Wilck wrote:
> Vladimir,
>
> thanks for your thoughtful answer. I understand your concerns better now.
>
> On 02/19/2013 10:37 AM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>
>> Suppose blocklist changes because of e.g. user mistake. Yet at the old
>> location there is still the old core.img. For the time being. So this
>> problem may go unnoticed for years yet if someone has the ability to
>> create new files on the disk in question, he creates ton of files with
>> copies of malicious sector, one of them will overwrite core and be
>> executed on next reboot.
>
> Am I understanding correctly that the user mistake you describe must be
> some manipulation of "core.img" itself (e.g. running grub2-mkimage but
> now grub2-setup, which would classify as "mistake" in a blocklist setup)?
Yes. Such kind of mistakes. Or deleting GRUB and restoring it from backup.
>
> Martin
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2013-02-19 16:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 10:47 GRUB and the risk of block list corruption in extX Martin Wilck
2013-02-08 11:44 ` Martin Wilck
2013-02-08 16:57 ` Vladimir 'phcoder' Serbinenko
2013-02-08 17:17 ` Vladimir 'phcoder' Serbinenko
2013-02-08 17:17 ` Martin Wilck
2013-02-08 18:42 ` Lennart Sorensen
2013-02-08 18:56 ` Bruce Dubbs
2013-02-08 18:58 ` Lennart Sorensen
2013-02-08 19:11 ` Andrey Borzenkov
2013-02-18 15:42 ` Martin Wilck
2013-02-09 6:22 ` Chris Murphy
2013-02-18 17:16 ` Martin Wilck
2013-02-18 21:07 ` Chris Murphy
2013-02-19 5:02 ` Andrey Borzenkov
2013-02-19 6:24 ` Chris Murphy
2013-02-19 8:43 ` Michael Chang
2013-02-19 9:06 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-02-19 18:54 ` Chris Murphy
2013-02-19 8:47 ` Martin Wilck
2013-02-19 18:56 ` Chris Murphy
2013-02-19 19:46 ` Martin Wilck
2013-02-19 9:37 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-02-19 12:58 ` Martin Wilck
2013-02-19 15:48 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-02-19 17:17 ` Martin Wilck
2013-02-19 5:26 ` Andrey Borzenkov
2013-02-19 10:54 ` Martin Wilck
2013-05-03 5:01 ` Andrey Borzenkov
2013-05-03 8:21 ` Martin Wilck
2013-05-03 19:21 ` Dr. Tilmann Bubeck
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=51239EC2.5040203@gmail.com \
--to=phcoder@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).