From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GRUB and network (was Re: GRUB and Google Summer of Code)
Date: Fri, 02 Apr 2010 14:48:12 +0200 [thread overview]
Message-ID: <4BB5E78C.10108@gmail.com> (raw)
In-Reply-To: <4BB53659.6010606@isaac.cedarswampstudios.org>
[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]
Isaac Dupree wrote:
> On 04/01/10 16:59, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>> There is already some crypto imported for password support so adding
>>> enough to have SSL would hopefully not be too difficult.
>>>
>> Not true. Although we have ciphers and hashes we don't have either
>> asymetric algorithms or random generator. The first is easy to import
>> but generating random numbers involves gathering entropy which is
>> cornerstone of network cryptography. Without a good random number
>> generator most SSL algorithms will only make the user happier without
>> adding any security against attacker.
>
> Is it reasonable to generate some random data during grub-install, and
> write it to the disk, where GRUB will then use it?
It is possible but there following problems:
1) This file has to be kept secret. In cases when one can be reasonably
sure GRUB wasn't tempered with but isn't sure it's still secret (e.g.
distribution of signed file), it's pretty much useless.
2) You can never ever use same entropy twice. So you will need to save
some kind of pointer where the last used entropy is. And when all
entropy was used we're back at square one. It's possible to save the
random number generator state instead but then random number isn't often
reseeded and so the smallest flaw in its algorithm is relatively easily
usable.
> Maybe in combination with real-time clock,
Point of random numbers is being unpredictable. RTC is predictable as a
clock.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2010-04-02 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 19:10 GRUB and Google Summer of Code Vladimir 'φ-coder/phcoder' Serbinenko
2010-03-30 14:31 ` Michal Suchanek
2010-03-30 17:26 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-03-30 18:46 ` Alex Zanetti de Lima
2010-04-01 16:11 ` Michal Suchanek
2010-04-01 20:59 ` GRUB and network (was Re: GRUB and Google Summer of Code) Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-02 0:12 ` Isaac Dupree
2010-04-02 12:48 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-04-01 21:06 ` GRUB and network (Re: " Vladimir 'φ-coder/phcoder' Serbinenko
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=4BB5E78C.10108@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 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.