“In the past, TextMate has suffered with editing files on a server, but thats all changed now. If you regularly find yourself SSHed into a remote box and wanting to edit a file using TextMate on your own box, your ship has come in.TextMate 2 now ships with an rmate Ruby script that you can drop onto servers. When you trigger rmate on a remote box, it will connect back to your box, allow you to edit, and update the file on the server with the changes.”
I needed a pair of DSA keys recently, not standard ssh DSA keys but PEM keys. Creating DSA PEM keys is something best suited to `openssl` but it can be a pain in the butt to get the params set up right. And othing creates key pairs quite as easily as `ssh-keygen` so I thought, what the heck, let’s combine the best of both worlds.
I figured I’d keep my new keys in `~/.ssh` where my RSA keys already live:
$ cd ~/.ssh
The next step is to create an ssh DSA key pair with `ssh-keygen`. `-t` sets the type (dsa in this case) while `-b` sets the number of bits (dsa are limited to 1024):
$ ssh-keygen -t dsa -b 1024
You’ll be asked for a file name and location (default is fine), and ask you for a passphrase. Unless you want the client side to always be prompted for a passphrase, I’d leave this blank.
Then we’ll use `openssl` to convert the ssh private dsa to a PEM. The default dsa we just created would be called `id_dsa`. If you named it otherwise, then change this line accordingly after the `-in` option:
$ openssl dsa -in id_dsa -outform pem > dsa_priv.pem
Now we have a private DSA PEM that we can use to create our public PEM:
$ openssl dsa -in dsa_priv.pem -pubout -out dsa_pub.pem
In your `~/.ssh` folder you’l now have `dsa_priv.pem` and `dsa_pub.pem`. Keep the private DSA PEM in a safe place and use the `dsa_pub.pem` as necessary for your client needs.
I’ve been playing around with ssh while I configure my Ubuntu Server (more details about that soon) and figured I would get my head out of the terminal for a bit. So I downloaded [ExpanDrive](http://www.expandrive.com/ “ExpanDrive for Windows: Ridiculously simple SFTP drive access on your PC”) again (used it a [while back](http://www.seydoggy.com/2008/03/10/expandrive-expands-my-horizons/ “seyDoggy Web and Graphic Design – seyDoggy weblog – my thoughts on the web and the mac”)) only to discover that it’s since been upgraded… a paid upgrade… and my old serial no longer applies. I wasn’t enamoured with “mounting” remote servers as hfs volumes enough to pay for this app a second time so I decide to move on to the free alternative; [MacFUSE](http://code.google.com/p/macfuse/ “macfuse – Project Hosting on Google Code”) + [MacFusion](http://www.macfusionapp.org/ “Macfusion: The world in your Finder”).
The only hiccup I encountered was that MacFusion didn’t seem all that happy about launching an ssh connection under Mac OS X 10.6 Snow Leopard. I could connect with no issues in terminal but not in MacFusion. A quick visit to the [MacFusion Google Group](http://groups.google.com/group/macfusion-devel “MacFusion-devel | Google Groups”) revealed [this temporary solution](http://rackerhacker.com/2009/08/28/fix-macfusion-on-snow-leopard/ “Fix MacFusion on Snow Leopard | Racker Hacker”), which is basically:
1. quite MacFusion
2. set up MacFUSE to get betas (under System Preferences)
3. and remove this file in Terminal:
To get the nitty-gritty, please read the full post at [Racker Hacker](http://rackerhacker.com/2009/08/28/fix-macfusion-on-snow-leopard/ “Fix MacFusion on Snow Leopard | Racker Hacker”).
[tags]snow leopard,mac osx,terminal,ssh,server,macfuse,macfusion[/tags]