From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Crypto Patch: Legal Issues
Date: Mon, 1 Sep 2008 23:53:04 +0200 [thread overview]
Message-ID: <20080901215303.GA11081@thorin> (raw)
In-Reply-To: <20080901172646.941ff40e.dn.tlp@gmx.net>
Marco, I think you're the only one who can take care of this. Please could
you have a look?
On Mon, Sep 01, 2008 at 05:26:46PM +0200, Simon Peter wrote:
> > >> In the meantime, I've assigned copyright of my work (excluding the
> > >> AES and RIPEMD implementations) to the FSF. The documents are
> > >> probably already waiting in my mailbox at home. I'll get the
> > >> signing done once I'm back home at the end of this month.
> > > I assume that I shall need to do this as well. What is the
> > > procedure for this? I couldn't find anything on the GRUB wiki, and
> > > can't find any forms on the FSF website.
> > Is anyone reviewing Michael's patch? It seems that when he mentions
> > it, no one follows up other than to make a brief comment. I am
> > presently using it and it works quite well. I would like to see it in
> > GRUB2's mainstream tree. This is a significant new capability.
>
> I'd like to join Mike in petitioning for the incorporation of Michael's
> patch into GRUB. This feature is badly needed for a secure bootup.
>
> Furthermore, my work is not really useful to end-users without all the
> ciphers that Michael implemented.
>
> Simon
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-09-01 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 15:11 Crypto Patch: Legal Issues Michael Gorven
2008-08-09 15:24 ` Marco Gerards
2008-08-09 17:11 ` Michael Gorven
2008-08-18 21:23 ` Simon Peter
2008-08-18 21:39 ` Michael Gorven
2008-08-31 2:59 ` W. Michael Petullo
2008-09-01 15:26 ` Simon Peter
2008-09-01 21:53 ` Robert Millan [this message]
2009-02-07 19:19 ` 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=20080901215303.GA11081@thorin \
--to=rmh@aybabtu.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.