Yes, this is the section of my install script
that generates the host key.
# Gen a key.
umask 022
PP1=`uname -ns`
PP2=`date +%T`
PP=`echo $PP1 PP2`
/usr/local/bin/ssh-keygen2 -p "$PP" -b 1024 -t dsa -c \
"Generating 1024-bit dsa hostkey. This may take a while." -o /etc/ssh2/hostkey
This is the same script that generates the keys on both systems.
In message <[EMAIL PROTECTED]>, Atro Tossavainen writes:
> Have you generated a host key on the second computer?
>
> --
> Atro Tossavainen (Mr.), Systems Analyst - email at URL - +358-9-850-111-86
> Institute of Biotechnology, University of Helsinki, Finland
> My opinions may freely be shared by my employers if they want to.
>
> < URL : http : / / www . iki . fi / atro . tossavainen / >
Mr. Atro Tossavainen was responding to my message:
>>Date: Sat, 01 Apr 2000 20:02:27 MST
>>To: [EMAIL PROTECTED]
>>From: Milton Calnek <[EMAIL PROTECTED]>
>>Subject: Help with ssh2 on Linux
>>
>>
>>Hello all,
>>
>>I am trying to use ssh2.0.13 bewteen to Linux boxes.
>>The boxes are mostly the same... ie: same kernel, glibc2.1.2.
>>
>>From host A (where all the source was compiled) I can use
>>either the ssh client or the sshd server.
>>
>>However, from host B, I cannot get the sshd deamon to work.
>>
>>When I run the daemon on host B, I get teh messages:
>>WARNING: ssh_privkey_read: Algorithm or key not supported.(1)
>>FATAL: ssh_privkey_read from /etc/ssh2/hostkey failed.
>>
>>I seem to be using the dl-modp algorithm on both hosts.
>>
>>
>>I have noticed that on host A (where the daemon works), the key length
>>is 32 bytes, while on host B (where the daemon does not work), it is
>>only 24 bytes.
>>
>>Any help is appreciated.
>>
>>Thanks.
--
Milton Calnek
At Telus: +1 403 530 3827 [EMAIL PROTECTED]
Fax: +1 403 530 4467
At Home: +1 403 229 2399 [EMAIL PROTECTED]
In Continental N/A: Cell: +1 403 870 8479
www.tti-telecom.com
GCS d- s:+ a- C++$ ULH+++$ P+++ L+++ E--- W-- N o? K w O? M+
V- PS++ PE Y+ PGP->+ t+ !5 X+ R tv b+ DI++ !D G>++++ e++
h--- r+++ y+++
