[jira] [Closed] (WAGON-262) Support hashed hostnames in the known_hosts file

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov closed WAGON-262.
--------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Support hashed hostnames in the known_hosts file
> ------------------------------------------------
>
>                 Key: WAGON-262
>                 URL: https://issues.apache.org/jira/browse/WAGON-262
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-ssh
>    Affects Versions: 1.0-beta-5
>            Reporter: Wes Wannemacher
>            Priority: Minor
>
> This isn't directly a wagon problem, but it was a problem with the older Jsch. Newer versions of OpenSSH can be told to hash the host names in the known_hosts file... There is some information on the 'net about the file format, example link - http://nms.csail.mit.edu/projects/ssh/install40-other.php. Although I have never had a problem before, I ran a bare-metal install of Ubuntu Jaunty earlier in the week and they have this option turned on by default. Since this was a new machine, all of the entries in known_hosts were hashed. This means, you try to deploy an artifact using wagon-ssh and you will get prompted since authenticity can't be verified. There is info on the Jsch home page that says that later versions (0.4.1?) support hashed known_hosts. I tried updating the pom.xml file to use a newer Jsch, and all of the unit tests pass. There is also a nabble thread here (where I converse with myself) about the issue - 
> http://n2.nabble.com/release%3Aperform-problem-with-ssh-scp-td2734566.html#none
> I'm not going to attach a patch, since all that I have tried to do is update the pom, I haven't done proper testing. 



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