[jira] [Resolved] (SSHD-865) Use lazy-loading for keys specified in the HostConfigEntry

["Goldstein Lyor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SSHD-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Goldstein Lyor resolved SSHD-865.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.1

> Use lazy-loading for keys specified in the HostConfigEntry
> ----------------------------------------------------------
>
>                 Key: SSHD-865
>                 URL: https://issues.apache.org/jira/browse/SSHD-865
>             Project: MINA SSHD
>          Issue Type: Improvement
>    Affects Versions: 2.1.1
>            Reporter: Goldstein Lyor
>            Assignee: Goldstein Lyor
>            Priority: Major
>             Fix For: 2.1.1
>
>
> Following SSHD-860 key loading occurs lazily - thus encrypted keys password is not requested until the key is actually needed. The exception to this rule are keys specified as part of a {{HostConfigEntry}} specified in an [ssh_config file|http://www.gsp.com/cgi-bin/man.cgi?topic=ssh_config].
> h5. Implementation details
> * Need to change {{SshClient#loadClientIdentities}} to return a {{KeyPairProvider}} that is propagated all the way to {{SshClient#onConnectOperationComplete}}.
> * The code in {{SshClient#onConnectOperationComplete}} should check after {{setupDefaultSessionIdentities}} if there is a non-empty {{KeyPairProvider}} propagated and *aggregate* it with any already set such provider on the session



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)