From: Andreas Schneider <asn@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: John Snow <jsnow@redhat.com>, Pino Toscano <ptoscano@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org, kwolf@redhat.com,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v3] ssh: switch from libssh2 to libssh
Date: Tue, 19 Dec 2017 00:19:36 +0100 [thread overview]
Message-ID: <2123560.m7mx4i3f7h@magrathea.fritz.box> (raw)
In-Reply-To: <20171218213140.GT2787@redhat.com>
On Monday, 18 December 2017 22:31:40 CET Richard W.M. Jones wrote:
> On Mon, Dec 18, 2017 at 01:43:39PM -0500, John Snow wrote:
> > Hi, friendly ping:
> >
> > It's been over a month with no replies, so it's safe to say this has
> > gotten lost in the 2.11 release shuffle.
> >
> > Recommend you re-send it for the 2.12 window.
>
> Actually there is an interop problem with the ssh daemon on ESXi which
> I've not resolved yet. Unfortunately there was no response to my
> upstream message about collecting debugging info:
>
> https://www.libssh.org/archive/libssh/2017-12/0000000.html
>
> Since liberating guests from VMware is a prime reason to have an ssh
> driver in qemu, I'd really like this to be fixed first ...
I responded to you mail, didn't you get it?
It looks like that their sftp server sent an invalid message.
Can you create libssh log and maybe also a pcap file?
https://git.libssh.org/projects/libssh.git/tree/examples/ssh_client.c#n308
See set_pcap() this will create a pcap file after decryption.
Andreas
next prev parent reply other threads:[~2017-12-18 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 16:26 [Qemu-devel] [PATCH v3] ssh: switch from libssh2 to libssh Pino Toscano
2017-11-15 17:10 ` Richard W.M. Jones
2017-12-18 18:43 ` [Qemu-devel] [Qemu-block] " John Snow
2017-12-18 21:31 ` Richard W.M. Jones
2017-12-18 23:19 ` Andreas Schneider [this message]
2017-12-19 15:24 ` Jeff Cody
2017-12-19 16:15 ` Richard W.M. Jones
2017-12-18 19:55 ` [Qemu-devel] " Jeff Cody
2018-01-18 16:26 ` Pino Toscano
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=2123560.m7mx4i3f7h@magrathea.fritz.box \
--to=asn@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=ptoscano@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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).