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: SSH command in windows |
|---|---|
| Date: | Mon, 15 Oct 2007 21:57:28 -0400 |
In order to avoid having to enter a password with the SSH command, you will need to do one of two things: 1) Allow some sort of key authentication using a public/private key pair (preferred). This will require you to generate the keys and place them in the correct location on the server and the client-side. I'm unfamiliar with using keys with the ssh command-line under a Windows environment, so you might check its documentation. Depending on your SSH implementation on the remote UNIX host, various steps should be taken to configure this there as well. This will require your additional access. 2) You could somehow butcher the SSH login authentication using PAM to where it no longer requires a password. I've done this by accident on a Linux box, so I know it works. However, this is probably the worst recommendation of all time, so I wouldn't do this. At any rate, I believe you will need to involve the UNIX administration team for the server on your efforts and perhaps they could assist in your endeavor. John Hall (securityfocus@neovolo.com) Technological Solutions Team Neovolo - New Life to Business SolutionsT http://www.neovolo.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.14.11/1071 - Release Date: 10/15/2007 6:48 AM
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | ssh connection stop at "debug1: SSH2_MSG_KEXINIT sent" - problem with linux 2.6 and vista, Marco Vannini |
|---|---|
| Next by Date: | public key authentication problem, Jan Kaspar |
| Previous by Thread: | Re: SSH command in windows, edw |
| Next by Thread: | .ssh/config equivalent of -q ?, Jason Bradley Nance |
| Indexes: | [Date] [Thread] [Top] [All Lists] |