Hello,

we have encountered the rekeying-bug 
discussed on this list in august and december 2000 
in a "ssh 2.3 - only" environment.

As "announced" by Sami Lehtinen, it is also present in unix-ssh 2.4. 

When automatic or manual (~r) rekeying is invoked,
the client does NOT search (or find?) the remote hosts public key in the
GLOBAL hostkeys dir.

Whenever the remote public key is not stored in the users
local directory (~/.shh2...), the connection will be interrupted
at rekeying time.
 
This looks like:
---
aixnetm3:/home/x80>                           [~V]
ssh: SSH Secure Shell 2.3.0 (non-commercial version) on
powerpc-ibm-aix4.2.1.0

aixnetm3:/home/x80>                           [~r]
Rekeying.
Host key not found from database.
Key fingerprint:
xegiv-gykac-dokut-cegyg-fazun-tazis-zohic-neril-fevuv-mezos-luxex
You can get a public key's fingerprint by running
% ssh-keygen -F publickey.pub
on the keyfile.
FATAL: sshreadline.c:1778 SshReadLine (function name
unavailable) Precondition failed: rl
aixnetm1:/home/x80> 
---

This is astonishing, 
since in the normal first login process all works fine.

The error seems to lay somewhere in sshunixuserfiles.c or "nearby", 
as debug-mode proposes:
---
at login-time:
debug: Ssh2Transport/trcommon.c:1278: ssh_tr_input_packet: read 632 bytes
debug: Ssh2Client/sshclient.c:301: checking key
        /home/x80/.ssh2/hostkeys/key_22_an3.pub
debug: SshUnixUserFiles/sshunixuserfiles.c:200: file
        /home/x80/.ssh2/hostkeys/key_22_an3.pub does not exist.
debug: SshUserFiles/sshuserfiles.c:508: key blob magic = 0x20000bdc
debug: Ssh2Client/sshclient.c:399: Host key found from database.
debug: Ssh2Transport/trcommon.c:1551: ssh_tr_send_simple_packet 21 
---
at rekeying-time:
debug: Ssh2Transport/trcommon.c:1278: ssh_tr_input_packet: read 652 bytes
debug: Ssh2Client/sshclient.c:301: checking key
        /home/x80/.ssh2/hostkeys/key_22_an3.pub
debug: SshUnixUserFiles/sshunixuserfiles.c:200: file  
        /home/x80/.ssh2/hostkeys/key_22_an3.pub does not exist.
Host key not found from database.
---

Has anyone else had this problem?
Is there an easy fix for this bug?

Our workaraound is a wrapping script, which copies the global public
key temporarily to the users local .ssh2-directory, and then invokes
ssh...

-- 
Best regards,

Joachim Peeck                       [EMAIL PROTECTED]

Reply via email to