On Tue, Apr 28, 2009 at 2:26 PM, Wes Wannemacher <[email protected]> wrote:
> That worked! Thanks!
>
> -Wes
>

No problem...

Upon looking into this a little bit further, it seems like the problem
is the new hashed known_hosts file. The latest release of ubuntu turns
the hashing of known_hosts on, where by default OpenSSH would normally
have it turned off. So, your known_hosts entry would normally look
like this -

people.apache.org ssh-dss AAAAB3...

In the new hashed format it looks like this -

|1|wiKjIB5... = ssh-dss AAAAB3...

The goal on the SSH side of things appears to be that if someone has
compromised your account, the known_hosts file is a decent place to
start looking for further hosts to joyride along. Having the option to
hash the hostname makes it more difficult for a joyrider to continue
on to more hosts. This seems like a good thing to have, so Jsch (which
Wagon uses for ssh/scp) should support it as well. I can try to follow
up with them. In your case, Wes, you probably recently installed the
new version of Ubuntu from scratch. So, you had an empty known_hosts
file. The stock install of Ubuntu (Jaunty) turns the configuration
parameter on to hash the known_hosts file and even though everything
worked on the command line, Jsch couldn't read the file since the
entries were hashed.

-Wes



-- 
Wes Wannemacher
Author - Struts 2 In Practice
Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more
http://www.manning.com/wannemacher

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to