Re: [JSch-users] Establish authenticity of remote host
Status: Alpha
Brought to you by:
ymnk
From: Quiring, S. <Sam...@wi...> - 2010-11-22 15:05:19
|
Hi Atsuhito, Yes, supplying a known hosts file is the answer. Thank you for your reply. I received email from Chia-ling Lee to that effect earlier and implemented the solution. The code you pointed me to has no documentation and hashes the host names. Had I received your reply first, I would not have known if hashing the host names was required (it is not). I am curious, why would you hash the host names? What is the advantage? It would be nice if the FAQ mentioned each of these facts: 1) Using a known hosts file will get rid of repeated popups "The authenticity of host...". JSch will record each approved host in the known hosts file and not ask the next time it sees that host. 2) Hash the host names to ... -Sam -----Original Message----- From: ats...@gm... [mailto:ats...@gm...] On Behalf Of Atsuhiko Yamanaka Sent: Sunday, November 21, 2010 11:13 PM To: Quiring, Sam Cc: jsc...@li... Subject: Re: [JSch-users] Establish authenticity of remote host Hi, On Sat, Nov 20, 2010 at 12:57 AM, Quiring, Sam <Sam...@wi...> wrote: > Greetings, > > One remaining issue is every time we connect to a host we get the popup with > the message "The authenticity of host ... Are you sure you want to continue > connecting? [Yes|No]" > > What do we have to do so that a yes answer to this question also saves the > remote host key so that this question will not be asked the next time we > connect with the host? Please refer to http://www.jcraft.com/jsch/examples/KnownHosts.java Sincerely, -- 1-14-20 HONCHO AOBA-KU, SENDAI, MIYAGI 980-0014 Japan. Tel +81-22-723-2150 +1-415-578-3454 Skype callto://jcraft/ Twitter: http://twitter.com/ymnk |