From: Daniel Axtens <dja@axtens.net>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
The development of GNU GRUB <grub-devel@gnu.org>
Cc: rashmica.g@gmail.com, alastair@d-silva.org
Subject: Re: [PATCH 08/18] libtasn1: import libtasn1-4.16.0
Date: Wed, 07 Oct 2020 10:54:13 +1100 [thread overview]
Message-ID: <87pn5ux656.fsf@dja-thinkpad.axtens.net> (raw)
In-Reply-To: <20201002175858.GA14414@char.us.oracle.com>
Hi Konrad,
>> +LICENSING
>> +=========
>> +
>> +The libtasn1 library is released under the GNU Lesser General Public
>> +License (LGPL) version 2.1 or later; see [COPYING.LESSER](doc/COPYING.LESSER)
>> +for the license terms.
>> +
>> +The GNU LGPL applies to the main libtasn1 library, while the
>> +included applications library are under the GNU GPL version 3.
>> +The libtasn1 library is located in the lib directory, while the applications
>> +in src/.
>
> GRUB is GPL-v3. This is not.
>
> Can you re-license it to be GPL-v3?
I believe we can combine and ship these together: any distribution of
grub that is compliant with GPLv3+ will also be compliant with
LGPLv2.1+. I source this from:
https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses
https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility
Or are you suggesting that we should additionally re-license the files
we import from LGPL to GPL per section 3 of LGPL2.1?
| 3. You may opt to apply the terms of the ordinary GNU General Public
| License instead of this License to a given copy of the Library. To do
| this, you must alter all the notices that refer to this License, so
| that they refer to the ordinary GNU General Public License, version 2,
| instead of to this License. (If a newer version than version 2 of the
| ordinary GNU General Public License has appeared, then you can specify
| that version instead if you wish.) Do not make any other change in
| these notices.
I don't have strong feelings either way.
We already include MIT-licensed "jsmn" code our GPLv3 json module, so it
wouldn't be a change from our usual practice to include GPLv3-compatible
code by wrapping it in a module that claims GPLv3.
Kind regards,
Daniel
next prev parent reply other threads:[~2020-10-06 23:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 5:13 [PATCH 00/18] Verify appended signatures from grub Daniel Axtens
2020-10-02 5:13 ` [PATCH 01/18] docs/grub: grub-install is no longer a shell script Daniel Axtens
2020-10-02 5:13 ` [PATCH 02/18] docs/grub: --pubkey has been supported for some time Daniel Axtens
2020-10-02 5:13 ` [PATCH 03/18] dl: provide a fake grub_dl_set_persistent for the emu target Daniel Axtens
2020-10-02 5:13 ` [PATCH 04/18] verifiers: factor unsafe module handling out of shim_lock Daniel Axtens
2020-10-02 5:13 ` [PATCH 05/18] pgp: factor out rsa_pad Daniel Axtens
2020-10-02 5:13 ` [PATCH 06/18] crypto: move storage for grub_crypto_pk_* to crypto.c Daniel Axtens
2020-10-02 5:13 ` [PATCH 07/18] posix_wrap: tweaks in preparation for libtasn1 Daniel Axtens
2020-10-02 5:13 ` [PATCH 08/18] libtasn1: import libtasn1-4.16.0 Daniel Axtens
2020-10-02 17:58 ` Konrad Rzeszutek Wilk
2020-10-06 23:54 ` Daniel Axtens [this message]
2020-10-02 5:13 ` [PATCH 09/18] libtasn1: disable code not needed in grub Daniel Axtens
2020-10-02 5:13 ` [PATCH 10/18] libtasn1: changes for grub compatibility Daniel Axtens
2020-10-02 5:13 ` [PATCH 11/18] libtasn1: compile into asn1 module Daniel Axtens
2020-10-02 5:13 ` [PATCH 12/18] test_asn1: test module for libtasn1 Daniel Axtens
2020-10-02 5:13 ` [PATCH 13/18] grub-install: support embedding x509 certificates Daniel Axtens
2020-10-12 3:38 ` Daniel Axtens
2020-10-02 5:13 ` [PATCH 14/18] appended signatures: import GNUTLS's ASN.1 description files Daniel Axtens
2020-10-02 5:13 ` [PATCH 15/18] appended signatures: parse PKCS#7 signedData and X.509 certificates Daniel Axtens
2020-10-02 5:13 ` [PATCH 16/18] appended signatures: support verifying appended signatures Daniel Axtens
2020-10-02 5:13 ` [PATCH 17/18] appended signatures: verification tests Daniel Axtens
2020-10-02 5:13 ` [PATCH 18/18] appended signatures: documentation Daniel Axtens
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=87pn5ux656.fsf@dja-thinkpad.axtens.net \
--to=dja@axtens.net \
--cc=alastair@d-silva.org \
--cc=grub-devel@gnu.org \
--cc=konrad.wilk@oracle.com \
--cc=rashmica.g@gmail.com \
/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