all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: 27429@debbugs.gnu.org
Subject: bug#27429: Stack clash (CVE-2017-1000366 etc)
Date: Fri, 23 Jun 2017 14:54:48 -0400	[thread overview]
Message-ID: <20170623185448.GA14284@jasmine.lan> (raw)
In-Reply-To: <87mv8yh7pi.fsf@netris.org>

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

On Fri, Jun 23, 2017 at 02:36:41PM -0400, Mark H Weaver wrote:
> Most packages are linked with 'glibc-final' in (gnu packages
> commencement), and we should expect them to now be linked with *its*
> replacement.  Try this to find the expected glibc-final replacement:
> 
>   ./pre-inst-env guix build -e '((@@ (guix packages) package-replacement) (@@ (gnu packages commencement) glibc-final))'

Thank you for the clarification. Indeed, with Efraim's latest patch,
packages seem to be referring to the replacement for glibc-final.

So, do we think this patch is ready to apply? AFAIK, nobody has yet
tried upgrading a GuixSD system with this patch. I won't have access to
my bare-metal GuixSD system for the next few days.

> > By the way, Qualys will probably begin publishing their exploits on
> > Tuesday [0]:
> 
> Thanks for the heads-up, and more generally to your prolific
> contributions to security in Guix!

Thank you for your advice and guidance, and to Efraim for taking the
lead on fixing this bug!

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

  reply	other threads:[~2017-06-23 18:55 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 22:25 bug#27429: Stack clash (CVE-2017-1000366 etc) Leo Famulari
2017-06-19 23:05 ` Leo Famulari
2017-06-20  0:42   ` Leo Famulari
2017-06-20  0:49 ` Leo Famulari
2017-06-20  7:18   ` Efraim Flashner
2017-06-20 13:16     ` Leo Famulari
2017-06-20 21:44     ` Mark H Weaver
2017-06-21  8:41       ` Efraim Flashner
2017-06-21  9:50         ` Efraim Flashner
2017-06-21 23:52           ` Leo Famulari
2017-06-22  0:03             ` Leo Famulari
2017-06-22  6:44               ` Mark H Weaver
2017-06-22 16:17                 ` Leo Famulari
2017-06-22 18:34                   ` Leo Famulari
2017-06-22 19:25                     ` Leo Famulari
2017-06-29 10:58                 ` Ludovic Courtès
2017-06-29 15:49                   ` Mark H Weaver
2017-06-29 20:06                     ` Ludovic Courtès
2017-06-29 21:03                       ` bug#27429: core-updates and shishi [was Re: bug#27429: Stack clash (CVE-2017-1000366 etc)] Leo Famulari
2017-06-29 22:27                         ` Ludovic Courtès
2017-06-30  6:47                           ` Leo Famulari
2017-06-30 12:59                             ` Ludovic Courtès
2017-06-23 17:20           ` bug#27429: Stack clash (CVE-2017-1000366 etc) Leo Famulari
2017-06-23 18:36             ` Mark H Weaver
2017-06-23 18:54               ` Leo Famulari [this message]
2017-06-23 20:03                 ` Mark H Weaver
2017-06-24  7:11                   ` Mark H Weaver
2017-06-26  8:41                     ` Ludovic Courtès
2017-06-26 11:19                       ` Mark H Weaver
2017-06-27 13:57                         ` Ludovic Courtès
2017-06-28 21:55             ` Leo Famulari
2017-06-20  3:31 ` Mark H Weaver
2017-06-25  9:38 ` bug#27429: Stack clash (CVE-2017-1000366 etc); -fstack-check Danny Milosavljevic
2017-06-25 10:41   ` Marius Bakke
2017-06-25 13:19     ` Leo Famulari
2017-07-20 15:54 ` bug#27429: Stack clash (CVE-2017-1000366 etc) Ludovic Courtès
2017-07-20 19:13   ` 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=20170623185448.GA14284@jasmine.lan \
    --to=leo@famulari.name \
    --cc=27429@debbugs.gnu.org \
    --cc=mhw@netris.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.