On Wednesday 28 May 2008 16:07:09 Robert Millan wrote: > On Thu, May 22, 2008 at 03:56:53PM +0200, Michael Gorven wrote: > > 2. If I am to submit Simon's patch, what remaining issues are there with > > it? If there is a problem with the license of the ciphers I can replace > > them with suitable implementations. > > In particular, rmd160.c was problematic: > > http://lists.gnu.org/archive/html/grub-devel/2007-09/msg00005.html
I have replaced the RIPEMD160 hash with the implementation from libgcrypt. > > 3. What licenses are suitable for integration with GRUB? Most of the > > ciphers I need are available in libgcrypt[3], which is copyrighted by the > > FSF and under LGPL 2.1. I am currently using some other code which is > > under GPL 2 however -- what is the situation with that? > > FSF-copyrighted code is always ok. As for GPL 2 code, if it's not "2 or > later" it can't be legally recombined with GPL 3 code (aside from the > constraints about paperwork, see above). Both pieces of code are "2 or later". The situation is therefore as follows (excluding code written by myself and Simon): Numerous ciphers and hashes from libgcrypt: Copyright FSF and LGPL 2.1 AES cipher from Simon's patch: LGPL 2.1 Two pieces of code I've used: GPL 2 or later What needs to be done? Michael -- http://michael.gorven.za.net PGP Key ID 6612FE85 S/MIME Key ID D33AEB31
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
