From: "Richard W.M. Jones" <rjones@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] block: Add support for Secure Shell (ssh) block device.
Date: Thu, 21 Mar 2013 20:31:37 +0000 [thread overview]
Message-ID: <20130321203137.GH1504@rhmail.home.annexia.org> (raw)
In-Reply-To: <CAJSP0QXVf1-TFqm_xKbnxqA=F0bMah0+_zfj0KECtKwb3r4LyQ@mail.gmail.com>
On Thu, Mar 21, 2013 at 08:35:29PM +0100, Stefan Hajnoczi wrote:
> On Thu, Mar 21, 2013 at 2:38 PM, Richard W.M. Jones <rjones@redhat.com> wrote:
> > From: "Richard W.M. Jones" <rjones@redhat.com>
> >
> > qemu-system-x86_64 -drive file=ssh://hostname/some/image
> >
> > QEMU will ssh into 'hostname' and open '/some/image' which is made
> > available as a standard block device.
> >
> > You can specify a username (ssh://user@host/...) and/or a port number
> > (ssh://host:port/...).
> >
> > Current limitations:
> >
> > - Authentication must be done without passwords or passphrases, using
> > ssh-agent. Other authentication methods are not supported. (*)
> >
> > - Does not check host key. (*)
> >
> > - New remote files cannot be created. (*)
> >
> > - Uses coroutine read/write, instead of true AIO. (libssh2 supports
> > non-blocking access, so this could be fixed with some effort).
> >
> > - Blocks during connection and authentication.
> >
> > (*) = potentially easy fix
> >
> > This is implemented using libssh2 on the client side. The server just
> > requires a regular ssh daemon with sftp-server support. Most ssh
> > daemons on Unix/Linux systems will work out of the box.
> > ---
> > block/Makefile.objs | 1 +
> > block/ssh.c | 514 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> > configure | 47 +++++
> > qemu-doc.texi | 28 +++
> > 4 files changed, 590 insertions(+)
> > create mode 100644 block/ssh.c
>
> Just noticed that libcurl supports sftp.
>
> Did you try enabling sftp support in block/curl.c? I think you just
> need to add CURLPROTO_SFTP to #define PROTOCOLS.
Interestingly curl's sftp support is implemented using libssh2. I'll
take a look at how easy this will be.
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-21 20:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 13:38 [Qemu-devel] [PATCH] Add support for Secure Shell (ssh) block device Richard W.M. Jones
2013-03-21 13:38 ` [Qemu-devel] [PATCH] block: " Richard W.M. Jones
2013-03-21 15:26 ` Stefan Hajnoczi
2013-03-21 15:39 ` Richard W.M. Jones
2013-03-21 19:29 ` Stefan Hajnoczi
2013-03-21 19:35 ` Stefan Hajnoczi
2013-03-21 20:31 ` Richard W.M. Jones [this message]
2013-03-22 13:04 ` [Qemu-devel] [PATCH] block/curl: Add support for Secure Shell (ssh/sftp) " Richard W.M. Jones
2013-03-22 13:41 ` Stefan Hajnoczi
2013-03-25 12:32 ` Richard W.M. Jones
2013-03-25 13:12 ` Stefan Hajnoczi
2013-03-25 14:36 ` [Qemu-devel] [PATCH] block: Add support for Secure Shell (ssh) " Kevin Wolf
2013-03-25 15:11 ` Richard W.M. Jones
2013-03-26 9:37 ` 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=20130321203137.GH1504@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).