From: Leo Famulari <leo@famulari.name>
To: 29000@debbugs.gnu.org
Subject: [bug#29000] [PATCH] gnu: glibc: Ungraft fix for CVE-2017-15670, CVE-2017-15671.
Date: Wed, 25 Oct 2017 14:56:07 -0400 [thread overview]
Message-ID: <674f248fb17fb1ee274a7fb0bc91ff0287f1f923.1508957767.git.leo@famulari.name> (raw)
* gnu/packages/base.scm (glibc)[replacement]: Remove field.
[source]: Add 'glibc-CVE-2017-15670-15671.patch'.
(glibc/fixed): Remove variable.
---
gnu/packages/base.scm | 11 +----------
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/gnu/packages/base.scm b/gnu/packages/base.scm
index 9cb628d8d..e1826f57b 100644
--- a/gnu/packages/base.scm
+++ b/gnu/packages/base.scm
@@ -528,7 +528,6 @@ store.")
(package
(name "glibc")
(version "2.25")
- (replacement glibc/fixed)
(source (origin
(method url-fetch)
(uri (string-append "mirror://gnu/glibc/glibc-"
@@ -549,6 +548,7 @@ store.")
"glibc-o-largefile.patch"
"glibc-memchr-overflow-i686.patch"
"glibc-vectorized-strcspn-guards.patch"
+ "glibc-CVE-2017-15670-15671.patch"
"glibc-CVE-2017-1000366-pt1.patch"
"glibc-CVE-2017-1000366-pt2.patch"
"glibc-CVE-2017-1000366-pt3.patch"))))
@@ -787,15 +787,6 @@ GLIBC/HURD for a Hurd host"
(define-syntax glibc
(identifier-syntax (glibc-for-target)))
-(define glibc/fixed
- (package
- (inherit glibc)
- (source (origin
- (inherit (package-source glibc))
- (patches (append
- (origin-patches (package-source glibc))
- (search-patches "glibc-CVE-2017-15670-15671.patch")))))))
-
;; Below are old libc versions, which we use mostly to build locale data in
;; the old format (which the new libc cannot cope with.)
--
2.14.3
next reply other threads:[~2017-10-25 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 18:56 Leo Famulari [this message]
2017-10-25 19:04 ` [bug#29000] Ungrafting glibc? Leo Famulari
2017-10-26 22:32 ` Ludovic Courtès
2017-10-26 22:33 ` [bug#29000] [PATCH] gnu: glibc: Ungraft fix for CVE-2017-15670, CVE-2017-15671 Ludovic Courtès
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=674f248fb17fb1ee274a7fb0bc91ff0287f1f923.1508957767.git.leo@famulari.name \
--to=leo@famulari.name \
--cc=29000@debbugs.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 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).