Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: ssh / keyless login problem

Subject: Re: ssh / keyless login problem
Date: Tue, 26 Jul 2005 11:58:44 +1000
SA wrote:
[...]
The first time the script runs after a long delay (ie overnight when the local host is turned off) ssh always asks for a password despite there being a valid key pair on both hosts. If I kill the script and run it again then it runs without asking for a password (as it should). My script needs to log in several times and run automatically so password free operation is essential.

I can't see why the first time fails - my only thought is that the remote machine mounts my home directory over NFS and maybe this causes a problem?

NFS should not be a problem, but maybe if your home directory is auto-mounted and there is some kind of delay in that process?


Does anyone have any suggestions as to:

How I might solve this problem?
How I might diagnose it? (it is hard to repeat it more than once a day)
How I might stop ssh from asking for a password and return an error instead? (in which case I can get my script to handle this exception with a dummy login).

Set the server to LogLevel DEBUG3 and wait for it to happen again, then look in the syslog to see what happened.


Any other suggestions?

Tell the client to use only pubkey auth ("ssh -o PreferredAuthentications=publickey ...") and put a sleep-and-retry or two into your script.


--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

<Prev in Thread] Current Thread [Next in Thread>