From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Fam Zheng <famz@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v4 00/38] Test and build patches
Date: Fri, 15 Sep 2017 13:09:46 +0100 [thread overview]
Message-ID: <20170915120946.GH13610@redhat.com> (raw)
In-Reply-To: <CAFEAcA9Vf8pvQ07+HNnRHiTv=N7m6LZRKUQdqziDiPX6=uEy_Q@mail.gmail.com>
On Fri, Sep 15, 2017 at 01:03:54PM +0100, Peter Maydell wrote:
> On 15 September 2017 at 12:40, Daniel P. Berrange <berrange@redhat.com> wrote:
> > IIUC, the public part of the key gets exposed to the guest images via
> > cloud-init metadata. During boot the guest read this metadata and add
> > the public key to authorized_keys. The private key is used by the test
> > suite on the host so that it can now login to the guests.
> >
> > So the risk here is that if these guests were exposed to the LAN in any
> > way, someone could grab our private key and login to these guests.
> >
> > What saves us is that the VMs are run with user mode slirp networking
> > so AFAICT, aren't exposed to the LAN.
>
> If I'm reading the right bit of the script we run QEMU with a
> hostfwd specification using 0.0.0.0 as the host part -- doesn't
> that listen on all interfaces including the LAN ones?
Actually yes, you are right, my bad.
That needs to be fixed to use 127.0.0.1 for sure.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-09-15 12:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 9:02 [Qemu-devel] [PULL v4 00/38] Test and build patches Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 10/38] scripts: Add archive-source.sh Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 11/38] tests: Add a test key pair Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 12/38] tests: Add vm test lib Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 13/38] tests: Add ubuntu.i386 image Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 14/38] tests: Add FreeBSD image Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 15/38] tests: Add NetBSD image Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 16/38] tests: Add OpenBSD image Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 17/38] Makefile: Add rules to run vm tests Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 18/38] MAINTAINERS: Add tests/vm entry Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 19/38] tests: Add README for vm tests Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 20/38] docker: Use archive-source.py Fam Zheng
2017-09-15 10:55 ` [Qemu-devel] [PULL v4 00/38] Test and build patches Peter Maydell
2017-09-15 11:36 ` Fam Zheng
2017-09-15 11:40 ` Daniel P. Berrange
2017-09-15 12:03 ` Peter Maydell
2017-09-15 12:09 ` Daniel P. Berrange [this message]
2017-09-15 12:21 ` Fam Zheng
2017-09-15 12:31 ` Daniel P. Berrange
2017-09-15 12:51 ` Fam Zheng
2017-09-15 14:47 ` Philippe Mathieu-Daudé
2017-09-15 20:52 ` Fam Zheng
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=20170915120946.GH13610@redhat.com \
--to=berrange@redhat.com \
--cc=famz@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).