[GH-ISSUE #171] no option for fingerprint #138

Closed
opened 2026-05-05 05:21:40 -06:00 by gitea-mirror · 7 comments
Owner

Originally created by @mathse on GitHub (Nov 7, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/171

Operating Systems

Server: windows 10

Client: Ubuntu 18.04

Barrier Version

2.1.0

Steps to reproduce bug

  1. ./barrierc -f --enable-crypto hostname.of.server

[2018-11-07T15:20:47] NOTE: started client
[2018-11-07T15:20:47] NOTE: connecting to 'hostname.of.server': 10.10.10.10.:24800
[2018-11-07T15:20:47] INFO: OpenSSL 1.1.0g 2 Nov 2017
[2018-11-07T15:20:47] NOTE: server fingerprint: B8:5F:6D:DC:17:43:59:7C:80:04:DA:14:69:81:5D:02:BA:BD:XX:XX
[2018-11-07T15:20:47] ERROR: failed to verify server certificate fingerprint
[2018-11-07T15:20:54] NOTE: stopped client

Problem

there is now way (documented) to tell barrier which fingerprint to use

Originally created by @mathse on GitHub (Nov 7, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/171 ### Operating Systems ### Server: windows 10 Client: Ubuntu 18.04 ### Barrier Version ### 2.1.0 ### Steps to reproduce bug ### 1. ./barrierc -f --enable-crypto hostname.of.server [2018-11-07T15:20:47] NOTE: started client [2018-11-07T15:20:47] NOTE: connecting to 'hostname.of.server': 10.10.10.10.:24800 [2018-11-07T15:20:47] INFO: OpenSSL 1.1.0g 2 Nov 2017 [2018-11-07T15:20:47] NOTE: server fingerprint: B8:5F:6D:DC:17:43:59:7C:80:04:DA:14:69:81:5D:02:BA:BD:XX:XX [2018-11-07T15:20:47] ERROR: failed to verify server certificate fingerprint [2018-11-07T15:20:54] NOTE: stopped client ### Problem there is now way (documented) to tell barrier which fingerprint to use
Author
Owner

@AdrianKoshka commented on GitHub (Nov 8, 2018):

This should help: https://wiki.archlinux.org/index.php/Synergy#Clients_configuration

<!-- gh-comment-id:436832287 --> @AdrianKoshka commented on GitHub (Nov 8, 2018): This should help: https://wiki.archlinux.org/index.php/Synergy#Clients_configuration
Author
Owner

@mathse commented on GitHub (Nov 8, 2018):

no, doesn't really help
tried ~/.synergy and ~/.barrier folder

<!-- gh-comment-id:436926366 --> @mathse commented on GitHub (Nov 8, 2018): no, doesn't really help tried ~/.synergy and ~/.barrier folder
Author
Owner

@AdrianKoshka commented on GitHub (Nov 8, 2018):

I think it's ~/.config/barrier? I know these instructions work because I've used them before.

<!-- gh-comment-id:437098031 --> @AdrianKoshka commented on GitHub (Nov 8, 2018): I think it's `~/.config/barrier`? I know these instructions work because I've used them before.
Author
Owner

@mathse commented on GitHub (Nov 9, 2018):

I think it's ~/.config/barrier? I know these instructions work because I've used them before.

could you provide a "tree -d ~/.config/barrier" ?

<!-- gh-comment-id:437388860 --> @mathse commented on GitHub (Nov 9, 2018): > I think it's `~/.config/barrier`? I know these instructions work because I've used them before. could you provide a "tree -d ~/.config/barrier" ?
Author
Owner

@AdrianKoshka commented on GitHub (Nov 10, 2018):

Sadly no, I don't have barrier setup anymore.

<!-- gh-comment-id:437559869 --> @AdrianKoshka commented on GitHub (Nov 10, 2018): Sadly no, I don't have barrier setup anymore.
Author
Owner

@dayne commented on GitHub (Dec 2, 2018):

Ubuntu client:

.config/barrier
└── SSL
    ├── Barrier.pem
    └── Fingerprints
        ├── Local.txt
        └── TrustedServers.txt

The TrustedServers.txt is a single line with the SSL Fingerprint of the Windows Server running barrier.

<!-- gh-comment-id:443486633 --> @dayne commented on GitHub (Dec 2, 2018): Ubuntu client: ``` .config/barrier └── SSL ├── Barrier.pem └── Fingerprints ├── Local.txt └── TrustedServers.txt ``` The TrustedServers.txt is a single line with the SSL Fingerprint of the Windows Server running barrier.
Author
Owner

@mathse commented on GitHub (Dec 4, 2018):

Yep this works

~/.config/barrier
└── SSL
├── Barrier.pem
└── Fingerprints
├── Local.txt
└── TrustedServers.txt

<!-- gh-comment-id:444097627 --> @mathse commented on GitHub (Dec 4, 2018): Yep this works ~/.config/barrier └── SSL ├── Barrier.pem └── Fingerprints ├── Local.txt └── TrustedServers.txt
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#138
No description provided.