all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kei Kebreau <kei@openmailbox.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: ntfs-3g: Fix CVE-2017-0358.
Date: Thu, 09 Feb 2017 22:28:56 -0500	[thread overview]
Message-ID: <87k28ysozr.fsf@openmailbox.org> (raw)
In-Reply-To: <87a89usuh0.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (Marius Bakke's message of "Fri, 10 Feb 2017 02:30:35 +0100")

[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]

Marius Bakke <mbakke@fastmail.com> writes:

> Kei Kebreau <kei@openmailbox.org> writes:
>
>> Marius Bakke <mbakke@fastmail.com> writes:
>>
>>> 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 
>>
>> Are we all agreed on pushing this change?
>
> I agree with Leo that we should try to cover for all use cases of
> software from Guix, so this change LGTM.

Great! Pushed as 1a82ba660e88e731841882523084e5d878267b53.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2017-02-10  3:29 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
2017-02-10  0:42       ` Kei Kebreau
2017-02-10  1:30         ` Marius Bakke
2017-02-10  3:28           ` Kei Kebreau [this message]

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=87k28ysozr.fsf@openmailbox.org \
    --to=kei@openmailbox.org \
    --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 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.