From: Danny Milosavljevic <dannym@scratchpost.org>
To: Leo Famulari <leo@famulari.name>
Cc: 34446@debbugs.gnu.org
Subject: [bug#34446] [PATCH 1/2] gnu: runc: Update to 1.0.0-rc6 [fixes CVE-2019-5736].
Date: Tue, 12 Feb 2019 01:45:01 +0100 [thread overview]
Message-ID: <20190212014501.31dcb6a8@scratchpost.org> (raw)
In-Reply-To: <61ed83d852124caae74fd8cd53a9c375ee3ac80d.1549931256.git.leo@famulari.name>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Mon, 11 Feb 2019 19:27:35 -0500
Leo Famulari <leo@famulari.name> wrote:
> (define-public runc
> (package
> (name "runc")
> - (version "1.0.0-rc5")
> + (version "1.0.0-rc6")
> (source (origin
> (method url-fetch)
> (uri (string-append
> "https://github.com/opencontainers/runc/releases/"
> "download/v" version "/runc.tar.xz"))
> + (file-name (string-append name "-" version ".tar.xz"))
> + (patches (search-patches "runc-CVE-2019-5736.patch"))
> (sha256
> (base32
> - "081avdzwnqpk368wbaihlzsypaxpj42d7699h7jgp0fks14x4103"))))
> + "1c7832dq70slkjh8qp2civ1wxhhdd2hrx84pq7db1mmqc9fdr3cc"))))
> (build-system go-build-system)
> (arguments
> '(#:import-path "github.com/opencontainers/runc"
Docker still contains some vendored dependencies, among those github.com/opencontainers/runc,
in directory "vendor", and so does containerd. It might make sense to also remove them now.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-02-12 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 23:37 [bug#34446] Runc container escape patches CVE-2019-5736 Leo Famulari
2019-02-12 0:10 ` Danny Milosavljevic
2019-02-12 0:13 ` Danny Milosavljevic
2019-02-12 17:56 ` bug#34446: " Leo Famulari
2019-02-12 0:27 ` [bug#34446] [PATCH 1/2] gnu: runc: Update to 1.0.0-rc6 [fixes CVE-2019-5736] Leo Famulari
2019-02-12 0:27 ` [bug#34446] [PATCH 2/2] gnu: Docker: Update to 18.09.2 Leo Famulari
2019-02-12 0:45 ` Danny Milosavljevic [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
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=20190212014501.31dcb6a8@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=34446@debbugs.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 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).