: > Hmm. If a hostkey is changed on disk, when a session to that host is
: > already established, and rekeying is enabled, this happens (it is a
: > known bug). Workaround is not to change the hostkey on that remote
: > system on regular basis :) Also, you can disable rekeying (note that
: > they must be disabled on both client and server).
:
: The hostkey is changed using ssh-keygen, right ? then that isn't the
: problem since the only time we regenerate hostkey are when a machine is
: re-installed.
: I'm not positive on that "rekeying" thing - how does one disable or enable
: it ?
If you are running against OpenSSH, then it is because OpenSSH doesn't
support rekeying. ssh 2.4 should work against OpenSSH also in this
case (rekeying is always disabled with OpenSSH).
You can disable rekeying manually by changing the value of
RekeyIntervalSeconds to '0'.
: > This is not fixed with the upcoming 2.4.0 release, I'm afraid. (blame me)
: >
: > : Also, is there any clear date on the next release of ssh the is supposed
: > : to fix the compatibility problem between ssh and openssh ?
: >
: > 2.4.0 should be compatible (in our tests has been) with OpenSSH, and
: > it will be released soon (< 2 weeks).
:
: OpenSSH 2.2 fixes the compatibility problem with ssh 2.3.0, but do you
: mean the ssh 2.4 will be compatible with previous versions ?
Yes.
Cheers,
--
[[EMAIL PROTECTED] -- Sami J. Lehtinen -- [EMAIL PROTECTED]]
[work:+358 9 85657425][gsm:+358 50 5170 258][http://www.iki.fi/~sjl]
[SSH Communications Security Corp http://www.ssh.com/]
