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: Connecting to host |
|---|---|
| Date: | Wed, 4 Jul 2007 11:15:42 -0700 (PDT) |
On Tue, 3 Jul 2007, Kelly Thomas wrote:
We have recently been asked by one of our vendors to connect to their system through SSH. They are a Unix Host - beyond that, I don't have much information. We are a 'windows' shop and I'm using Putty version 0.60 to connect with a Windows XP Professional machine. I have created a public key and sent it to them. They have also sent their public key to me. From what they're telling me, there should be no password to connect. When I try to connect it first asks for my passphrase. I'm assuming it will only do that the first time to validate my key - not sure.
The private key you created with PuTTY may require a passphrase. That may be what you're seeing. Or, their end may not be correctly finding the public key for you. If it's not, then it may be reverting to password or keyboard-interactive authentication. I believe PuTTY can run with some debugging turned on. This will give you some information about what authentication methods it is finding, allowing, tying, failing, etc.
After typing in my passphrase for the key, I get a disconnect message: Server sent disconnect message type 7 (service not available): "Unsupported request (pty-req)."
This sounds seriously like their SSH daemon is not set up properly. Are THEY able to SSH to their server? Are they able to do so and log in with your username? It's also possible that they succeed from inside their firewall, but when you attempt to come in from outside the firewall, the firewall (or router) is intercepting the SSH connection. They would need to configure the firewall/router to forward a port 22 (default for SSH) connection to the appropriate internal machine. Are THEY able to connect in from the Internet at large (outside their office)?
This message appears to be something on their end but they are telling me it's on my end. Can anyone help?
It sounds to me like it is on THEIR end.
You might want to try Anzio Lite, our SSH client, available from the
website below.
Regards,
....Bob Rasmussen, President, Rasmussen Software, Inc.
personal e-mail: ras@anzio.com
company e-mail: rsi@anzio.com
voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
fax: (US) 503-624-0760
web: http://www.anzio.com
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | SCP from OpenSSH to Fsecure SSH, unable to establish SCP version 2, Heng Kuo Kuang Kelvin NCS |
|---|---|
| Next by Date: | RE: Connecting to host, Kelly Thomas |
| Previous by Thread: | Re: Connecting to host, Justin Alcorn |
| Next by Thread: | RE: Connecting to host, Kelly Thomas |
| Indexes: | [Date] [Thread] [Top] [All Lists] |