| Summary: | The synergy server connection is stopped several seconds after a synergy client has connected | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Alain Choucroot <choucroot> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, geiger.david68210, sysadmin-bugs |
| Version: | 5 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | http://www.mageialinux-online.org/forum/topic-22120+synergy-deconnexion-client-serveur-parametre-heartbeat.php | ||
| Whiteboard: | MGA5-64-OK, advisory | ||
| Source RPM: | synergy-1.5.0-3.mga5 synergy-gui-1.5.0-3.mga5 | CVE: | |
| Status comment: | |||
|
Description
Alain Choucroot
2016-05-09 15:28:13 CEST
Hi Alain, I just rebuild synergy against libcryptopp 5.6.3 on 5/Core/Updates_testing repo, could you test with this update if synergy now work properly? Thanks in advance! - synergy-1.5.0-3.1.mga5 - synergy-gui-1.5.0-3.1.mga5 CC:
(none) =>
geiger.david68210 ok, I reinstalled the updated packages [afb@localhost ~]$ rpm -qf `which synergy` synergy-gui-1.5.0-3.1.mga5 Then I relaunched synergy ( ensured the heartbeat parameter was commented ;-). I do claim that it works fine again ! Assigning to QA, Advisory: ============================= Many users have reported that synergy doesn't work properly anymore, due to a recurrent disconnection from a configured synergy server using the crypto-mode cfb, since a recent security update of libcryptopp. This update is simply a rebuild against this new libcryptopp and fixes this issue. Packages in 5/core/updates_testing: ======================== synergy-1.5.0-3.1.mga5 synergy-gui-1.5.0-3.1.mga5 Source RPM: ======================== synergy-1.5.0-3.1.mga5.src.rpm Assignee:
bugsquad =>
qa-bugs Working fine here, though I don't use the cfb crypto. Advisory added to svn, validating the update. Keywords:
(none) =>
validated_update An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGAA-2016-0073.html Status:
NEW =>
RESOLVED |