From: Colin D Bennett <colin@gibibit.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: dn.tlp@gmx.net
Subject: Re: Strong Crypto Support for GRUB2
Date: Mon, 21 Jul 2008 06:48:24 -0700 [thread overview]
Message-ID: <20080721064824.5c5f840e@gibibit.com> (raw)
In-Reply-To: <20080721014952.257d99d4.dn.tlp@gmx.net>
On Mon, 21 Jul 2008 01:49:52 +0200
Simon Peter <dn.tlp@gmx.net> wrote:
> Did the message below ever arrive on the list?
>
> 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.
>
> What's missing to get my code into GRUB2 mainline?
I think you'll have to assign copyright to the FSF.
Regards,
Colin
> Thanks!
> Simon
>
> Begin forwarded message:
>
> Date: Sun, 3 Feb 2008 18:25:47 +0100
> From: Simon Peter <simon.peter@gmx.de>
> To: The development of GRUB 2 <grub-devel@gnu.org>
> Cc: Marco Gerards <mgerards@xs4all.nl>, Robert Millan
> <rmh@aybabtu.com> Subject: Re: Strong Crypto Support for GRUB2
>
>
> > Sorry for the *very* late reply.
>
> Sorry for my late reply. I wasn't subscribed anymore (and I'm still
> not) and only now I found out that you replied...
>
> Attached is my patch against current CVS with the changes you proposed
> incorporated.
>
> I'd appreciate very much if you could review this complete patch
> again. Sorry for any inconvenience with my first weird double-patch.
>
> > > +int
> > > +aes_self_test (int verbose)
> > > {
> [...]
> > > + printf ("passed\n");
> > Where does printf come from?
>
> It's in a self-test routine that's actually never included in the GRUB
> source. Shall I remove the whole thing?
>
> Thanks!
> Simon
>
>
next prev parent reply other threads:[~2008-07-21 13:49 UTC|newest]
Thread overview: 17+ 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
2008-07-21 13:48 ` Colin D Bennett [this message]
2008-07-21 20:38 ` Simon Peter
2008-07-22 22:12 ` Robert Millan
-- strict thread matches above, loose matches on Subject: below --
2007-09-13 9:16 Simon Peter
2007-11-10 17:22 ` Marco Gerards
2007-09-02 12:17 Simon Peter
2007-09-02 16:05 ` Robert Millan
2007-09-02 17:25 ` Simon Peter
2007-09-02 19:41 ` Robert Millan
2007-09-02 20:53 ` Simon Peter
2007-09-02 23:05 ` Robert Millan
2007-09-03 18:51 ` Simon Peter
2007-11-10 17:20 ` Marco Gerards
2007-09-03 9:42 ` Patrick Georgi
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=20080721064824.5c5f840e@gibibit.com \
--to=colin@gibibit.com \
--cc=dn.tlp@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox