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: | sshd windows server - automatic ssh linux authentication. |
|---|---|
| Date: | Mon, 18 Oct 2004 16:52:59 +0200 |
Thanks for your answer, Rajsekar.
That step has done it well for me, but I'm still with the problem.
I've spent at least 15 hours just with this, at the moment. I'm really
becaming crazy. It goes on asking for a password interactively. Maybe I
should change some option in the "ssh_config" file for the linux client and
the "sshd_config" file for the windows sshd server?
I'm using protocol 2. Maybe I'm not indicating the correct parameters
In the windows "sshd_config" file for the sshd server:
1)
What should I do with the "Hostkey" line? This is refered to the path in
client computers? If this is a windows path, how could write it?
2) I've put:
PubKeyAuthentication yes
I guess this is correct (?)
3) How can I write in windows the path to my authorized keys file? I'also seen
that something like
AuthorizedKeysFile C:\Program files\OpenSSH\etc\authorized_keys
prevents the server from starting.
In the linux "ssh_config" file, I'm writing:
PasswordAuthentication yes
HostbasedAuthentication yes
It always asks for a password, and if I put "PasswordAuthentication no", then
I've a message saying "Permission denied". Oh, my god!!
Well, thank you for any help or advice,
Javier
-------------------------------
El Lunes, 18 de Octubre de 2004 20:04, escribió:
You are trying to create two keys seperately. That is not the way Execute ssh-keygen once and you get a pair of keys, private and public. private is kept secret (client side). public is put in the server and since you want to tell ssh server that whenever you/anyone says he has got a key (private), the server should check the public, you will have to put it in some place(I do not know where to put in windows - Read documentation regarding this). In linux what you would (typically) do is this. Client$ ssh-keygen -t rsa -f new_key Enter passphrase (empty for no passphrase): Enter same passphrase again: ... ... ... Now you will (usually) add the file new_key.pub to ~/.ssh/authorized_keys in the server. Then you can use ssh `-i' option and everything must work as expected. I hope this clears the doubt even though I have provided quite terse info.
-- A. Javier Garcia Water and Soil conservation department CEBAS-CSIC Campus Universitario Espinardo PO BOX 164 30100 Murcia (SPAIN) Phone: +34 968 39 62 57 Fax: +34 968 39 62 13 email: rn001@cebas.csic.es
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Illegal user ssh probes, Christopher Strong |
|---|---|
| Next by Date: | scp problems with RedHat Machines to Unix w/SSH, Michael A Gilchrist |
| Previous by Thread: | Re: Illegal user ssh probes, Christopher Strong |
| Next by Thread: | scp problems with RedHat Machines to Unix w/SSH, Michael A Gilchrist |
| Indexes: | [Date] [Thread] [Top] [All Lists] |