From: Michael Gorven <michael@gorven.za.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Crypto Patch: Legal Issues
Date: Sat, 9 Aug 2008 17:11:01 +0200 [thread overview]
Message-ID: <200808091711.07211.michael@gorven.za.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Hi
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.
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?
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/msg00184.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 --]
next reply other threads:[~2008-08-09 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 15:11 Michael Gorven [this message]
2008-08-09 15:24 ` Crypto Patch: Legal Issues 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
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=200808091711.07211.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.