Nick Bolton

Synergy 1.7.3 released

65 posts in this topic

Hello, I'd like to announce the release of Synergy 1.7.3. » [url=http://synergy-project.org/download/]Download Synergy v1.7.3-stable[/url] This version fixes the major SSL bugs (see below for details). Version 1.7.4 is due in about a month ([url=https://github.com/synergy/synergy/milestones/v1.7.4-stable]track our progress[/url]). Here's the bug fixes: [list] [*]Bug [url=https://github.com/synergy/synergy/issues/4565]#4565[/url] - Incorrect plugin downloads on Debian and Mint[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4677]#4677[/url] - Windows service log file grows to very large size[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4651]#4651[/url] - High logging rate causes Windows service to crash[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4650]#4650[/url] - SSL error log message repeats excessively and freezes cursor[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4624]#4624[/url] - Runaway logging causes GUI to freeze[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4617]#4617[/url] - Windows service stops after 'ssl handshake failure' error[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4601]#4601[/url] - Large clipboard data with SSL causes 'protocol is shutdown' error[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4593]#4593[/url] - Locking Windows server causes SSL_ERROR_SSL to repeat[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4577]#4577[/url] - Memory leak in GUI on Windows caused by logging[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4538]#4538[/url] - Windows service crashes intermittently with no error[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4341]#4341[/url] - GUI freezes on first load when reading log[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4566]#4566[/url] - Client or server crashes with 'ssl handshake failure' error[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4706]#4706[/url] - Installer is not output to build config dir on Windows[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4704]#4704[/url] - Plugin 'ns' release build is replaced with debug build on Linux[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4703]#4703[/url] - Plugins are not built to config directory on Mac[/*:m] [*]Bug [url=https://github.com/synergy/synergy/issues/4697]#4697[/url] - Timing can allow an SSL socket to be used after cleanup call[/*:m][/list:u] And we also made some improvements: [list] [*]Enhancement [url=https://github.com/synergy/synergy/issues/4661]#4661[/url] - Log error but do not crash when failing to load plugins[/*:m] [*]Enhancement [url=https://github.com/synergy/synergy/issues/4708]#4708[/url] - Download ns plugin for specific Mac versions[/*:m] [*]Enhancement [url=https://github.com/synergy/synergy/issues/4587]#4587[/url] - Include OpenSSL binaries in source for easier building[/*:m] [*]Enhancement [url=https://github.com/synergy/synergy/issues/4695]#4695[/url] - Automatically upload plugins as Buildbot step[/*:m][/list:u] Thanks, Nick

Share this post


Link to post
Share on other sites
So I've installed 1.7.3-stable on Windows as a client and 1.7.3-stable under Debian as a server. The encryption settings are different. Windows speaks of a certificate. Linux speaks of a password / PSK. [quote]What do I do? [/quote] Ha, resolved. I quit the upgraded server instance and restarted it & it asked for my "pro" credentials, and after logging in on that the server supported certs. Nice that the fingerprint is /just/ visible in the server GUI. Very simple fingerprint validation. Nice work guys.

Share this post


Link to post
Share on other sites
Sorry but this installation executable is so annoying ... what's the point of using Synergy if the install cannot update the software without me having to shut it down, manually switch the keyboard/mouse cables (because the client is no longer running) and install it on each machine? And still getting this annoying error message that the service couldn't be installed and that I should check my user privileges. Then after the first failed install, of course the synergy service is marked for deletion and I have to manually edit the registry entries to get it back (no I absolutely cannot restart the machine as it is running calculation for days at a time). Here's what the installation executable should do: 1.) stop the synergy service 2.) update all files 3.) restart the synergy service come on, virtually every piece of software out there does this without any issue. It is really that much to ask for?

Share this post


Link to post
Share on other sites
Hello, Great job on the new update! Version 1.7.2 never worked for me. I waited for the update and 1.7.3 works like a champ. Everything installed smoothly and up and running within minutes. You guys rock!

Share this post


Link to post
Share on other sites
I did notice that when i installed and registered my 1.7.3 release on my PC and Mac to sync the two, the mouse works great! not jumpy which is GREAT! but I did notice that the keyboard does not carry over from my Mac to PC.

Share this post


Link to post
Share on other sites
Tried installing 1.7.3 - Server is windows 7 -54bit client is redhat - 64 bit. Cannot have different versions talk to one another - ok - kinda expected that looking at the changes. Windows seems to install fine. Linus compains it cannot figure out what version of linux is running. When I run it i get the following: ERROR: error:140C5042:SSL routines:SSL_UNDEFINED_FUNCTION:called a function you should not call ERROR: failed to accept secure socket INFO: accepted secure socket NOTE: disconnected from server NOTE: stopped client So - bad things. 1.7.2 has issues with connections, 1.7.3 doesn't run. Next version please...

Share this post


Link to post
Share on other sites
[quote="mike laforet"]I did notice that when i installed and registered my 1.7.3 release on my PC and Mac to sync the two, the mouse works great! not jumpy which is GREAT! but I did notice that the keyboard does not carry over from my Mac to PC.[/quote] I had the same problem. Keyboard and mouse worked fine on the Mac (the Synergy server), and the mouse moved to the Windows client as expected, but when I typed on the keyboard the characters went into the active window on the Mac. Rebooting Windows did not help, but rebooting the Mac did -- all is well now.

Share this post


Link to post
Share on other sites
NON SSL is working now, however cannot get any of the SSL functions up and working. Windows 7 32bit Synergy 1.7.3 server OS X 10.10 Synergy 1.7.3 client Windows 7 32bit Synergy 1.7.3 client I'll post details in a different post, rather than addressing them all here.

Share this post


Link to post
Share on other sites
Got 1.7.3 working between two Linux Mint 17.1 computers. After some trial and error I found that before you upgrade / install 1.7.3, you have to remove the .synergy directory on all systems. Then configure and you can turn on SSL and it works.

Share this post


Link to post
Share on other sites
Downloaded newest version to both PC and MAC. Got the PC connected to server (MAC), after rebooting, and disarming the SSL settings. However, the MAC is still totally unresponsive. Here's the last error message: ERROR: failed to load plugin 'libns.dylib', error: dlopen(/Users/carolroberts/Library/Synergy/Plugins/libns.dylib, 1): Library not loaded: /usr/lib/libcurl.4.dylib Referenced from: /Users/carolroberts/Library/Synergy/Plugins/libns.dylib Reason: Incompatible library version: libns.dylib requires version 7.0.0 or later, but libcurl.4.dylib provides version 6.0.0 NOTE: started server, waiting for clients NOTE: accepted client connection NOTE: client "Carol-HP" has connected I'm about ready to delete your whole program as this has been a nightmare.

Share this post


Link to post
Share on other sites
I'm on Mint 17.1 and 1.7.3 solved all the issues I was having...I might have to give you guys another $10 :-)

Share this post


Link to post
Share on other sites
1.7.3 fixed all the issues I was having, but now I find that it is using 25% CPU resources (server side) and 33% on the client side. Both are running win 8.1 64.

Share this post


Link to post
Share on other sites
[quote="Greg Kaurin"]1.7.3 fixed all the issues I was having, but now I find that it is using 25% CPU resources (server side) and 33% on the client side. Both are running win 8.1 64.[/quote] I'm having the exact same issue on the server (a full core being used, 25% of total), but i'm on Win 7 64. My client isn't having any significant utilization, but it's still on 1.6.2 on a BSD OS installed from ports.

Share this post


Link to post
Share on other sites
I am now having trouble with the mouse on the second screen. It's really hard to move around. I guess I will go back to the previous which was working fine for me.

Share this post


Link to post
Share on other sites
Just installed synergy on windows XP server and windows 7 client. Neither will talk to each other. 1.7.2 worked fine. Server says: ERROR: ssl error occurred (system call failure) ERROR: eof violates ssl protocol ERROR: failed to accept secure socket INFO: client connection may not be secure NOTE: accepted client connection ERROR: ssl error occurred (system call failure) ERROR: eof violates ssl protocol ERROR: failed to accept secure socket INFO: client connection may not be secure NOTE: accepted client connection

Share this post


Link to post
Share on other sites
Small update: Make sure not to skip the wizard and run it through to completion. There are differences between the pre-1.7.3 plugins and the 1.7.3 plugins as well as a few differences in the locations of parts of the plugin structure. The wizard builds the correct file setup, and the new plugin needs to be downloaded. We're working on having the SSL plugin delivered via the install process rather than the wizard, but it didn't make the cut for 1.7.3 release. This will only ensure that a given executable will have the correct plugin version, but not ensure that the server/client(s) relationship will be compatible. And as a small addition, Errors that look like this: error:140C5042:SSL routines:SSL_UNDEFINED_FUNCTION:called a function you should not cal are errors we receive from OpenSSL. If there is a significant version mismatch (usually a very old OpenSSL), it's possible that it doesn't support some routine we use from the more modern OpenSSL. That's not to say there isn't an issue on the synergy end, but it's a place to check to make sure the SSL presently on the system is modern.

Share this post


Link to post
Share on other sites
I had installed 1.7.2, but had a lot of issues and for unclear reasons sometimes it worked and sometimes it did not. I got a lot of "connection timed out" error messages. I did multiple uninstalls, manual removing remaining register entries and directories (the uninstall does not really do a full uninstall, already discovered that with prior upgrades). When 1.7.3 came out I was happy since it mentioned solving a lot of problems I was having as well. Unfortunately 1.7.3 does not change the situation. I still have mostly error messages, connections dropping etc. Also strange behavior that despite having Synergy Pro and having registered, after a reboot both server and client side again are UNREGISTERED. Tried many things, with SSL, DEBUG 1, DEBUG 2, without SSL, trying to find out if anything is being blocked, all without success. I have done about 4 upgrades with Synergy, and all of them have had the same issues of Synergy no longer working and a lot of trial and error. The prior 3 times in the end I was able to resolve it (often unclear why or what changed). This time I am not so lucky, and I have given up. Major lesson learned for me is to not upgrade Synergy. I really like Synergy and it is very practical in my setup, but the upgrades are very bad and painful. Quite unfortunate.

Share this post


Link to post
Share on other sites
Yesterday I upgraded a Windows XP Pro system from 1.7.2 to 1.7.3 of synergy. This system is being used as a Synergy client. Right away I had to disable SSL to get it to connect to my Windows 8.1 system that is the Synergy server. Later on in the day I rebooted the XP system and when it came back up the security settings/software were such that it could no longer join the Domain. Our domain is a Windows 2012 Server based active directory domain. Not initially suspecting Synergy, I spent a lot of time trying other corrections without luck. This morning I restored the system to the restore point just before the Synergy 1.7.3 installation and everything is working fine. I wasn't having any problems with the 1.7.2 system, so I'm not in a hurry to upgrade. However, I would like to keep current with the software in the long run. Any suggestions on what 1.7.3 did and how to troubleshoot it?

Share this post


Link to post
Share on other sites
Uninstalled this mess! Upgraded when 1.7.3 was published..It's eating CPU cycles like no tomorrow..that's the cause of the unresponsive mouse issue. I can't work if my PC acts like an Intel 386 machine..Hello, the Eighties called, they want their CPU back! :evil:

Share this post


Link to post
Share on other sites
Upgraded to 1.7.3 after 1.7.2 was just a bit flaky on two Win7-64 boxes. Now, ONLY "failed to accept secure socket" and "ssl error occurred (system call failure)" and no function at all with gobs of SSL errors. I restarted both systems and got this yet again... "ERROR: failed to init synwinhk.dll, another program may be using it INFO: restarting your computer may solve this error FATAL: failed to start server: unable to open screen ERROR: failed to launch, error: process immediately stopped" This should not be rocket science... ...and did a repair reinstall twice, uninstalled and started again. "ERROR: failed to verify server certificate fingerprint activeDesktop:Default ERROR: passive ssl error limit exceeded: 100001 ERROR: failed to connect secure socket Is now working WITHOUT SSL, which is REQUIRED here. What am I doing wrong? Edited by Guest

Share this post


Link to post
Share on other sites
I have the same issue, although my setup will work for a while, then crash, then trying to reboot, I get the same error as Ira above regarding the synwinhk.dll. Any ideas on how to fix this without having to restart the computer?

Share this post


Link to post
Share on other sites
On Win8 64-bit running 1.7.2 Server, I ran the 1.7.3 installer. All fine (it complained about a file being in use by Sublime Text of all things), but at the end I got 'Error: Failed to download plugin 'ns'... '. In the end I clicked 'Finish', and Synergy restarted quite happily and the clients reconnected. I've no idea if this 'ns' plugin is required, whether it will be downloaded next time Synergy starts, etc. Seems like people have many different experiences with the upgrade process...

Share this post


Link to post
Share on other sites
... and the same thing happened on a Win8 64-bit 1.7.2 client. The exact text is: Error: Failed to download plugin 'ns' to C:\Users\davidl\AppData\Local\Synergy\Plugins The process cannot access the file because it is being used by another process. I'm assuming that's because Synergy is running - although it does seem to disconnect momentarily during the upgrade, it reconnects almost immediately, _before_ that error (i.e. at the end of the install and before the wizard). After all that, I clicked 'Finish', as before, and this time the GUI froze. I was still connected to the client though, and the rest of the machine was fine. After a few seconds of unresponsiveness, the GUI sprang back to life, with the slightly comical warning at the top saying that my version of Synergy (which is 1.7.3) was out of date, and that 1.7.3 was available for download. Huh? I checked under Help-About, and it confirms version 1.7.3. So, is that due to the failed 'ns' plugin? Or something else?

Share this post


Link to post
Share on other sites
[quote="speaker"]...OpenSSL. If there is a significant version mismatch (usually a very old OpenSSL), it's possible that it doesn't support some routine we use from the more modern OpenSSL. ... [b][u]check to make sure the SSL presently on the system is modern[/u][/b].[/quote] How do we do that, exactly? Specifically on Win7...

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.