Is there any way you can add barrier-2.3.3 back into portage? I am having the following issue https://github.com/debauchee/barrier/issues/1489 where barrier is now unusable now that I upgraded to the only version in gentoo (2.4.0). I added the ebuild introduced in https://bugs.gentoo.org/show_bug.cgi?id=736814 and put that in an overlay. Could you just add that back to portage?
I don't think I should. Older versions had a serious vulnerability, where malicious clients could connect. Security was tightened up in 2.4.0, and this may be why you're having trouble. I had a little trouble with the update, but I'm afraid I've forgotten the specifics. I figured it would be easier for people using the GUI. If you're not using the GUI, I think you have to manually add fingerprints to ~/.local/share/barrier/SSL/Fingerprints/TrustedClients.txt on the server side. It sounds like your client isn't presenting a certificate at all though. Try starting from scratch? On a related note, there is a new upstream and project name at https://github.com/input-leap/input-leap, but they haven't done any new releases yet.
When I run the server using the GUI it works...but it uses the option --no-client-cert-checking, which explains why it works. When you use 2.4.0, are you disabling client cert checking? jharvell 1128233 1128197 1 15:44 ? 00:00:01 /usr/bin/barriers -f --no-tray --debug INFO --name wolfhound --disable-client-cert-checking -c /tmp/Barrier.gXHvpl --address :24800 jharvell@wolfhound package.mask$ cat /tmp/Barrier.gXHvpl section: screens wolfhound: halfDuplexCapsLock = false halfDuplexNumLock = false halfDuplexScrollLock = false xtestIsXineramaUnaware = false preserveFocus = false switchCorners = none switchCornerSize = 0 aln-jharvell: halfDuplexCapsLock = false halfDuplexNumLock = false halfDuplexScrollLock = false xtestIsXineramaUnaware = false preserveFocus = false switchCorners = none switchCornerSize = 0 end section: aliases end section: links wolfhound: right = aln-jharvell aln-jharvell: left = wolfhound end section: options relativeMouseMoves = false screenSaverSync = true win32KeepForeground = false clipboardSharing = true switchCorners = none switchCornerSize = 0 end
I forgot to say in the previous comment that it refers to barrier-2.4.0.
I resolved the issue I was having with 2.4.0 and updated how I resolved it in https://github.com/debauchee/barrier/issues/1489. Please close as WONT FIX. Thanks.