diff options
Diffstat (limited to 'Components/SSH-Contact.mdwn')
| -rw-r--r-- | Components/SSH-Contact.mdwn | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/Components/SSH-Contact.mdwn b/Components/SSH-Contact.mdwn new file mode 100644 index 0000000..65dd231 --- /dev/null +++ b/Components/SSH-Contact.mdwn @@ -0,0 +1,34 @@ + + +# Description + +SSH-Contact is a client/service tool that makes it easy to connect to your telepathy IM contacts via SSH. No need to care about dynamic IP, NAT, port forwarding, or firewalls anymore; if you can chat with a friend, you can also SSH to their machine. + + +# Links + +* [[SSH-Contact releases|http://telepathy.freedesktop.org/releases/ssh-contact/]] +* [[SSH-Contact git|http://cgit.freedesktop.org/telepathy/telepathy-ssh-contact/]] +* [[Report a bug|https://bugs.freedesktop.org/enter_bug.cgi?product=Telepathy&component=ssh-contact]] + +# FAQ + + +## Does it work if I'm using pidgin? + +No. You and the contact you are sshing must be online using a Telepathy client (like Empathy). + + +## Which IM protocols are supported? + +Currently only Jabber (using telepathy-gabble) is supported. But ssh-contact could work with any protocol if its telepathy backend supports [[StreamTube|StreamTube]]. + + +## Why some of my contacts are not listed in ssh-contact menu? + +Only contacts with ssh-contact service installed and connected using telepathy are listed + + +## Is there security risks? + +If you install the ssh-contact service, your ssh daemon is exposed to all your IM contacts. Of course they still have to make the ssh authentication (password, ssh key, etc). This means that your sshd is not "protected" anymore behind a NAT or firewall. It is equivalent to have ssh daemon running with a public IP address and port 22 open. So ssh-contact-service security == sshd security. It is your choice to trust sshd or not. |