Actually there are a lot of good reasons to keep running SSH1. The main
one is to have backward compatibility since not everyone is using SSH2.
Also has been around much longer and they have worked out all the bugs in
this software, which SSH2 is still working on. Secondly SSH2 has no option
on the Windows side to choose form a List of Servers and then pick one and
log in. TTSSH+SSH1 has this ability, this is very important for for a lot
of Window Users who just don't know the Server Names. Secondly there are
two steps that you need to do in the .ssh2
a). add the name of the pub_key.pub to the authorization file.
b). copy the pub_key.pub file to the remote computer.
Although it is not too difficult to do.
One question I hope one of you can answer for me is in SSH2 is if there is
also a \etc\ssh_known_hosts file
which the administrator can keep updated and then distribute to all the
clients such that no annoying prompts are give to the users asking them if
they wish to accept the Public Key. If the user answer yes then the public
key would then be added to the local machine $HOME$\.ssh\know_hosts file
?
How is this handled in SSH2 and what does the Admin have to do ?
A brief explanation would be appreciated.
-----Original Message-----
From: Atro Tossavainen [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, June 08, 2000 9:09 PM
To: [EMAIL PROTECTED]
Subject: FAQ section 1.12
> there is no reason to continue to run the SSH1 implementations.
Aside from the fact that patches exist for ssh1 to work with certain
environments (such as AFS; possibly others, can't think of any) that do
not exist for ssh2 yet, and as far as I have heard from the developers,
aren't even in the works.
So maybe it should have this pointed out in the FAQ.
--
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 / >
