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]

Re: X11 tuneling: a hard to fix problem

Subject: Re: X11 tuneling: a hard to fix problem
Date: Mon, 24 Apr 2006 15:40:49 +0200

Ok i ran `sshd -ddd` following the suggestion of Jonathan Loh:

Then local.client.desktop# xterm  
.             .        .
.             .        .
.             .        .
debug1: session_input_channel_req: session 0 req x11-req
debug2: bind port 6010: Cannot assign requested address   
debug1: channel 1: new [X11 inet listener]
debug1: server_input_channel_req: channel 0 request pty-req reply 0
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req pty-req
debug1: Allocating pty.
debug1: session_new: init
debug1: session_new: session 0
.             .        .
.             .        .
.             .        .
.             .        .
    And now it goes

For some reason the DISPLAY variable was set to localhost:11.0.
Now i stop && start the sshd and it always forwards DISPLAY
correctly, without changing any config file.

I know we get lasy to understand a problem once we solved it
without understanding, but i these case I'd like to know it
anyone has an idea what happened.
The `ssh -vvv remote.server` shows the same messages as before. 

For some reason the remote.server was not getting the conection
to port 6010, as seen above. But know it gets !!! ???

Thanks all for the help,
nader

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