From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH web 0/2] Secure the download links and more
Date: Mon, 4 Sep 2017 09:36:39 -0500 [thread overview]
Message-ID: <7c228b52-f5bf-929b-9acf-07e705ec0198@redhat.com> (raw)
In-Reply-To: <20170904142608.4897-1-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
On 09/04/2017 09:26 AM, Daniel P. Berrange wrote:
> which gives the $BAD guys plenty chance to compromise your
> download. Fix this to link to https:// sites exclusively
> and use the preferred qemu.org domani too. All links are
> fixed to use https, not merely download site links.
We should also patch include/qemu-common.h, which lists http:// rather
than https:// for the --help output (because at the time the patch was
first written, we did not have https:// fully working yet)
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-09-04 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 14:26 [Qemu-devel] [PATCH web 0/2] Secure the download links and more Daniel P. Berrange
2017-09-04 14:26 ` [Qemu-devel] [PATCH web 1/2] Update all links to prefer qemu.org over qemu-project.org Daniel P. Berrange
2017-09-04 14:26 ` [Qemu-devel] [PATCH web 2/2] Use https links whereever possible Daniel P. Berrange
2017-09-04 14:36 ` Eric Blake [this message]
2017-09-11 15:37 ` [Qemu-devel] [PATCH web 0/2] Secure the download links and more Paolo Bonzini
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=7c228b52-f5bf-929b-9acf-07e705ec0198@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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.
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 NNTP newsgroup(s).