From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 33300@debbugs.gnu.org
Subject: bug#33300: Automatically detecting binaries in source tarballs
Date: Thu, 08 Nov 2018 09:50:23 +0100 [thread overview]
Message-ID: <87y3a454xc.fsf@gnu.org> (raw)
In-Reply-To: <20181108005701.2e76fd3d@scratchpost.org> (Danny Milosavljevic's message of "Thu, 8 Nov 2018 00:57:01 +0100")
Hello,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> I think it would be good to have guix check for closed-source binaries after
> unpacking, automatically (including jar files with class files in them).
Oh right, jars are certainly quite common, more than .so files.
>> > No idea if it's worth the trouble/performance hit/false-positive rate,
>> > of course. That's for the ner^Wgods to decide.
>>
>> Yeah I wonder if it would be fruitful.
>
> Marking known-good binaries (whitelisting) is still better than hoping
> we notice some closed-source binary (blacklisting).
>
> It would be a conspicious reminder of what we still have to do - as
> opposed to the situation now where it's mostly in someone's head
> (if at all).
Yeah, that makes sense.
What about adding such a phase in %standard-phases in core-updates-next?
I guess it could check for files that match ‘elf-file?’ or ‘ar-file?’
and for *.jar. WDYT?
We must make add a keyword parameter in ‘gnu-build-system’ to make it
easy to disable it and/or to skip specific files.
Any takers?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-11-08 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 10:19 bug#33300: hplip 3.18.9 contains non-free binary blobs Ludovic Courtès
2018-11-07 12:48 ` Efraim Flashner
2018-11-07 14:34 ` Ludovic Courtès
2018-11-07 13:09 ` Tobias Geerinckx-Rice
2018-11-07 14:41 ` Ludovic Courtès
2018-11-07 23:57 ` bug#33300: Automatically detecting binaries in source tarballs Danny Milosavljevic
2018-11-08 8:50 ` Ludovic Courtès [this message]
2018-11-08 23:11 ` Björn Höfling
2018-11-11 7:23 ` Efraim Flashner
2018-11-11 17:28 ` Ludovic Courtès
2018-11-11 17:30 ` bug#33300: hplip 3.18.9 contains non-free binary blobs Ludovic Courtès
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=87y3a454xc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33300@debbugs.gnu.org \
--cc=dannym@scratchpost.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 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.