all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 29232@debbugs.gnu.org
Subject: [bug#29232] [PATCH] gnu: qemu: Fix CVE-2017-{15038,15268,15289}.
Date: Thu, 09 Nov 2017 23:51:48 +0100	[thread overview]
Message-ID: <87a7zvhxq3.fsf@gnu.org> (raw)
In-Reply-To: <98773909c59c0ca327584f7d20ec35eedff74c79.1510251328.git.leo@famulari.name> (Leo Famulari's message of "Thu, 9 Nov 2017 13:15:53 -0500")

Hello,

Leo Famulari <leo@famulari.name> skribis:

> What do you think of fetching the patches like this, instead of copying
> them into the Guix source tree?

I think it’s OK.  If the Gitweb instance disappears, or if it changes
somehow, hopefully the patch itself will still have the same hash, so we
can always change to different URL or a local file.

> * gnu/packages/virtualization.scm (qemu-patch): Use HTTPS.
> (qemu)[source]: Use qemu-patch.

[…]

> +            (qemu-patch "7bd92756303f2158a68d5166264dc30139b813b6"
> +                        "qemu-CVE-2017-15038.patch"
> +                        (base32
> +                         "0wpgf8ivjdbaihf2l7720h1fydh7kdl36wj2nchjd9irfkhw399q"))
> +            (qemu-patch "a7b20a8efa28e5f22c26c06cd06c2f12bc863493"
> +                        "qemu-CVE-2017-15268.patch"
> +                        (base32
> +                         "1adhwj91pmgbmdvyrkvslbfsyz7l00xdrr6vzps6s58q5idvdp79"))
> +            (qemu-patch "eb38e1bc3740725ca29a535351de94107ec58d51"
> +                        "qemu-CVE-2017-15289.patch"
> +                        (base32
> +                         "1zshrlzbwgwrsnimbq8kqr7injd65ncsr8a4lrmgyfv185ma4z8d"))))

I trust these commits correspond to these CVEs.

Thanks,
Ludo’.

  reply	other threads:[~2017-11-09 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 18:15 [bug#29232] [PATCH] gnu: qemu: Fix CVE-2017-{15038,15268,15289} Leo Famulari
2017-11-09 22:51 ` Ludovic Courtès [this message]
2017-11-10 17:17   ` bug#29232: " Leo Famulari
2017-11-10 21:42     ` [bug#29232] " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7zvhxq3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=29232@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 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.