From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel Berrange" <berrange@redhat.com>,
eblake@redhat.com, "Peter Maydell" <peter.maydell@linaro.org>,
"Jeff Cody" <jcody@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
cohuck@redhat.com, "Paolo Bonzini" <pbonzini@redhat.com>,
"Fam Zheng" <famz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH v4 5/8] git: use HTTPS git URLs for repo.or.cz
Date: Thu, 8 Nov 2018 11:15:28 +0000 [thread overview]
Message-ID: <20181108111531.30671-6-stefanha@redhat.com> (raw)
In-Reply-To: <20181108111531.30671-1-stefanha@redhat.com>
When you clone the repository without previous commit history, 'git://'
doesn't protect from man-in-the-middle attacks. HTTPS is more secure
since the client verifies the server certificate.
Suggested-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
MAINTAINERS | 14 +++++++-------
pc-bios/README | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 391c8460b8..5fb757edd6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1464,7 +1464,7 @@ F: tests/qemu-iotests/
F: util/qemu-progress.c
F: qobject/block-qdict.c
F: tests/check-block-qdict.c
-T: git git://repo.or.cz/qemu/kevin.git block
+T: git https://repo.or.cz/qemu/kevin.git block
Block I/O path
M: Stefan Hajnoczi <stefanha@redhat.com>
@@ -1511,7 +1511,7 @@ F: blockdev.c
F: block/qapi.c
F: qapi/block*.json
F: qapi/transaction.json
-T: git git://repo.or.cz/qemu/armbru.git block-next
+T: git https://repo.or.cz/qemu/armbru.git block-next
Dirty Bitmaps
M: Fam Zheng <famz@redhat.com>
@@ -1706,14 +1706,14 @@ F: tests/test-visitor-serialization.c
F: scripts/qapi-gen.py
F: scripts/qapi/*
F: docs/devel/qapi*
-T: git git://repo.or.cz/qemu/armbru.git qapi-next
+T: git https://repo.or.cz/qemu/armbru.git qapi-next
QAPI Schema
M: Eric Blake <eblake@redhat.com>
M: Markus Armbruster <armbru@redhat.com>
S: Supported
F: qapi/*.json
-T: git git://repo.or.cz/qemu/armbru.git qapi-next
+T: git https://repo.or.cz/qemu/armbru.git qapi-next
QObject
M: Markus Armbruster <armbru@redhat.com>
@@ -1727,7 +1727,7 @@ F: tests/check-qnum.c
F: tests/check-qjson.c
F: tests/check-qlist.c
F: tests/check-qstring.c
-T: git git://repo.or.cz/qemu/armbru.git qapi-next
+T: git https://repo.or.cz/qemu/armbru.git qapi-next
QEMU Guest Agent
M: Michael Roth <mdroth@linux.vnet.ibm.com>
@@ -1759,7 +1759,7 @@ F: docs/devel/*qmp-*
F: scripts/qmp/
F: tests/qmp-test.c
F: tests/qmp-cmd-test.c
-T: git git://repo.or.cz/qemu/armbru.git qapi-next
+T: git https://repo.or.cz/qemu/armbru.git qapi-next
qtest
M: Paolo Bonzini <pbonzini@redhat.com>
@@ -2073,7 +2073,7 @@ F: include/block/nbd*
F: qemu-nbd.*
F: blockdev-nbd.c
F: docs/interop/nbd.txt
-T: git git://repo.or.cz/qemu/ericb.git nbd
+T: git https://repo.or.cz/qemu/ericb.git nbd
NFS
M: Jeff Cody <jcody@redhat.com>
diff --git a/pc-bios/README b/pc-bios/README
index b572e9eb00..8f98c07a74 100644
--- a/pc-bios/README
+++ b/pc-bios/README
@@ -5,7 +5,7 @@
project (http://www.nongnu.org/vgabios/).
- The PowerPC Open Hack'Ware Open Firmware Compatible BIOS is
- available at http://repo.or.cz/w/openhackware.git.
+ available at https://repo.or.cz/openhackware.git.
- OpenBIOS (http://www.openbios.org/) is a free (GPL v2) portable
firmware implementation. The goal is to implement a 100% IEEE
--
2.19.1
next prev parent reply other threads:[~2018-11-08 11:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 11:15 [Qemu-devel] [PATCH v4 0/8] Use 'https://' instead of 'git://' Stefan Hajnoczi
2018-11-08 11:15 ` [Qemu-devel] [PATCH v4 1/8] README: use " Stefan Hajnoczi
2018-11-08 11:52 ` Cornelia Huck
2018-11-08 11:15 ` [Qemu-devel] [PATCH v4 2/8] get_maintainer: " Stefan Hajnoczi
2018-11-08 11:53 ` Cornelia Huck
2018-11-08 11:15 ` [Qemu-devel] [PATCH v4 3/8] MAINTAINERS: use 'https://' instead of 'git://' for GitHub Stefan Hajnoczi
2018-11-08 11:56 ` Cornelia Huck
2018-11-08 11:15 ` [Qemu-devel] [PATCH v4 4/8] gitmodules: use 'https://' instead of 'git://' Stefan Hajnoczi
2018-11-08 11:58 ` Cornelia Huck
2018-11-08 11:15 ` Stefan Hajnoczi [this message]
2018-11-08 11:59 ` [Qemu-devel] [PATCH v4 5/8] git: use HTTPS git URLs for repo.or.cz Cornelia Huck
2018-11-08 11:15 ` [Qemu-devel] [PATCH v4 6/8] pc-testdev: use HTTPS git URL Stefan Hajnoczi
2018-11-08 12:01 ` Cornelia Huck
2018-11-08 11:15 ` [Qemu-devel] [PATCH v4 7/8] target-alpha: use HTTPS git URL for palcode Stefan Hajnoczi
2018-11-08 12:02 ` Cornelia Huck
2018-11-08 11:15 ` [Qemu-devel] [PATCH v4 8/8] docker: use HTTPS git URL for virglrenderer Stefan Hajnoczi
2018-11-08 12:04 ` Cornelia Huck
2018-11-09 18:16 ` [Qemu-devel] [PATCH v4 0/8] Use 'https://' instead of 'git://' Michael S. Tsirkin
2018-11-12 13:48 ` Peter Maydell
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=20181108111531.30671-6-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=mst@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).