From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, Pino Toscano <ptoscano@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, rjones@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v4] ssh: switch from libssh2 to libssh
Date: Tue, 13 Feb 2018 12:59:18 -0600 [thread overview]
Message-ID: <c3b37bdc-8694-10dc-6b85-eecd6d0147f1@redhat.com> (raw)
In-Reply-To: <19874fff-b615-593f-c0a4-16954fa2732c@redhat.com>
On 02/13/2018 12:49 PM, Max Reitz wrote:
> On 2018-01-18 17:44, 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
>>
>> @@ -628,6 +570,8 @@ static int connect_to_ssh(BDRVSSHState *s, QDict *options,
>> Error *local_err = NULL;
>> const char *user, *path, *host_key_check;
>> long port = 0;
>> + unsigned long portU = 0;
>
> I was about to say: How about making port an unsigned long and swapping
> the qemu_strtol() for a qemu_strtoul()?
>
> But I think you'd rather want an unsigned int instead (and that won't
> work with qemu_strtoul()).
Dan has a pending patch that adds qemu_strtoi() and qemu_strtoui(), when
we want to deal with parsing to ints.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-02-13 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 16:44 [Qemu-devel] [PATCH v4] ssh: switch from libssh2 to libssh Pino Toscano
2018-02-13 18:49 ` Max Reitz
2018-02-13 18:59 ` Eric Blake [this message]
2018-06-25 17:41 ` 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=c3b37bdc-8694-10dc-6b85-eecd6d0147f1@redhat.com \
--to=eblake@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).