[GH-ISSUE #897] Compare server fingerprint - but how? #717

New issue

Open

opened 2026-05-05 06:59:15 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:59:15 -06:00

Owner

Originally created by @ccoenen on GitHub (Oct 3, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/897

When I connect a new client, it asks me to verify the server fingerprint. I would love to do so, but I do not see any way to actually accomplish that. The SSL Fingerprint field in the gui is empty despite SSL being enabled.

To Reproduce

Steps to reproduce the behavior:

Install Barrier 2.3.3 from github's releases page
Open
see screenshot as above

Expected behavior
Have a fingerprint visible.

Desktop (please complete the following information):

OS: Windows 10
Barrier version: 2.3.3

Additional context

On this machine, I had Synergy installed previously, maybe that interferes somehow?

Originally created by @ccoenen on GitHub (Oct 3, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/897 When I connect a new client, it asks me to verify the server fingerprint. I would love to do so, but I do not see any way to actually accomplish that. The `SSL Fingerprint` field in the gui is empty despite SSL being enabled. ![empty SSL fingerprint label](https://user-images.githubusercontent.com/124909/94987041-b7e3e880-0563-11eb-9093-e9246558a7cd.png) ![SSL is turned on](https://user-images.githubusercontent.com/124909/94987115-10b38100-0564-11eb-97ae-f93f0004fd08.png) **To Reproduce** Steps to reproduce the behavior: 1. Install Barrier 2.3.3 from github's releases page 2. Open 3. see screenshot as above **Expected behavior** Have a fingerprint visible. **Desktop (please complete the following information):** - OS: Windows 10 - Barrier version: 2.3.3 **Additional context** On this machine, I had Synergy installed previously, maybe that interferes somehow?

gitea-mirror commented

2026-05-05 06:59:19 -06:00

Author

Owner

@Ashark commented on GitHub (Oct 4, 2020):

I was going to file exactly this bug.
As I remember, there was not a possibility to see server's fingerprint even at times when this fork was not existent, I mean when I used synergy.

@Ashark commented on GitHub (Oct 4, 2020): I was going to file exactly this bug. As I remember, there was not a possibility to see server's fingerprint even at times when this fork was not existent, I mean when I used synergy.

gitea-mirror commented

2026-05-05 06:59:22 -06:00

Author

Owner

@Ashark commented on GitHub (Oct 4, 2020):

I have found a place where it can be checked: $HOME/.local/share/barrier/SSL/Local.txt
I think that should go to readme. And even better, be able to check it from application gui.

Edit: Also, it may be in another location. So to see the current fingerprint, you may run
cat ~/.local/share/barrier/SSL/Fingerprints/Local.txt

@Ashark commented on GitHub (Oct 4, 2020): I have found a place where it can be checked: $HOME/.local/share/barrier/SSL/Local.txt I think that should go to readme. And even better, be able to check it from application gui. Edit: Also, it may be in another location. So to see the current fingerprint, you may run `cat ~/.local/share/barrier/SSL/Fingerprints/Local.txt`

gitea-mirror commented

2026-05-05 06:59:24 -06:00

Author

Owner

@Ashark commented on GitHub (Nov 14, 2020):

And even better, be able to check it from application gui.

I have completely missed the fact, that GUI already has the field for that! As seen at the first screenshot.

@Ashark commented on GitHub (Nov 14, 2020): > And even better, be able to check it from application gui. I have completely missed the fact, that GUI already has the field for that! As seen at the first screenshot.