From: Maxime Devos <maximedevos@telenet.be>
To: Vagrant Cascadian <vagrant@debian.org>, Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, 34717@debbugs.gnu.org
Subject: bug#34717: GPL and Openssl incompatibilities in u-boot and possibly others
Date: Sat, 23 Oct 2021 09:08:24 +0000 [thread overview]
Message-ID: <c4b60036e9aa7d2459f6ed2a71cfc274206b6b70.camel@telenet.be> (raw)
In-Reply-To: <87fsssoj6z.fsf@yucca>
Vagrant Cascadian schreef op vr 22-10-2021 om 14:15 [-0700]:
> [...]
> 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).
Add openssl to #:disallowed-references. Then the build will fail
if the store item has a reference to openssl.
This most likely won't catch uses of the _static_ OpenSSL libraries
though, so the "openssl:static" input would need to be removed for
this approach to work.
Greetings,
Maxime.
--
not hacking on guix for a while, only occassionally looking at IRC logs
and bug reports. E-mails are unsigned until backup is located.
next prev parent reply other threads:[~2021-10-23 9:09 UTC|newest]
Thread overview: 17+ 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
[not found] ` <87y26loa74.fsf@yucca>
[not found] ` <YXMgmR33gtyA8tgZ@jasmine.lan>
[not found] ` <87fsssoj6z.fsf@yucca>
2021-10-23 9:08 ` Maxime Devos [this message]
[not found] ` <87cznwoj2q.fsf@yucca>
[not found] ` <YXRmAoyt3X3DNTeX@jasmine.lan>
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4b60036e9aa7d2459f6ed2a71cfc274206b6b70.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=34717@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).