[ 
https://issues.apache.org/jira/browse/WAGON-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691121#comment-15691121
 ] 

ASF GitHub Bot commented on WAGON-467:
--------------------------------------

GitHub user nfalco79 opened a pull request:

    https://github.com/apache/maven-wagon/pull/29

    [WAGON-467] Allow customisation of some SSH options

    This commit add StrictHostKeyChecking and PreferredAuthentications custom 
fields that together allow you to perform, the command scp enough to remove any 
user interaction (username, password and add host key to know_hosts file).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nfalco79/maven-wagon feature/WAGON-467

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/maven-wagon/pull/29.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #29
    
----
commit b5f312c5dca59b745662fd81a9e24401d1322ebc
Author: Nikolas Falco <nikolas.fa...@finantix.com>
Date:   2016-11-23T19:24:41Z

    [WAGON-467] Allow customisation of some SSH options
    
    This commit add StrictHostKeyChecking and PreferredAuthentications custom 
fields that together allow you to perform, the command scp enough to remove any 
user interaction (username, password and add host key to know_hosts file).

----


> Enforce SSH command to be interactive
> -------------------------------------
>
>                 Key: WAGON-467
>                 URL: https://issues.apache.org/jira/browse/WAGON-467
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-ssh
>    Affects Versions: 2.10
>         Environment: Maven 3.3
> Jenkins
>            Reporter: Nikolas Falco
>
> Hi,
>    I'm looking a way to deploy the maven site using scp protocol.
> I found some issues:
> * when I create a Jenkins node the maven process stucks during site:deploy 
> goal because it prompts to me if I want add the destination host key to 
> know_hosts file.
> * also with correct credential in settings.xml it prompts to me for Kerberos 
> username [$USER] and password.
> After a lot of google search the SSH options command to setup should be:
> * StrictHostKeyChecking [ask, no, yes]
> * PreferredAuthentications a mix of [gssapi-with-mic, publickey, password, 
> keyboard-interactive]
> Configure those option into them into .ssh/config file it's hard to manage in 
> many in case of many machine
> Actually there is not way to change those settings in the wagon instance 
> For StrictHostKeyChecking could be used the settings.xml 
> {code:xml}
> <servers>
>       <server>
>               <id>docserver</id>
>               <username>xxx</username>
>               <password>password</password>
>               <configuration>
>                       <knownHostsProvider>
>                               <hostKeyChecking>no</hostKeyChecking>
>                       </knownHostsProvider>
>               </configuration>
>       </server>
> </servers>
> {code}
> but it fails because KnownHostsProvider it's an interface and if I specify 
> the implementation of knownHostsProvider
> {code:xml}
> <knownHostsProvider 
> implementation="org.apache.maven.wagon.providers.ssh.knownhost.FileKnownHostsProvider">
> {code}
> fails because ClassNotFound on IOUtil in super constructor method.
> Instead for PreferredAuthentications it's an plain string into the code so no 
> way to change it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to