Barrier user experience
#1884
Replies: 1 comment
-
|
Writing this as I struggled to make it work for my laptop and pc, there was a change so it only checks sha256 fingerprints, but the wiki only describes how to add sha1 for trusted servers. The solution is to add the sha256 to the trusted servers file instead, but in this form: You can find the sha256 either in the client logs or using an openssl command that outputs sha256 instead of sha1. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I need to install barrier, I know from having used it 20 years ago that, when it works it works great.
And I know from having used it about a years ago, it's hell to install.
Now I need to use it for a new purpose and I've forgotten all about how to set it up again !
So I decided to document my user experience re-figuring it out and maybe that could help other people trying to set it up. And if someone is still working on this software they would know what needs fixing.
This is for a windows 10 barrier server and linux client running ubuntu 22.10
Installed 2.4 on window
got missing barrier.pem error
installed previous version, it works
added my client to the server config interactive editor
started putty, tried to connect with DISPLAY=:0 barrierc serverhostname.lan
console doesn't echo anymore,
a client connects (not even the name in log)
nothing happens
It might be wayland, disable wayland from my ubuntu 22.10 client
sudo nano /etc/gdm3/custom.conf
WaylandEnable=true
did not fix the problem
figure out new command line
barrierc --enable-crypto --display :0 --debug INFO -f serverhostname.lan
download this script wget https://gist.githubusercontent.com/dayne/e3a7f31f0624bf299faf9fadfe510322/raw/2c64b78c7abb4493d9fafee5f36032a6161b0e44/barrierc-trust.sh
using winscp
copy C:\Users\shodan\AppData\Local\Barrier\SSL\barrier.pem to /home/screen/.local/share/barrier/SSL/barrier.pem
fingerprint on the server
11:49:E7:BA:A0:7E:DC:64:33:D1:ED:60:4A:B7:21:53:A1:52:88:39
fingerprint on the client
11:49:E7:BA:A0:7E:DC:64:33:D1:ED:60:4A:B7:21:53:A1:52:88:39
[2023-01-25T02:31:44] NOTE: peer fingerprint (SHA1): 11:49:E7:BA:A0:7E:DC:64:33:D1:ED:60:4A:B7:21:53:A1:52:88:39 (SHA256): CC:F5:F6:79:B8:7D:5E:72:3B:4D:B8:30:A5:33:CD:0F:35:07:00:7D:25:C6:03:58:C4:79:E7:B1:F2:FF:27:38
bang head on wall
copy paste from logs 11:49:E7:BA:A0:7E:DC:64:33:D1:ED:60:4A:B7:21:53:A1:52:88:39 to trusted server file ?
ok time to make new certification files
openssl.exe found in C:\Program Files\Barrier
but can't run openssl there, ok
Ah, need to specify a config file
Oh, there isn't one, found one in gajim
oh wait, wrong syntax
Ok, still complains about the config file but works anyway ...
copy cert.pem (50/50 that it's key.pem I guess) to C:\Users\shodan\AppData\Local\Barrier\SSL
Restart server
Guess key.pem was the correct answer ...
Nope, the answer is neither
Ok, I probably did the openssl command wrong, time to search forum
Now I remember, when I last used this on the raspberry pi, I just disabled encryption, maybe it's impossible to make encryption work ?
it's getting late, maybe I should give up already
Maybe I should check out https://github.com/input-leap/input-leap
Ok new command to try , thank you @Desani #1674
openssl req -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pemor
D:\shodan\Documents\key\barrierkey>"C:\Program Files\Barrier\openssl.exe" req -config "C:\Program Files\Gajim\ssl\openssl.cnf" -x509 -nodes -days 365 -subj /CN=Barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pemWell, this looks promessing
client side
server side
running barrierc-trust.sh again
It seems barrier is now unmaintained and I'm running around in circles
input-leap/input-leap#1414
Ok, it doesn't work, can't install input-leap with apt,
I give up
Beta Was this translation helpful? Give feedback.
All reactions