I guess you perform
all the updates and the prob seems to disappear (at least it did so in
my case!).
I don't think so. Which version are you using?
# rpm -q openssh
openssh-4.6p1-58.1
Could it be related to unauthorized logins? There are some in the log
but not all the time while I tried to
make sure your DNS works properly this usually happens when reverse
lookups are broken in my experience, that is most likely the cause,
there is a setting you can disable if you will not have a good working
DNS in your environment, I believe it is the GSSAPI options, if you
google search with
Johannes Nohl wrote:
I guess you perform
all the updates and the prob seems to disappear (at least it did so in
my case!).
I don't think so. Which version are you using?
# rpm -q openssh
openssh-4.6p1-58.1
Could it be related to unauthorized logins? There are some in the log
but not all
Hi Todd!
make sure your DNS works properly this usually happens when reverse
lookups are broken in my experience, that is most likely the cause,
there is a setting you can disable if you will not have a good working
DNS in your environment, I believe it is the GSSAPI options, if you
google
You know what you're saying. Great! That was the answer. THANKS.
Is it a security risk?
I uncommented this options in /etc/ssh/sshd_config:
# GSSAPI options
GSSAPIAuthentication no
GSSAPICleanupCredentials yes
(what I don't understand: I read that every option in config which is
commented
This normally is a problem with dns resolution. The resolv.conf file
should be updated automatically updated by dhclient when you get your
ip. If it isn't, then something is wrong.
But that's exactly what happens. All three nameservers are working and
I can look up my dial in IP using
Johannes Nohl wrote:
This normally is a problem with dns resolution. The resolv.conf file
should be updated automatically updated by dhclient when you get your
ip. If it isn't, then something is wrong.
But that's exactly what happens. All three nameservers are working and
I can look up
Dear list,
I just set up a new server running 10.3 (minimal text install).
Whenever I try to login using a ssh client (ssh on linux, putty on
windows) I encounter a long delay (appr. 15 seconds) after the
password input.
log/messages says sshd: reverse mapping ... I googled this and it was
about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/3/07, Johannes Nohl wrote:
Dear list,
I just set up a new server running 10.3 (minimal text install).
Whenever I try to login using a ssh client (ssh on linux, putty on
windows) I encounter a long delay (appr. 15 seconds) after the
