|
|
Necessary and sufficient ssh port forwarding
If you execute the first ssh command (fixed as described in the other posts) on the client machine (i.e., the one that you want to use to control the other), then that will encrypt all communication between client and server. Additional ssh port forwarding is unnecessary. Indeed, the ssh command in Rob's edit doesn't really accomplish anything here. It takes all packets destined for port 1202 on the server machine and forwards them to port 5900. With this setup, though, you won't be sending any packets to port 1202 on the server side -- they're going to port 1202 on the client side, and the first ssh command takes care of the necessary forwarding. Finally, if the server machine has a globally-visible hostname, you can use that instead of the IP address in the ssh command.
Necessary and sufficient ssh port forwarding
...and I thought this was a simple Hint...
Necessary and sufficient ssh port forwarding
So what's the proper command to create a secure tunnel for using a VNC connection to remotely control my Mac?
Necessary and sufficient ssh port forwarding
I had successful connections using the following command:
ssh -N -f -L 5999:127.0.0.1:5900 user@remoteMac after authentication, launch Chicken of the VNC (or your preferred VNC viewer) and use localhost:5999 as destination server. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.06 seconds |
|