Google
  Web www.spinics.net

SSH Query

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Hi, 

We are doing an ssh from RHEL machine to the remote target that runs
linux. 

Things are fine when we hit the right password first time. However, if
we hit the wrong password in the first go, and then subsequently enter
right passwords in the next ones, we still see "Permission Denied"
messages. 

I have ran both the server and client in debug modes, with a first wrong
password and then right passwords. The output messages are:

Client @ 192.168.99.50:
-----------------------

debug1: Next authentication method: password root@xxxxxxxxxxxxx's
password: 
debug1: Authentications that can continue:
publickey,gssapi-with-mic,password
Permission denied, please try again.
root@xxxxxxxxxxxxx's password: 
debug1: Authentications that can continue:
publickey,gssapi-with-mic,password
Permission denied, please try again.
root@xxxxxxxxxxxxx's password: 
debug1: Authentications that can continue:
publickey,gssapi-with-mic,password
debug1: No more authentication methods to try.
Permission denied (publickey,gssapi-with-mic,password).
wrlinux@pcajain:/home/wrlinux/WindRiverGpp>


Server @ 192.168.99.51:
-----------------------

debug1: PAM: initializing for "root"
debug1: PAM: setting PAM_RHOST to "192.168.99.50"
debug1: PAM: setting PAM_TTY to "ssh"
debug1: userauth-request for user root service ssh-connection method
password
debug1: attempt 1 failures 1
debug1: PAM: password authentication failed for root: Authentication
failure Failed password for root from 192.168.99.50 port 38103 ssh2
debug1: Unable to open the btmp file /var/log/btmp: No such file or
directory led password for root from 192.168.99.50 port 38103 ssh2
debug1: Unable to open the btmp file /var/log/btmp: No such file or
directory
debug1: userauth-request for user root service ssh-connection method
password
debug1: attempt 3 failures 3
debug1: PAM: password authentication failed for root: Authentication
failure Failed password for root from 192.168.99.50 port 38103 ssh2
debug1: Unable to open the btmp file /var/log/btmp: No such file or
directory Connection closed by 192.168.99.50
debug1: do_cleanup
debug1: do_cleanup
debug1: PAM: cleanup
root@x:/root>

Apparently, the right passwords entered at trial 2 & 3 are also treated
like the wrong ones. If we try the same between any two RHEL machines,
everything works fine. Clearly the 'sshd' on target is a suspect, either
for configuration or for its code. I have tried looking google, but
could not find the same issue. I was looking at the options present in
start-up files, but could not locate a similar option for configuration.
The options available either disable password checking or allow it. 

Does somebody have an insight?

Regards,
Ajay

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

[Site Home]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux ARM Kernel]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Tools]     [DDR & Rambus]     [Monitors]

Powered by Linux

Google PageRank Checking tool