On Wed, 25 Jun 2008, Eric Lease Morgan wrote:

> On Jun 25, 2008, at 11:21 AM, Nate Vack wrote:
>
>>> $ ssh -T -L 3306:mysql.example.org:3306 [log in to unmask] &
>>> $ mysql -h mysql.example.org
>> 
>> Yeah -- this is (probably) the way you want to do it, though. You'll need 
>> to:
>> 
>> * Set up SSH keys such that building the tunnel doesn't prompt for a 
>> password
>> * Run the local end of the tunnel on a free port
>> * Configure your local client to talk to the local end of the tunnel
>
> I went to Plan B, namely, installing my Perl module on the remote host where 
> the MySQL database resides. Doing the tunneling thing was too much like using 
> my right hand to reach around my head to scratch my left ear. Cumbersome.

SSH tunneling is an odd concept at first, but it's very useful if you 
don't have VPN ...

For instance, when I'm on the road, I use tunneling to make my e-mail look 
like it's coming from a machine that our SMTP server will route mail for.

I've also used it for checking development websites that are behind 
firewalls, by connecting the tunnel to my local port 80.  (you also need 
to adjust your /etc/hosts or equivalent if the site isn't good about using 
relative or root-relative links to their local content).

> Now I have YAUAPTR (Yet Another Username And Password To Remember). /me 
> sighs too


Get a password management program... I have 93 in one, and 165 in another 
... and my work wants us to have seperate login & wheel accounts, which is 
going to add another 31.  There's no way in hell that I could remember 
them all.

-Joe