From: Pierre Neidhardt <ambrevar@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 31487@debbugs.gnu.org
Subject: [bug#31487] [PATCH] gnu: Add upx.
Date: Sun, 27 May 2018 15:46:48 +0200 [thread overview]
Message-ID: <87muwli52v.fsf@gmail.com> (raw)
In-Reply-To: <87lgc6yy1t.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> There’s one issue left though:
>
> $ ./pre-inst-env guix lint upx
> gnu/packages/compression.scm:2179:2: upx@3.94: probably vulnerable to CVE-2017-15056, CVE-2017-16869
>
> Could you check whether patches are available for these? Better be safe
> than sorry!
Indeed they are.
They are not on the master branch though, only devel I think.
So what's the protocol here? Shall we cherry-pick the fixing commits or
get latest devel?
--
Pierre Neidhardt
The day advanced as if to light some work of mine; it was morning,
and lo! now it is evening, and nothing memorable is accomplished.
-- H.D. Thoreau
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-05-27 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 22:51 [bug#31487] [PATCH] gnu: Add upx Pierre Neidhardt
2018-05-18 6:46 ` Pierre Neidhardt
2018-05-26 20:14 ` Ludovic Courtès
2018-05-27 13:46 ` Pierre Neidhardt [this message]
2018-05-28 7:55 ` Ludovic Courtès
2018-05-29 6:42 ` Pierre Neidhardt
2018-05-29 13:27 ` Ludovic Courtès
2018-06-15 7:12 ` Ludovic Courtès
2018-06-16 14:58 ` Pierre Neidhardt
2018-06-16 19:15 ` Pierre Neidhardt
2018-06-16 14:54 ` [bug#31487] [PATCH] gnu: upx: Fix CVE-2017-15056 Pierre Neidhardt
2018-06-16 21:57 ` bug#31487: " 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
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=87muwli52v.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=31487@debbugs.gnu.org \
--cc=ludo@gnu.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).