From: "Richard W.M. Jones" <rjones@redhat.com>
To: Pino Toscano <ptoscano@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, jcody@redhat.com,
kwolf@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] ssh: switch from libssh2 to libssh
Date: Fri, 21 Oct 2016 16:39:17 +0100 [thread overview]
Message-ID: <20161021153916.GL11243@redhat.com> (raw)
In-Reply-To: <2365877.PbZSkETgfu@thyrus.usersys.redhat.com>
On Fri, Oct 21, 2016 at 05:30:39PM +0200, Pino Toscano wrote:
> On Friday, 21 October 2016 13:02:21 CEST Richard W.M. Jones wrote:
> > On Fri, Oct 21, 2016 at 01:16:11PM +0200, Pino Toscano wrote:
> > > Rewrite the implementation of the ssh block driver to use libssh instead
> > > of libssh2. The libssh library has various advantages over libssh2:
> > > - easier API for authentication (for example for using ssh-agent)
> > > - easier API for known_hosts handling
> > > - supports newer types of keys in known_hosts
> > >
> > > Kerberos authentication can be enabled once the libssh bug for it [1] is
> > > fixed.
> > >
> > > The development version of libssh (i.e. the future 0.8.x) supports
> > > fsync, so reuse the build time check for this.
> > >
> > > [1] https://red.libssh.org/issues/242
> > >
> > > Signed-off-by: Pino Toscano <ptoscano@redhat.com>
> > > ---
> > >
> > > Changes from v1:
> > > - fixed jumbo packets writing
> > > - fixed missing 'err' assignment
> > > - fixed commit message
> >
> > This version works, but I also switched from using a remote server to
> > using this over localhost.
>
> Could you please give it a try with the remote server case as well?
I tried it and it failed with the remote server. Same kinds of errors
as last time.
> > It seems as if the timeout might be a bit short. Could that be made
> > controllable? Or increased to match whatever libssh2 was using?
>
> Which timeout are you referring to?
Not any particular thing, I just observed that with the remote server
the errors happen quite quickly, and so perhaps there is a shorter
timeout. (libssh2 apparently defaults to unlimited waiting, although
I'm sure there are other timeouts in ssh or TCP which kick in).)
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
prev parent reply other threads:[~2016-10-21 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 11:16 [Qemu-devel] [PATCH v2] ssh: switch from libssh2 to libssh Pino Toscano
2016-10-21 11:25 ` Daniel P. Berrange
2016-10-21 15:28 ` Pino Toscano
2016-10-21 12:02 ` Richard W.M. Jones
2016-10-21 15:30 ` Pino Toscano
2016-10-21 15:39 ` Richard W.M. Jones [this message]
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=20161021153916.GL11243@redhat.com \
--to=rjones@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=ptoscano@redhat.com \
--cc=qemu-block@nongnu.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).