github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #227] synergy compatibility? #182

New issue

Closed

opened 2026-05-05 05:33:13 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 05:33:13 -06:00

Owner

Originally created by @brianjmurrell on GitHub (Jan 17, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/227

Did barrier lose compatibility with synergy somewhere along the line?

synergyc (2.0.0, protocol version 1.6) client reports:

[2019-01-16T23:21:26] WARNING: failed to connect to server: Protocol error from server, check encryption settings

when connecting to barrier 2.1.2

Originally created by @brianjmurrell on GitHub (Jan 17, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/227 Did barrier lose compatibility with synergy somewhere along the line? `synergyc` (2.0.0, protocol version 1.6) client reports: ``` [2019-01-16T23:21:26] WARNING: failed to connect to server: Protocol error from server, check encryption settings ``` when connecting to barrier 2.1.2

gitea-mirror closed this issue

2026-05-05 05:33:14 -06:00

gitea-mirror commented

2026-05-05 05:33:17 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Jan 17, 2019):

I think we did bump up the amount of bits our SSL certs use...

@AdrianKoshka commented on GitHub (Jan 17, 2019): I think we did bump up the amount of bits our SSL certs use...

gitea-mirror commented

2026-05-05 05:33:18 -06:00

Author

Owner

@mwilck commented on GitHub (Apr 16, 2020):

This happens even without encryption. AFAICS it occurs because the protocol is deliberately different. synergy uses the Hello string Synergy%2i%2i, whereas barrier expects Barrier%2i%2i.
This can be observed by running both server and client with -d DEBUG2.

@mwilck commented on GitHub (Apr 16, 2020): This happens even without encryption. AFAICS it occurs because the protocol is deliberately different. synergy uses the Hello string `Synergy%2i%2i`, whereas barrier expects `Barrier%2i%2i`. This can be observed by running both server and client with `-d DEBUG2`.

gitea-mirror commented

2026-05-05 05:33:21 -06:00

Author

Owner

@PaulAyling commented on GitHub (Apr 17, 2020):

I have the same issue - with SSL encryption turned off on both server and client. My server is running synergy 1.8.8 and client on barrier

@PaulAyling commented on GitHub (Apr 17, 2020): I have the same issue - with SSL encryption turned off on both server and client. My server is running synergy 1.8.8 and client on barrier

gitea-mirror commented

2026-05-05 05:33:22 -06:00

Author

Owner

@mwilck commented on GitHub (Apr 17, 2020):

I have the same issue - with SSL encryption turned off on both server and client. My server is running synergy 1.8.8 and client on barrier

That won't work, see above. You need to use either synergy or barrier on both sides.

@mwilck commented on GitHub (Apr 17, 2020): > I have the same issue - with SSL encryption turned off on both server and client. My server is running synergy 1.8.8 and client on barrier That won't work, see above. You need to use either synergy or barrier on both sides.

gitea-mirror commented

2026-05-05 05:33:24 -06:00

Author

Owner

@PaulAyling commented on GitHub (Apr 23, 2020):

Thanks Mwilck!. Installing and using barrier was very easy (I put it off as I didn't want to learn it) but it practially the same - although I had to turn of ssl

@PaulAyling commented on GitHub (Apr 23, 2020): Thanks Mwilck!. Installing and using barrier was very easy (I put it off as I didn't want to learn it) but it practially the same - although I had to turn of ssl

gitea-mirror commented

2026-05-05 05:33:26 -06:00

Author

Owner

@p12tic commented on GitHub (Jul 19, 2020):

Closing as the original question has been answered.

@p12tic commented on GitHub (Jul 19, 2020): Closing as the original question has been answered.