Check that /etc/pam.d/sshd on the server does not have any errors.
Make certain that $HOME/.ssh has perms set to 700.
If these are OK (they probably are) then stop sshd on the problem
server and restart it in debug mode.
# service sshd stop
# sshd -d
Try logging in and see what the server
Taylor, ForrestX [EMAIL PROTECTED] writes:
Did you use ssh -v -v -v? Did you check /var/log/secure?
/var/log/secure only says
Dec 11 12:10:39 server sshd[10325]: Accepted publickey for oleg from 192.168.0.7
port 37287 ssh2
I posted ssh -v output earlier, here is the tail of the output
Another arbitrary guess. Does the remote user have a valid shell?
___
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
On 11 Dec 2001, Oleg Goldshmidt wrote:
Keith Morse [EMAIL PROTECTED] writes:
Another arbitrary guess. Does the remote user have a valid shell?
# grep oleg /etc/passwd
oleg:x:500:500:Oleg Goldshmidt:/home/oleg:/bin/bash
# /bin/bash --version
GNU bash, version 2.04.21(1)-release
Jack Bowling [EMAIL PROTECTED] writes:
Oleg, I just went through this on 7.2. In my case, I had to add the
client IP to /etc/hosts.allow since RH compiles ssh with
libwrap. Check yours out.
Thanks, Jack, but it didn't help, either: I added
ALL:192.168.
to /etc/hosts.allow on the server,
Hi Oleg,
On 10 Dec 2001, Oleg Goldshmidt wrote:
Jack Bowling [EMAIL PROTECTED] writes:
Oleg, I just went through this on 7.2. In my case, I had to add the
client IP to /etc/hosts.allow since RH compiles ssh with
libwrap. Check yours out.
Thanks, Jack, but it didn't help, either: I
Try to disable X-forwarding (ssh -x) or if it dont work try the verbose
mode (ssh -v) to see where it fails..
Dams
You wrote :
On 10 Dec 2001, Oleg Goldshmidt wrote:
Jack Bowling [EMAIL PROTECTED] writes:
Oleg, I just went through this on 7.2. In my case, I had to add the
King_Kong [EMAIL PROTECTED] writes:
Did you /etc/ssh/sshd_config have a :
AllowUsers put_your_login_here
? :)
No ;-)
--
Oleg Goldshmidt | [EMAIL PROTECTED]
If it ain't broken, it has not got enough features yet.
___
Seawolf-list mailing
Dams [EMAIL PROTECTED] writes:
Try to disable X-forwarding (ssh -x)
No difference (and it shouldn't matter)
or if it dont work try the verbose mode (ssh -v) to see where it
fails..
I included ssh -v output with my original posting.
--
Oleg Goldshmidt | [EMAIL PROTECTED]
If it ain't
On 10 Dec 2001, Oleg Goldshmidt wrote:
King_Kong [EMAIL PROTECTED] writes:
Did you /etc/ssh/sshd_config have a :
AllowUsers put_your_login_here
? :)
No ;-)
Hey Oleg, wanna try it out...? I've used to be the same situation before.
:)
K_K
--
Oleg Goldshmidt | [EMAIL
King_Kong [EMAIL PROTECTED] writes:
AllowUsers put_your_login_here
Hey Oleg, wanna try it out...? I've used to be the same situation before.
Oh, but I did... And I don't understand why it should help - by
default everybody is allowed (at least according to man sshd), so
listing users
Just in case it might help, here is the (not commented part of)
/etc/ssh/sshd_config on the problematic server:
Port 22
HostKey /etc/ssh/ssh_host_key
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
ServerKeyBits 768
LoginGraceTime 600
KeyRegenerationInterval 3600
On 10 Dec 2001, Oleg Goldshmidt wrote:
Just in case it might help, here is the (not commented part of)
/etc/ssh/sshd_config on the problematic server:
You've certainly got my interest now. The parameters in sshd_config you
posted appear to match my stock one on RH7.2 box (sans commented
I suddennly cannot ssh as user to one of our RH7.1 machines. I used to
be able to... I can ssh as root without a problem, but no ordinary
user can connect, either using RSA or DSA keys, or ssh 1, or just with
a password. This happens for several clients. The clients are able to
connect to other
One machine or the other could be blocking ports above 1024,
which ssh also needs to complete the connection.
Check firewall logs on the server, and make sure
that logging is turned on for anything that's not accepted,
at least while you're debugging.
If this is the only server where the
Jan Carlson [EMAIL PROTECTED] writes:
One machine or the other could be blocking ports above 1024,
which ssh also needs to complete the connection.
No, that's not the case. And remember that I can ssh as root - I think
ssh needs non-reserved ports in that case as well.
If this is the only
** Reply to message from Oleg Goldshmidt [EMAIL PROTECTED] on 09 Dec 2001
12:24:57 +0200
I suddennly cannot ssh as user to one of our RH7.1 machines. I used to
be able to... I can ssh as root without a problem, but no ordinary
user can connect, either using RSA or DSA keys, or ssh 1, or
17 matches
Mail list logo