Open the class and use Ctrl + O to show/hide inherited methods.

I Did NOT have this problem when my Synergy Server was on Windows. When I switched my Synergy Server to my Red Hat Linux box, I noticed my Back/Forward mouse buttons didn’t work.

After searching around for a bit, adding the following lines to your synergy.conf file fixed this.

$ sudo vi /etc/synergy.conf

section: options
  mousebutton(6) = keystroke(WWWBack)
  mousebutton(7) = keystroke(WWWForward)
  mousebutton(4) = ;
  mousebutton(5) = ;
end

So with my current setup (sk-win7 <-> sk-redhat <-> sk-ubuntu) with sk-redhat being my Synergy Server, my /etc/synergy.conf looks like:

section: screens
  sk-redhat:
  sk-win7:
  sk-ubuntu:
end

section: aliases
  sk-win7:
  10.4.1.1
end

section: links
  sk-redhat:
    left = sk-win7
    right = sk-ubuntu
  sk-win7:
    right = sk-redhat
  sk-ubuntu:
    left = sk-redhat
end

section: options
  mousebutton(6) = keystroke(WWWBack)
  mousebutton(7) = keystroke(WWWForward)
  mousebutton(4) = ;
  mousebutton(5) = ;
end

After adding this section, I was able to get my mouse back/forward buttons to work on all of my boxes.

The below example will demonstrate how shivdev@sk-optiplex can SSH to shivdev@sk-redhat without a password. The idea is to create SSH (public/private) keys on sk-optiplex and then copy the public key /home/shivdev/.ssh/id_dsa.pub from sk-optiplex over to sk-redhat as ./ssh/authorized_keys2.

I’m using SSH 2 with DSA encryption, because I just couldn’t get SSH with RSA encryption to work.

shivdev@sk-optiplex:~$ ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/home/shivdev/.ssh/id_dsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/shivdev/.ssh/id_dsa.
Your public key has been saved in /home/shivdev/.ssh/id_dsa.pub.
The key fingerprint is:
73:4a:b1:d3:d6:3c:fc:ed:c7:c6:61:18:0f:fb:06:6b shivdev@sk-optiplex
The key’s randomart image is:
+–[ DSA 1024]—-+
| |
| |
| . |
| + + o |
| S + = * |
| . * * = |
| . *oo|
| E +=|
| . ..o|
+—————–+
shivdev@sk-optiplex:~$ scp /home/shivdev/.ssh/id_dsa.pub shivdev@sk-redhat:.ssh/authorized_keys2
The authenticity of host ‘sk-redhat (sk-redhat)’ can’t be established.
RSA key fingerprint is b4:3a:15:5d:cb:5d:7e:05:39:35:0d:9c:1f:d4:84:08.
Are you sure you want to continue connecting (yes/no)? yes
Failed to add the host to the list of known hosts (/home/shivdev/.ssh/known_hosts).
shivdev@sk-redhat’s password:
id_dsa.pub 100% 610 0.6KB/s 00:00
shivdev@sk-optiplex:~$ ssh shivdev@sk-redhat
The authenticity of host ‘sk-redhat (sk-redhat)’ can’t be established.
RSA key fingerprint is b4:3a:15:5d:cb:5d:7e:05:39:35:0d:9c:1f:d4:84:08.
Are you sure you want to continue connecting (yes/no)? yes
Failed to add the host to the list of known hosts (/home/shivdev/.ssh/known_hosts).
Last login: Thu May 17 14:48:01 2012 from 10.4.21.184
[shivdev@sk-redhat ~]$

As you can see after copying over the public key from shivdev@sk-optiplex:.ssh/id_dsa.pub over to shivdev@sk-redhat:.ssh/authorized_keys2, shivdev@sk-optiplex is able to SSH into shivdev@sk-redhat without a password.

If you do get this error “Agent admitted failure to sign using the key.”, then you might need to run ssh-add or logout of the terminal and try to login again.

shivdev@sk-optiplex:~$ ssh shivdev@sk-redhat
Agent admitted failure to sign using the key.
shivdev@sk_redhat’s password:

shivdev@sk-optiplex:~$ ssh-add

shivdev@sk-optiplex:~$ ssh shivdev@sk-redhat
Last login: Thu May 17 14:51:01 2012 from 10.4.21.184
[shivdev@sk-redhat ~]$