From: Jan Alsenz <janalsenz@student.ethz.ch>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: SHA-1 MBR
Date: Sat, 21 Feb 2009 00:06:20 +0100 [thread overview]
Message-ID: <499F376C.60906@student.ethz.ch> (raw)
In-Reply-To: <499F25B0.8000202@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
Hi!
Wow, cool work!
It's not complete SHA-1, but the rest should be just a constant offset.
But I'm still not sure, what you are trying to do here, is the MBR your root of
trust?
If not, who checks the MBR?
Greets,
Jan
phcoder wrote:
> Hello, as promised I wrote an mbr which performs SHA-1. To squeeze the
> code I had to remove chs and to change the bootdrive installer will have
> to overwrite corresponding instruction. SHA-1 implemented in it is
> little-endian and without padding. Standard version is big-endian and
> with padding. In this case padding is unnecessary since a sector is
> always 512 bytes. Litt-le endian means just that data isn't byte-swapped
> before hashing. And the hash in sector has to be written in little
> endian and the double should be in order
> h1,h2,h3,h4,h0
> I also implemented the same thing as standalone program
> Regards
> Vladimir 'phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-20 23:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 21:50 SHA-1 MBR phcoder
2009-02-20 23:06 ` Jan Alsenz [this message]
2009-02-20 23:41 ` phcoder
2009-02-21 0:32 ` Jan Alsenz
2009-02-21 1:02 ` Isaac Dupree
2009-02-21 1:21 ` Javier Martín
2009-02-21 9:43 ` phcoder
2009-02-21 8:56 ` Jan Alsenz
2009-02-21 13:27 ` phcoder
2009-02-21 14:12 ` phcoder
-- strict thread matches above, loose matches on Subject: below --
2009-02-21 2:21 Alex Besogonov
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=499F376C.60906@student.ethz.ch \
--to=janalsenz@student.ethz.ch \
--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.