Note: If you are using "red" or any subsequent site realm (basically, if your site's realm name is a color), outbound ssh (including to other member sites) should work normally and you should be able to disregard this entry.
It's a bit tricky. Due to an operating system limitation that we have not yet been able to work around, the ssh application cannot prompt you when establishing an outbound connection. If you run into this problem, you will most likely see a message like "host key verification failed."
To make it work you need:
- The destination host's host key in your /home/private/.ssh/known_hosts file.
- A public/private keypair that the destination host will accept.
- No passphrase on the private key.
Since this isn't the most secure state of affairs, we recommend that you not store such private keys on our network, but instead, scp them in when you need them and delete them when you are finished.
In general, although it is possible to make this work, it's better if you can refactor what you're doing to ssh into our server instead if you have that option. Also keep in mind that we offer ssh solely for the purpose of maintaining your website. It is not a "general purpose" Unix shell account and using it as such might cause bad things to happen to you.
The following factors are different if you intend to ssh out from our ssh server into our ssh server (e.g. from one site hosted here to another):
- You must install the public key you wish to use via our member interface so that our system will recognize it as authorized.
- You should currently use the -4 flag with ssh/sftp/scp when ssh'ing internally. Our IPv6 support is not fully implemented. Example: ssh -4 firstname.lastname@example.org