From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: ntfs-3g: Fix CVE-2017-0358.
Date: Fri, 10 Feb 2017 00:07:35 +0100 [thread overview]
Message-ID: <87o9ybrmiw.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170209224346.GA20362@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
Leo Famulari <leo@famulari.name> writes:
> 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?
That does make a lot of sense. Reading up on execl(3), it looks like
this patch does the right thing and can't hurt even when not setuid.
Mind=changed! :P
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-02-09 23:07 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
2017-02-09 23:07 ` Marius Bakke [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o9ybrmiw.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.