From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30827@debbugs.gnu.org
Subject: [bug#30827] [PATCH] gnu: util-linux: Fix CVE-2018-7738.
Date: Mon, 19 Mar 2018 16:52:21 -0400 [thread overview]
Message-ID: <20180319205221.GA20036@jasmine.lan> (raw)
In-Reply-To: <871sggv32t.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
On Mon, Mar 19, 2018 at 10:15:22AM +0100, Ludovic Courtès wrote:
> Hello!
>
> Leo Famulari <leo@famulari.name> skribis:
>
> > * gnu/packages/patches/util-linux-CVE-2018-7738.patch: New file.
> > * gnu/local.mk (dist_patch_DATA): Add it.
> > * gnu/packages/linux.scm (util-linux)[replacement]: New field.
> > (util-linux/fixed): New variable.
>
> [...]
>
> > +https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7738
> > +
> > +Patch copied from upstream source repository:
> > +
> > +https://github.com/karelzak/util-linux/commit/75f03badd7ed9f1dd951863d75e756883d3acc55
>
> I’m late to the party, but I’m wondering in this case if, instead of
> grafting, we should simply add an util-linux@2.31a package, and make
> sure GuixSD uses that one in %base-packages.
>
> That way, both GuixSD and manually installed util-linux would get the
> Bash completion fix. It’s probably OK that packages that depend on
> util-linux don’t get the fixed version because users don’t get bash
> completion from there.
>
> WDYT?
That's a good idea. I'll test and push today.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-19 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 17:58 [bug#30827] [PATCH] gnu: util-linux: Fix CVE-2018-7738 Leo Famulari
2018-03-16 14:13 ` Marius Bakke
2018-03-19 9:15 ` Ludovic Courtès
2018-03-19 20:52 ` Leo Famulari [this message]
2018-03-19 22:15 ` Leo Famulari
2018-03-20 1:23 ` Marius Bakke
2018-03-20 8:47 ` Ludovic Courtès
2018-03-20 21:17 ` Leo Famulari
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=20180319205221.GA20036@jasmine.lan \
--to=leo@famulari.name \
--cc=30827@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 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.