through ssh with listen mode - how on Linux ??
Tue Apr 15 05:18:00 2003
--- Wayne Throop <firstname.lastname@example.org> wrote:
> So it's simple. On ws-at-work you (eg)
> ssh -2 -N -R 5901:localhost:5901 ws-at-home
> which will establish a reverse port redirection.
> Note: as somebody else already mentioned, this is a security risk
> to your corporate firewall, so you will want to be very careful,
> ensure your home system is secure enough to satisfy your
> corporate ip security folks.
> Now, on ws-at-home you simply run vncviewer, and choose localhost:1
> as the place you want to connect to. It's just that simple.
It is. Check and thanks!
> You could also make the redirection be -L 5501:localhost:5501 to do
> port forward to ws-at-home. In that case, you'd need to start the
> viewer at home with -listen 1, and use vncconnect at work something
> so: vncconnect -display :1 localhost:1. This would be less of a
> security risk, slightly, since everything is innitiated outgoing, and
> it'd be harder for somebody to force access to your corporate net
> because they have to already be on ws-at-work to run vncconnect at
> session startup.
This is convincing. Only, I don't get any display. Maybe somthing wrong
to be pointed out easily?
1. I start vncviewer -listen 1 on ws_at_home.
It tells me it's listening on port 5501
2. I start vncserver on ws_at_work.
It tells me "New 'X' desktop is ws_at_work:1
3. I start the link on ws_at_work with
ssh -2 -N -L 5501:localhost:5501 ws_at_home.
It asks for password and accepts (though no confirmation, just nothing.
But if I give the wrong one, it complains. Seems to be okay.)
4. I connect on ws_at_work using vncconnect -display :1 localhost:1
It returns the prompt on the next line and fails to connect (without an
error message on either side; simply no changes).
Yes, everything under root.
Thanks for any hint,
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo