New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSL Linux Client #142
Comments
Apparently this bug is caused when one side has SSL enabled but the other doesn't. |
I'll close this, feel free to open it again if it doesn't solve the problem. |
No, we have tried it with an without SSL, on both sides--client and server. |
It is Windows Firewall problem, just had same issue and you need to add rule to Allow program - barriers.exe. Having just barrier.exe as allowed is not enough. |
I am glad you mentioned that; when I went to add the program to the exception, it was already there but had the name "Open Source KVM software" |
Operating Systems
Server: Windows 10
Client: Ubuntu 16.04.4 LTS
Barrier Version
2.2.0-snapshot-53ebc47a (client I am using)
Steps to reproduce bug
READ ME, DELETE ME: Try to be succinct. If your bug is intermittent, try and describe what you're doing when it happens most.
Other info
So it works when I use Ubuntu as the server and connect a Windows 10 client to it. However, it stops working when I connect a Windows barrier server to the Linux client. I have also tried removing the SSL fingerprints folder and PEM file entirely at ~/.local/share/barrier/SSL/Barrier.pem and ~/.local/share/barrier/SSL/FingerPrints/ . I have also tried making sure OpenSSL (through apt repository) is up-to-date, and python/python3 openssl package. I have tried doing it both unencrypted and encrypted.
I ran "sudo tcpdump -i wlo1 'port 24800'" and saw absolutely nothing encrypted, it was all plaintext. I have also tried running as root.
I'm running on a Ubuntu Live Disk, if that helps any. I've ran several commands, just trying to get it to work, so I figure it might help out understanding how I built the software. Here's the link: http://paste.debian.net/1045806/ .
The text was updated successfully, but these errors were encountered: