[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 2/2] ssh: implement private key authentication
From: |
Markus Armbruster |
Subject: |
Re: [Qemu-devel] [PATCH 2/2] ssh: implement private key authentication |
Date: |
Mon, 29 Jul 2019 12:57:40 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) |
Pino Toscano <address@hidden> writes:
> On Friday, 26 July 2019 16:24:34 CEST Eric Blake wrote:
>> On 7/26/19 9:09 AM, Pino Toscano wrote:
>> > Add a 'private-key' option which represents the path of a private key
>> > to use for authentication, and 'private-key-secret' as the name of an
>> > object with its passphrase.
>> >
>> > Signed-off-by: Pino Toscano <address@hidden>
>>
>> > +++ b/qapi/block-core.json
>> > @@ -3226,6 +3226,11 @@
>> > # @password-secret: ID of a QCryptoSecret object providing a password
>> > # for authentication (since 4.2)
>> > #
>> > +# @private-key: path to the private key (since 4.2)
>> > +#
>> > +# @private-key-secret: ID of a QCryptoSecret object providing the
>> > passphrase
>> > +# for 'private-key' (since 4.2)
>>
>> Is password-secret intended to be mutually-exclusive with
>> private-key/private-key-secret?
>
> My initial thought was to allow users to specify data for all the
> authentication methods possible. Either ways (all of them, or a single
> one) are fine for me.
How does this work at the libssh level? Can you configure multiple
authentication methods, and let negotiation pick the one to be used?
Re: [Qemu-devel] [PATCH 0/2] ssh: add password and privkey auth methods, Richard W.M. Jones, 2019/07/26