From: "Richard W.M. Jones" <rjones@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4] block: Add support for Secure Shell (ssh) block device.
Date: Thu, 28 Mar 2013 11:16:58 +0000 [thread overview]
Message-ID: <20130328111657.GA1461@rhmail.home.annexia.org> (raw)
In-Reply-To: <20130328104732.GA15114@stefanha-thinkpad.redhat.com>
On Thu, Mar 28, 2013 at 11:47:32AM +0100, Stefan Hajnoczi wrote:
> ssh(1) prompts the user to accept the hostkey. When QEMU fails like
> this the user needs to run ssh(1) first to populate known_hosts?
Yes - I tested this and qemu will simply fail to open the disk with
the error message about the host key not being found. Currently you
have to manually log in (eg. with ssh), accept the key in ssh, and
then retry the qemu command.
Not that I think this is much of a problem, as long as the error is
clear.
But ... if I wanted to make qemu interactively ask about host keys, or
even accept passwords, how would I do that? Is there a block device
driver that asks for passwords that I can look at?
[The only mention of 'password' is in the iscsi driver, and that seems
to be related to passing passwords in the URL (!?!)]
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
next prev parent reply other threads:[~2013-03-28 11:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 15:57 [Qemu-devel] [PATCH v4] block: Add support for Secure Shell (ssh) block device Richard W.M. Jones
2013-03-27 15:57 ` Richard W.M. Jones
2013-03-28 10:47 ` Stefan Hajnoczi
2013-03-28 11:16 ` Richard W.M. Jones [this message]
2013-03-28 13:29 ` Stefan Hajnoczi
2013-04-03 22:14 ` Richard W.M. Jones
2013-04-08 11:37 ` Stefan Hajnoczi
2013-04-08 13:01 ` Richard W.M. Jones
2013-04-08 13:05 ` Richard W.M. Jones
2013-04-08 14:58 ` Stefan Hajnoczi
2013-04-08 20:21 ` Stefan Hajnoczi
2013-04-09 7:30 ` Richard W.M. Jones
2013-04-09 12:56 ` Stefan Hajnoczi
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=20130328111657.GA1461@rhmail.home.annexia.org \
--to=rjones@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).