You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2013/03/01 00:35:12 UTC

[jira] [Resolved] (IVY-1408) Ssh Resolver doesn't work with recent Jsch versions

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

Maarten Coene resolved IVY-1408.
--------------------------------

    Resolution: Fixed
      Assignee: Maarten Coene

Applied your patch in SVN trunk (but I didn't upgrade the jsch library though).
Thanks for the contribution!
                
> Ssh Resolver doesn't work with recent Jsch versions
> ---------------------------------------------------
>
>                 Key: IVY-1408
>                 URL: https://issues.apache.org/jira/browse/IVY-1408
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.3.0
>            Reporter: Mykhailo Delegan
>            Assignee: Maarten Coene
>            Priority: Minor
>         Attachments: IVY-1408.patch
>
>
> There is a known "issue" with the Jsch library and Java 1.7, in that it prompts for a kerberos username and password (which are then ignored if other credentials have already been supplied). This doesn't stop the Ant ssh tasks from working, but it does stop them from being completely automated (e.g. scripts invoked by a CI server like Jenkins)
> The workaround is either of two: 
> # Move back to Java 1.6
> # Use old enough Jsch version (0.1.31 seems to be ok).
> Jsch author, Atsuhiko Yamanaka, [suggests|http://sourceforge.net/mailarchive/message.php?msg_id=29359265] to configure Jsch Session as following to avoid the issue: 
> {code:java}
> session.setConfig("PreferredAuthentications", "publickey,keyboard-interactive,password");
> {code}
> The very same issue was [filed|https://issues.apache.org/bugzilla/show_bug.cgi?id=53437] and [fixed|http://svn.apache.org/viewvc?rev=1429602&view=rev] in Ant. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira