Gordon,
Thanks, the install went fine and I now connect using SSH2. I am, however,
getting a "Failed to open a secure file transfer session" message when I
connect, which I wasn't before (although Secure File Transfer didn't work
previously -- I just assumed that it isn't supported).
Maybe my client settings are wrong. I'm using SSH Secure Shell 2.4.0 (Build
163).
Regards,
Mark.
-----Original Message-----
From: Gordon Rowell [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 24, 2001 9:09 PM
To: Mark Farey
Cc: 'E-smith developers list'
Subject: Re: [e-smith-devinfo] SSH after 4.1.2 upgrade
On Tue, Apr 24, 2001 at 11:50:01AM -0400, Mark Farey <[EMAIL PROTECTED]>
wrote:
>
> I upgraded to 4.1.2 but now when I remotely connect ssh I get a warning
> message that the host is now using SSH1 protocol and that it's not secure.
> What changed? (Sorry if I missed this in an earlier thread).
> [...]
Could you try (one line of course):
rpm -Uvh ftp://ftp.e-smith.org/pub/e-smith/contrib/GordonRowell/RPMS/noarch/
e-smith-openssh-1.2.0-03.noarch.rpm
/sbin/e-smith/signal-event remoteaccess-update
and let the list know if this fixes your problem. openssh-2.5 requires
an extra HostKey line in /etc/ssh/sshd_config for the DSA host key.
Gordon
--
Gordon Rowell [EMAIL PROTECTED]
http://www.e-smith.org (development) http://www.e-smith.com (corporate)
e-smith, inc. 1500-150 Metcalfe St, Ottawa, ON K2P 1P1 Canada
