Talk:Input Leap

Synergy 1.7+ SSL encryption

Synergy 1.7+ replaces the existing crypto with an SSL transport plugin, according to http://synergy-project.org/wiki/Security. This is automatically configured for Synergy Pro users using the GUI, but can be compiled from source and installed manually for free. Might be worth touching on this in the encryption section, which is now outdated. Wlritchi (talk) 06:24, 3 June 2015 (UTC)

Update to Synergy 2.0

Fedora 26 is now on Synergy 2.0 - it breaks existing configurations/autostart/etc - so likely we're going to have to update the article very soon. :-| Zatricky (talk) 05:44, 8 February 2018 (UTC)

• Pulec (talk) 21:31, 1 July 2018 (UTC): There is synergy2 binary https://aur.archlinux.org/packages/synergy2-bin, didn't tried it though, I am up for testing it and adding a section about config comability, someone could explain the legal level... and alternatives. BTW I am sure you can somehow get older RPM for Fedora and keep ideally same version pkgs. There is no reason for stop using synergy1 as long as its working.

Significantly, though synergyc and synergys are provided, they both refer to using synergy-core --client and synergy-core --server instead. Zatricky (talk) 05:51, 8 February 2018 (UTC)

A tip about keystrokes, should be OS agnostic, not sure where to put it

Default way for switching between clients is to go over the edge with mouse pointer (perhaps redundant point), for switching clients using keyboard only, there is a posibility for using hotkeys (keystrokes) like:

(is there way how to make nice shift key and such?)

• Win+` for switching to client on the right
• Win+Shift+` for switching to client on the left

