I haven't had any problems, yet I haven't upgraded it since I installed
Mandrake 8.0.
However, one of the things that our "Buddies" at OpenBSD and OpenSSH like
to do, is completely change the config files. The version that comes with
Mandrake 7.2, and the version that you upgraded to a few months later, has
a completely difference /etc/ssh/sshd_config. Now it has a banner you can
add and more.
What it sounds like you have going on now, would be strict host checking.
When I read your message that was the first thing that came to mind. Here's
where you can find that option.
/etc/ssh/ssh_config
# $OpenBSD: ssh_config,v 1.9 2001/03/10 12:53:51 deraadt Exp $
# This is ssh client systemwide configuration file. See ssh(1) for more
# information. This file provides defaults for users, and the values can
# be changed in per-user configuration files or on the command line.
# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# Site-wide defaults for various options
Host *
ForwardAgent yes
ForwardX11 yes
RhostsAuthentication no
RhostsRSAAuthentication yes
RSAAuthentication yes
PasswordAuthentication yes
FallBackToRsh no
UseRsh no
BatchMode no
CheckHostIP yes
StrictHostKeyChecking no
IdentityFile ~/.ssh/identity
IdentityFile ~/.ssh/id_dsa
IdentityFile ~/.ssh/id_rsa1
IdentityFile ~/.ssh/id_rsa2
Port 22
Protocol 2,1
Cipher blowfish
EscapeChar ~
TransmitInterlude 100
Host *
ForwardAgent yes
ForwardX11 yes
# Cipher 3des
TransmitInterlude 100
StrictHostKeyChecking no
You can either comment out the StrictHostKeyChecking line, or you can
simply make sure it's set to no. It's good to have it set to yes, just
for security. Makes it a bid more difficult to get into the machine if
it is set like that, but if you're not always accessing it from the same
machine, or the same IP address, that can cause problems. So a lot of
people just leave it set to no.
Start looking at that file, which is /etc/ssh/ssh_config. Look for things
like the strict host checking. You can also compare it to the syntax I
pasted above. That came from a Mandrake 7.2 machine, with the up to date
SSH. (Myself and the other Linux Admin of that server always keep up on
the updates for that machine.) You can also go through /etc/ssh/sshd_config
file that has some more configs in it.
That should get you off to a start, and honestly I think it's the StrictHostKeyChecking
but good luck, and if that doesn't try the list again.
tdh
T. Holmes
Unixtechs.org
[EMAIL PROTECTED]
"Real Men use Vi."
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [010524 18:25]:
| hi!
| i'm running mandrake 7.1 and run ssh server in order to access my pc during daytime
|when i'm not home. as a common behaviour i updated the ssh related packages today.
|since that update i can not remotely login. i have to mentian that sshd had been up
|and running fine just till after updating. have anyone been having same problem ? is
|there anything i have to configure to make it work again ? all suggestions are welcome
| thanks in advance
| __________________________________________________________________
| Get your own FREE, personal Netscape Webmail account today at
|http://webmail.netscape.com/
