all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: 02/02: gnu: linux-pam: Add cracklib to inputs.
Date: Sun, 28 Aug 2016 10:46:28 -0400	[thread overview]
Message-ID: <20160828144628.GA10486@jasmine> (raw)
In-Reply-To: <20160828130241.9381A220144@vcs.savannah.gnu.org>

On Sun, Aug 28, 2016 at 01:02:41PM +0000, David Craven wrote:
> dvc pushed a commit to branch core-updates
> in repository guix.
> 
> commit 25d1b3107fc7ebdc155649722fc257f4dbc4b04a
> Author: David Craven <david@craven.ch>
> Date:   Sun Aug 28 15:00:49 2016 +0200
> 
>     gnu: linux-pam: Add cracklib to inputs.
>     
>     * gnu/packages/linux.scm (linux-pam)[inputs]: Add cracklib.

Recently, some security vulnerabilities in cracklib have been disclosed
[0].

For CVE-2016-6318, the disclosure message pointed out that if
cracklib is compiled without the FORTIFY_SOURCE compiler flag, the bug
can result in code execution and privilege escalation.

Unfortunately, that applies to us. Our exposure to the bug was mitigated
by the fact that cracklib is not used by our base system (it is used in
our GNOME system, however).

For this reason, I want to revert this commit until we have begun
"hardening" our packages [1].

Any objections?

[0]
http://seclists.org/oss-sec/2016/q3/290
http://seclists.org/oss-sec/2016/q3/370

[1]
http://lists.gnu.org/archive/html/guix-devel/2016-08/msg01157.html

       reply	other threads:[~2016-08-28 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160828130241.21430.58427@vcs.savannah.gnu.org>
     [not found] ` <20160828130241.9381A220144@vcs.savannah.gnu.org>
2016-08-28 14:46   ` Leo Famulari [this message]
2016-08-28 15:26     ` 02/02: gnu: linux-pam: Add cracklib to inputs David Craven

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=20160828144628.GA10486@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@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.