[ 
http://jira.codehaus.org/browse/WAGON-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194667#action_194667
 ] 

Jozef Kotlár commented on WAGON-262:
------------------------------------

Sorry, my last comment was not correct.
- The bug mentioned here *is* solved.
- The improvement was not realized yet, the possibility to save entries in 
hashed form requires some codings.

I would suggest to guess right option from existing entries. If any (last?) 
entry in HostKeys file starts with {{|1|}}, then _HashKnowHosts_ should be set 
to _yes_.

> Support hashed hostnames in the known_hosts file
> ------------------------------------------------
>
>                 Key: WAGON-262
>                 URL: http://jira.codehaus.org/browse/WAGON-262
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-ssh
>    Affects Versions: 1.0-beta-5
>            Reporter: Wes Wannemacher
>            Priority: Minor
>             Fix For: 1.0
>
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to