Barrier doesn't exchange SSL certificates

[halfbeing]

Barrier version 2.4.0 doesn't exchange SSL certificates, which means that mouse and keyboard sharing simply don't work. This is true across all platforms. Connecting Mac to Windows, Windows to Mac, Mac to Linux, Windows to Linux, Windows to Windows, Linux to Windows, Linux to Mac, it is the same problem. Discussions on github indicate that this problem has remained unresolved, with no software update for almost a year. Barrier looks very much like abandonware and really needs to be removed from the Snap repository so that other people don't end up wasting as much time as I have wasted this evening trying to get it to work.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: barrier 2.4.0+dfsg-2
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 30 02:40:24 2022
InstallationDate: Installed on 2022-05-18 (164 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: barrier
UpgradeStatus: No upgrade log present (probably fresh install)

[halfbeing (halfbeing)]

I'm sorry. I now realise that I made a mistake while trying to execute a workaround due to a clumsy copy-paste, causing it to fail. So while this bug is still real, it is not fatal. Barrier can still be made to work.

The workaround is to execute the command

openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem

in the Barrier SSL folder on the Barrier server, and then to restart the Barrier service using the Barrier interface on the server. I did this in MacOS, but I believe that the exact same command will work for Ubuntu, except that the path to the Barrier SSL folder will be different.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Eddie (pixhix)]

I spent an hour or more on solving this Barrier KVM software SSL doesn't exist error.
Will save you and probably me an hour when I run into this same problem again in a year.

Just got Barrier working on OSX Sonoma v14.0 thanks to the above comment. Thanks!

1) I found my SSL folder here on the Barrier Server (mine happens to be a Mac):
/Users/YOUR USERNAME/Library/Application Support/Barrier/SSL
note: on the Barrier client click Show Log you will see in the log the folder the Barrier client is looking for on the Barrier Server for the SSL certificate

    I had both the server and client running and was getting the SSL certificate doesn't exist error

2) open terminal window on OSX (this will probably work on other OS, but I did this on 2 macBook Pro)

3) cd to the SSL directory above

4) cut this line
openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem

5) paste the line into the terminal window (while you are cd into the SSL folder)

6) it creates the SSL certificate in the correct folder that the Barrier clent is looking for

7) the Barrier client now sees the newly created certificate and asks you to confirm. Do you trust this fingerprint? SHA256: click Yes if you trust this SSL cert. It should match the cert on your system that is the Barrier server

8) Barrier works !!

I downloaded Barrier from this location https://github.com/debauchee/barrier/releases/tag/v2.4.0 scroll down to ASSETS and click the dmg

Treason I got into this was because I use old Mac hardware which I have upgraded w max memory and fast 1TB or 2TB SSL hard drives. I install OpenCore Legacy Patcher to be able to give new life to my old Macs and can then upgrade to the latest OSX. The downside for me was after successfully upgrading 4 systems in the last 10 months multiple times to new OCLP and the latest OSX flawlessly, I had a failure on my mid 2020 iMac 27" the only fix was a clean reinstall. Previously, using an older KVM software called Teleport and I could not get Teleport installed after trying several times, something to do with OSX Sonoma. Therefore the hunt for a newer KVM software and found Synergy then Barrier and also maybe in the future will use Input-Leap when it is ready and released. The good news is that Barrier is faster and smoother than Teleport.

So ... I can verify Barrier works well between old 15" Macbook Pro mid 2020 w OpenCore Legacy Patcher v1.0.1 and Sonoma OSX v14.0 as a barrier server and as the client a 13" early 2011 MacBook Pro w OpenCore Legacy Patcher v1.0.1 and OSX Sanoma 14.0 and another Barrier client mid 2020 iMAC 27" OCLP v1.0.1 running Sanoma v14.0

a lot of info but hope it helps at least 1