Add following section called options (if you don't already have one) and define keystroke with switchInDirection argument

 section: options
         keystroke(Super+`) = switchInDirection(right)
         keystroke(Super+Shift+`) = switchInDirection(left)
 end

(not sure how to remove the indent)

Change Fingerprint path and Describe the compatibility between Barrier and Synergy

• Troubleshooting fingerprint trust on Barrier
• synergy uses the Hello string Synergy%2i%2i, whereas barrier expects Barrier%2i%2i

Pulec (talk) 21:27, 1 July 2018 (UTC)

Update to Barrier 2.4.0

After upgrade to v2.4.0 (2021-11-04), a connection stopped working, returning the following on the output:

[2021-xx-xxTxx:xx:xx] INFO: --enable-crypto is used by default. The option is deprecated.
...
[2021-xx-xxTxx:xx:xx] NOTE: peer fingerprint (SHA1): RL:27:5A:R1:EE:51:FA:70:LF:6B:22:DD:21:35:70:31:D1:27:FA:LE (SHA256): AE:0E:62:27:06:25:R3:72:F1:16:RB:ER:R0:32:LB:1F:03:EE:A2:FL:20:1L:A2:RL:FE:6F:R1:2F:7E:2R:61:52
[2021-xx-xxTxx:xx:xx] NOTE: fingerprint_db_path: /home/$USER/.local/share/barrier/SSL/Fingerprints/TrustedClients.txt
[2021-xx-xxTxx:xx:xx] NOTE: Could not read fingerprints from: /home/$USER/.local/share/barrier/SSL/Fingerprints/TrustedClients.txt
[2021-xx-xxTxx:xx:xx] NOTE: Fingerprint does not match trusted fingerprint
[2021-xx-xxTxx:xx:xx] ERROR: failed to verify server certificate fingerprint

The first one --enable-crypto is clear enough, ain't needed anymore.

The remainder, well after some more digging I was able to find:

New file TrustedClients.txt is required on the server.

Also the format of Local.txt and the new TrustedClients.txt has changed. I was only able to figure out the new SHA256 form: v2:sha256:YO:UR:ST:RI:NG. I have no idea how the SHA1 form would look like, I've tried v1:sha1:... or v2:sha1:..., but that doesn't work.

Meaning, both Local.txt and the new TrustedClients.txt must change, and for the start, these SHA256 values can be taken from the output of server and client, or as I just tried and it worked:

Server (then copy to the Client into TrustedServers.txt):

$ openssl x509 -fingerprint -sha256 -noout -in ~/.local/share/barrier/SSL/Barrier.pem | sed -e "s/.*=/v2:sha256:/" > ~/.local/share/barrier/SSL/Fingerprints/Local.txt

Client (then copy to the Server into TrustedClients.txt):

$ openssl x509 -fingerprint -sha256 -noout -in ~/.local/share/barrier/SSL/Barrier.pem | sed -e "s/.*=/v2:sha256:/" > ~/.local/share/barrier/SSL/Fingerprints/Local.txt

Synergy 3

There is a whole new version of synergy in the AUR called synergy3-bin^AUR. I am going to make a section in the wiki while I try to figure out how to configure and daemonize the program. I am open to discussing maybe creating a synergy-3 package on the Official Repositories. Additionally, possibly re-name the synergy to synergy3? Because Barrier is its own thing but synergy is now synergy3 and the legacy should maybe be called synergy-legacy or synergy2. Any thoughts? Tsangares (talk) 22:23, 12 November 2023 (UTC)

I'd like to see an official synergy3 package. As I noted in a separate comment, the dependencies on the current AUR package do not seem correct or comprehensive and I don't have the time or packaging know-how at the moment to improve upon that PKGBUILD. Nalthien (talk) 17:55, 8 February 2024 (UTC)

New Page

I am going to start making a new wiki page later for just Synergy because it seems to have diverged a lot from the input-leap or barrier type of software. Tsangares (talk) 08:38, 12 December 2023 (UTC)

I came to the Talk page to make a similar note. The current state of things in this area is a mess. We have:

• Synergy which is now in the beta period of version 3, is closed source, and is completely incompatible with earlier versions. Effectively none of what's on this page currently is applicable to Synergy3. The AUR package is again maintained; but, the dependencies are not correct and I don't think the people packaging know what those dependencies should be. My first guess is that there are some Qt and KDE dependencies that the AUR packagers just assume are available everywhere; but, that's just a guess. There's a flatpak available which might make more sense for people right now.
• Barrier seems to be unmaintained since 2021.
• Input Leap seems maintained; but, the README still notes that it's not ready for any kind of release and people should default to using Barrier.

As it is now, the page itself is a mix of things that apply to older versions of Synergy and Barrier and the whole thing should probably be rewritten. Nalthien (talk) 17:48, 8 February 2024 (UTC)

Wayland & Other Tips

Instructions do not mention how to properly install input-leap, despite it being the name of the page. Despite the maintainers calling it alpha quality, it is probably the best option available, especially considering it is the only option that supports Wayland, and development has stopped on Barrier, with former Barrier developers moving to Input-Leap. It should be noted that Input-Leap is backwards compatible with Barrier as well, such that a linux server with input-leap can work fully with a Windows Client using Barrier.

Currently, for Wayland support, users must install input-leap-inputcapture, which contains the input capture patches necessary for Wayland, and KDE only supports this as of plasma 6.1. This solution is compatible with X11 for users who switch between sessions. This may be eventually merged into the main branch of input-leap-git.

Getting this to work on KDE was tracked in this issue and could provide troubleshooting steps: https://github.com/input-leap/input-leap/issues/1908

Users who want to start input-leap on boot without using a systemd service can configure autostart to use the (apparently undoucmented?) --start-in-tray flag.

I also think there should be a section on graphical configuration of clients since this is easier than writing your own text-based files. Benm (talk) 16:41, 8 July 2024 (UTC)

Completely agreed. I haven't gone through the history to see when it happened or why it happened; but, this page was originally the "Synergy" page. Someone renamed it to "Input Leap" without really doing any of the revisions that should be done for such a page.

I think the best thing to do, for now, is probably rename this page back to Synergy and create a new page for Input Leap. Nalthien (talk) 02:57, 13 July 2024 (UTC)