From: Vagrant Cascadian <vagrant@debian.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, 34717@debbugs.gnu.org
Subject: Re: bug#34717: GPL and Openssl incompatibilities in u-boot and possibly others
Date: Fri, 22 Oct 2021 14:15:00 -0700 [thread overview]
Message-ID: <87fsssoj6z.fsf@yucca> (raw)
In-Reply-To: <YXMgmR33gtyA8tgZ@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
On 2021-10-22, Leo Famulari wrote:
> On Thu, Oct 21, 2021 at 11:17:03PM -0700, Vagrant Cascadian wrote:
>> While openssl 3.0 is licensed compatibly with GPLv3, u-boot has portions
>> which are GPLv2-only, so that's not as attractive of a way forward as
>> one might hope for...
>
> What are other distros doing? Surely we can't be the only group
> distributing u-boot?
Both fedora and (recently) debian have openssl declared as a system
library, invoking the GPL's system library exception... which I
personally find at best to be a grey area workaround.
I wouldn't be surprised if most distros simply ignore the issue
entirely.
Interestingly, today I was called in on a relevent discussion on the
u-boot mailing list:
https://lists.denx.de/pipermail/u-boot/2021-October/464529.html
Though, it is *possible* that various u-boot-BOARD in some cases doesn't
include any openssl code at all in the resulting binaries, but builds
some tools used during the build process, that are then used to produce
various cryptographic signatures in the build:
https://lists.denx.de/pipermail/u-boot/2021-October/464533.html
If that's true, it should be ok for various boards (though the
possibility of openssl code getting linked in would be hard to
catch).
u-boot-tools would still need a viable workaround, though.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-10-22 21:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 1:58 bug#34717: GPL and Openssl incompatibilities in u-boot and possibly others Vagrant Cascadian
2019-03-06 15:15 ` Ludovic Courtès
2019-03-06 18:12 ` Danny Milosavljevic
2019-03-08 9:59 ` Ludovic Courtès
2019-03-07 4:17 ` Vagrant Cascadian
2019-03-07 23:02 ` Vagrant Cascadian
2019-03-08 10:23 ` Ludovic Courtès
2019-03-08 19:14 ` Vagrant Cascadian
2019-03-09 21:57 ` Ludovic Courtès
2019-03-09 23:10 ` Vagrant Cascadian
2019-03-10 3:58 ` Jack Hill
2019-03-10 17:12 ` Ludovic Courtès
2021-10-22 6:17 ` Vagrant Cascadian
2021-10-22 20:35 ` Leo Famulari
2021-10-22 21:15 ` Vagrant Cascadian [this message]
2021-10-23 9:08 ` Maxime Devos
2021-10-22 21:17 ` Vagrant Cascadian
2021-10-23 19:44 ` Leo Famulari
2021-10-24 8:50 ` Dr. Arne Babenhauserheide
2019-03-08 10:08 ` Ludovic Courtès
2019-03-08 10:16 ` Ludovic Courtès
2019-03-15 23:55 ` Adonay Felipe Nogueira
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=87fsssoj6z.fsf@yucca \
--to=vagrant@debian.org \
--cc=34717@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.