From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: ntfs-3g: Fix CVE-2017-0358.
Date: Thu, 9 Feb 2017 23:43:46 +0100 [thread overview]
Message-ID: <20170209224346.GA20362@jasmine> (raw)
In-Reply-To: <878tpft2dt.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
On Thu, Feb 09, 2017 at 11:39:42PM +0100, Marius Bakke wrote:
> Kei Kebreau <kei@openmailbox.org> writes:
>
> > Reviewers, how does this patch look to you?
>
> AFAIU from CVE-2017-0358, ntfs-3g is only vulnerable when installed
> setuid root, which is not the case on guix.
>
> FWIW Debian do not carry this patch, but have fixed the CVE according to
> the changelog. So I doubt this patch is necessary.
There have been a couple security-related bugs publicized recently that
are only dangerous when the software is installed setuid root.
Although we don't do that by default, system administrators can do it on
GuixSD. I also think that Guix is valuable as a distribution mechanism
of free source code, and we should fix bugs for that use case.
So, I was thinking that we should fix these bugs unless they require
grafting, and then we should fix them in core-updates.
WDYT?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-02-09 22:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 21:33 [PATCH] gnu: ntfs-3g: Fix CVE-2017-0358 Kei Kebreau
2017-02-09 22:39 ` Marius Bakke
2017-02-09 22:43 ` Leo Famulari [this message]
2017-02-09 23:07 ` Marius Bakke
2017-02-10 0:42 ` Kei Kebreau
2017-02-10 1:30 ` Marius Bakke
2017-02-10 3:28 ` Kei Kebreau
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=20170209224346.GA20362@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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).