From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Crypto Patch: Legal Issues
Date: Sat, 09 Aug 2008 17:24:23 +0200 [thread overview]
Message-ID: <87tzdudxeg.fsf@xs4all.nl> (raw)
In-Reply-To: <200808091711.07211.michael@gorven.za.net> (Michael Gorven's message of "Sat, 9 Aug 2008 17:11:01 +0200")
Hi Michael,
Michael Gorven <michael@gorven.za.net> writes:
> Two months ago[1] I announced on this list that I was working on adding
> support for LUKS encrypted partitions to GRUB. I had some queries[2]
> regarding other code which I have used, and still haven't had a proper
> response to those queries. Could someone please advise me on what needs to be
> done to get my patch integrated?? The patch includes the following pieces of
> code.
Sorry to keep you waiting. After the weekend I will have more time
and get back to you.
> Ciphers and hashes from libgcrypt: Copyright FSF, LGPL 2.1 or later
> Simon's crypto framework: Copyright Simon Peter, GPL 3
> AFsplitter: Copyright Clemens Fruhwirth, GPL 2 or later
> PBKDF2: Copyright FSF, GPL 2 or later
> Code I've written
>
> What needs to be done to convert these to compatible licenses and/or reassign
> copyright?
I was about the review Simon's patch. What is the best way to
proceed. More than one person works on this and I am confused about
how to deal with this. Would it help if Simons work got in first, or
didn't you continue with this, but did you just pick pieces of code
from him instead?
--
Marco
next prev parent reply other threads:[~2008-08-09 15:21 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 [this message]
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
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=87tzdudxeg.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--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.