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. |

| Subject: | Re: Connect with null passphrases |
|---|---|
| Date: | Wed, 06 Dec 2006 15:50:23 +0100 |
Hello, we use ssh keys for cron jobs. The private keys used for connecting dont require a password. http://www.ssh3.com/support/documentation/online/ssh/adminguide/32/Public-Key_Authentication-2.html John Stefani schrieb:
Hello Everybody,
I have some cron jobs that use ssh (version 4.4p1) to connect to other
servers and run certain tasks. The users in question sometimes are
real users, sometimes fictitious users that I created only for running
the cron job. I changed to *NP* the password field of /etc/shadow for
the fictitious users on the servers the cron jobs connect to, and all
works happily. Here's my problem: those servers to which the cron
job tries to connect to as a real user, who has a real password, does
not allow ssh connections with null passphrases. I can't set the
password field in /etc/shadow to *NP* because sometimes I have to
connect as the real user. Does someone know how I can connect
automatically to a server, using ssh, as a user that has a password,
but with a null passphrase? Hope the above was not too confusing...
Absolutely any thoughts or workarounds will be much appreciated.
John Stefani
jstefani _at_ yorku.ca
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Connect with null passphrases, Michael Ekstrand |
|---|---|
| Next by Date: | commercial SSH vs. OpenSSH, jalburger |
| Previous by Thread: | Re: Connect with null passphrases, Michael Ekstrand |
| Next by Thread: | Generating SSL certificate for Apache HTTPD breaks SSH, samljones |
| Indexes: | [Date] [Thread] [Top] [All Lists] |