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]

tunneled ports not working

Subject: tunneled ports not working
Date: Mon, 4 Apr 2005 16:00:39 -0500
OpenSSH 3.9 server (packaged by HP - HP-UX Secure Shell-A.03.91.002) /
PuTTY 0.56 client / DSA 1024 key...

Any reason why a tunneled port would work when I use password auth. and
not work when I use public/private keys for auth?
The use of a key doesn't seem to make a difference when using an OpenSSH
client, only with PuTTY. Here's a snapshot of the log file dumped by
PuTTY.

---snip---
Event Log: Opening forwarded connection to localhost:5555
Outgoing packet type 90 / 0x5a (SSH2_MSG_CHANNEL_OPEN)
  00000000  00 00 00 0c 64 69 72 65 63 74 2d 74 63 70 69 70
....direct-cpip
  00000010  00 00 01 01 00 00 40 00 00 00 40 00 00 00 00 09
.....@...@.....
  00000020  6c 6f 63 61 6c 68 6f 73 74 00 00 15 b3 00 00 00
ocalhost.......
  00000030  16 63 6c 69 65 6e 74 2d 73 69 64 65 2d 63 6f 6e
.client-side-on
  00000040  6e 65 63 74 69 6f 6e 00 00 00 00                 nection....
Incoming packet type 92 / 0x5c (SSH2_MSG_CHANNEL_OPEN_FAILURE)
  00000000  00 00 01 01 00 00 00 01 00 00 00 0b 6f 70 65 6e
...........open
  00000010  20 66 61 69 6c 65 64 00 00 00 00                  failed....
Event Log: Forwarded connection refused by server: Administratively
prohibited [open failed]
---/snip---


Never seen this behavior before...


-Carl


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