On Thu, Sep 29, 2011 at 4:48 PM, Francis Devereux <francis@devrx.org> wrote:

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?

If JSch would throw the exception regardless of the value of StrictHostKeyChecking, what's the point of this option anyway?