joshskidmore
commented
2 years ago @ccoenen - I apologize for the delay in replying.
I unfortunately don't have a Windows machine to test, but I would still assume your issue is either around the SSL certificate and/or options being passed to the Barrier server or Waynergy client. I may be wrong, but I don't this this is related to your Windows OpenSSL versions. Though my Barrier server is in Linux, I thought I would share my options and configurations to see if there is something strikingly obvious.
(Linux) Barrier server:
/usr/bin/barriers \
--config ~/.barrier.conf \
--no-daemon \
--enable-crypto \
--disable-client-cert-checking \
--debug INFO- My
~/.barrier.conffile contains nothing related to SSL or encryption. - I have a combined OpenSSL key+certificate at
~/.local/share/barrier/SSL/Barrier.pem. I believe this was generated by Barrier at some point. - In the
~/.local/share/barrier/SSL/Fingerprints/Local.txtfile, I have two lines. The first starts withv2:sha1:and the second starts withv2:sha256:.
Waynergy client (also Linux)
/usr/bin/waynergy \
--loglevel 1 \
--host [IPV4_OF_ABOVE_BARRIER_SERVER] \
--name [NAME_OF_THIS_CLIENT_MACHINE_USED_IN_BARRIERS_CONFIG] \
--enable-crypto \
--enable-tofu \
--fatal-none- I have an keymap file at
~/.config/waynergy/xkb_keymap. - Waynergy automatically generated a subfolder at
~/.config/waynergy/tls/hash/, and automatically generated what appear to be OpenSSL SHA256 hashes of Barrier servers it connects to. I didn't do anything here; it generated these automatically.
Whenever the Waynergy client attempts to the Barrier server, occasionally it does throw an SSL connection/protocol error, but ends up connecting on the next retry.
ccoenen
The direct response to that is the server sending back the handshake-failure:
nonsleepr
What happened?
On the Wayland-Support ticket (#109) I reported this issue earlier, but it's a separate issue that only clutters that thread. Currently, my barrier on windows is in version 2.4.0 (current version at time of writing) and it seems to ship with OpenSSL 1.0.2l from 2017.
on my system, there would be a more recent openssl available, this is the one on the system's
PATH:But from within barrier, the shipped 1.0.2l seems to be used:
This leads to connection problems with waynergy compiled with a more recent openssl version (and therefore no matching ciphers, apparently). The connection attempts can be seen above.
(originally from https://github.com/debauchee/barrier/issues/109#issuecomment-1016539840, and I already tried the suggestions by @joshskidmore https://github.com/debauchee/barrier/issues/109#issuecomment-1016526113 and @brmnjsh https://github.com/debauchee/barrier/issues/109#issuecomment-1030988825 )
Version
v2.4.0
Git commit hash (if applicable)
3e0d758b
If applicable, where did you install Barrier from?
BarrierSetup-2.4.0-release.exefrom this project's release page.What OSes are you seeing the problem on? (Check all that apply)
Windows
What OS versions are you using?
Windows 10, Version 21H1 Build 19043.1466)
Relevant log output
Any other information
I am trying to connect a waynergy client (linux) to the barrier server (windows)