All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Gorven <michael@gorven.za.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Fw: Re: Strong Crypto Support for GRUB2
Date: Mon, 21 Jul 2008 11:22:53 +0200	[thread overview]
Message-ID: <200807211122.58744.michael@gorven.za.net> (raw)
In-Reply-To: <20080721014952.257d99d4.dn.tlp@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]

On Monday 21 July 2008 01:49:52 Simon Peter wrote:
> I'm still interested in getting strong crypto into grub mainline and
> while it's still not in, I just saw you guys proposed this as a project
> for Google's summer of code. Are you going to point students at the
> code I already produced? Would be a shame if you have someone replicate
> the work already done.

Hi Simon

I've been working on a LUKS module[1] for GRUB, and have used your patch as a 
starting point. I have added a few extra functions to the crypto module, and 
implemented CBC in the crypto module itself. I have also added a number of 
ciphers and hashes[2]. I am still waiting for a proper review of my patch, 
and for some license issues to be resolved. I think that my changes have 
broken the devmapper module, but I intend to implement that functionality in 
the LUKS module some time.

Michael

[1] http://lists.gnu.org/archive/html/grub-devel/2008-05/msg00127.html
[2] http://lists.gnu.org/archive/html/grub-devel/2008-05/msg00157.html

-- 
http://michael.gorven.za.net
PGP Key ID 6612FE85
S/MIME Key ID D33AEB31

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-07-21  9:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20 23:49 Fw: Re: Strong Crypto Support for GRUB2 Simon Peter
2008-07-21  0:20 ` Pavel Roskin
2008-07-21  9:22 ` Michael Gorven [this message]
2008-07-21 13:48 ` Colin D Bennett
2008-07-21 20:38   ` Simon Peter
2008-07-22 22:12     ` 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=200807211122.58744.michael@gorven.za.net \
    --to=michael@gorven.za.net \
    --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.