My G+ Profile
« Preparing Students to be Influential | Main | Cut the Vision in Half and Ship It »
SSH Tricks
Linux Journal has a nice article on Eleven SSH Tricks. These, of course, work on OS X as well. If you’re an OS X user, you may not be all that interested in the first one, X11 forwarding, but skip that one and read the rest.
I’ve used SSH for years for securing remote sessions and copying operations. I’ve never used it for port forwarding, but I may play with that a little. BYU doesn’t offer VPNs for faculty and I’ve never bothered to set one up myself. Port forwarding would take care of some of the little things I worry about when I’m traveling.
Posted by windley on December 12, 2005 9:57 AM
Comment from Joseph Scott at December 12, 2005 10:35 AM
If you are using SSH on Mac OS X you need to check out SSH Agent for OS X:
http://www.phil.uu.nl/~xges/ssh/
It can take care of many of these tasks for you.
Comment from brent ashley at December 12, 2005 10:57 AM
Hi Phil;
I wrote about how I use port forwarding last year.
http://www.ashleyit.com/blogs/brentashley/?p=529
I you need any help when you set something up for yourself, just send me an email.
Comment from Nathan at December 12, 2005 10:11 PM
Why is port forwarding X11 "not all that interest[ing]"? Running a linux X application on a linux server and having the app show up on X11 on my PowerBook is very useful--especially for apps that don't have a darwin port.
Of course, it would be even MORE useful if Gentoo's current version of X and Apple's X11 were a bit nicer to eachother. I tend to get a lot of X11-related crashes due to some bug between the two. I ought to install x.org on my powerbook...
Comment from Eric Pan at December 12, 2005 11:18 PM
Here are some of the problem/inconveniences with port forwarding over SSH.
1. It is not two way communications.
2. The server that I am connecting to is identifying itself by its DNS name, not localhost.
3. I've have to edit my HOSTS file on my machine to resolve to the DNS names to localhost.
To solve the problem, I run Red Hat Linux in both my office and home. Then, I setup a VPN over SSH. This way I don't have to worry about my applications not being able to find the host. Other benefits includes being able to see my Samba or windows shared folder in my office, being able to print to the network printer, all my machines in my home network can access all offices machines without additional configuration other than changing the route table.
The only inconvience with this solution is not being able to use DNS server in my office as it does not handle UDP. So, I have to run my DNS server at home.
For more information using VTUN over SSH, look here: http://www.linuxjournal.com/article/6675