Hi,
+-From: Francis Devereux <[email protected]> --
|_Date: Thu, 29 Sep 2011 14:48:05 +0100 _______
|
|I've noticed that JSch allows connections even when the remote
|host's key has been changed if StrictHostKeyChecking is "no".
|I'd expect it to throw a "HostKey has been changed" exception in this case.
|Is the current behaviour intentional?
Yes, it is an intentional behavior.
StrictHostKeyChecking should not be "no" in the practical usage,
and choose "ask" or "yes".
Sincerely,
--
Atsuhiko Yamanaka
JCraft,Inc.
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
Facebook: http://facebook.com/aymnk
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
JSch-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jsch-users
