Synology has released Cloud Sync version 1.0-0378, In addition to several fixes it adds support for Amazon Cloud Drive and improves WebDAV compatibility.
The complete set of changes is:
Added support for Amazon Cloud Drive.
Improved WebDAV compatibility.
Fixed an issue where S3 subfolders might not be correctly displayed.
Fixed an issue where token expiration is not duly notified in certain conditions.
Fixed an issue where an expired access token might lead to a syncing loop.
Updated Yandex Disk icon.
I applied the update to both my test NAS, a DS212+, and my production NAS, a DS1815+, without a problem. But I don’t use any of the affected services such as S3. Microsoft OneDrive, Google Drive, and Dropbox all seem unaffected.
Synology has released Disk Station Manager 5.2 Update 2 and is calling it DSM 5.2-5565 Update 2. While there are some security fixes there’s nothing major. Unless, of course, you’re impacted by one of the bugs that have been fixed.
Synology has also stated that they reviewed DSM and their implementation of OpenSSL is not vulnerable to the LogJam vulnerability.
The complete list of documented fixes is:
Improved the stability of SHR expansion.
Improved the stability of SMB transfer when the system is being accessed by an excessive number of clients.
Fixed multiple kernel vulnerabilities (CVE-2014-3122, CVE-2014-3153, CVE-2014-0196, and CVE-2014-4699).
Fixed an issue where CPU usage could remain high when widget is enabled.
Fixed an issue where LDAP users could fail to log in to DSM.
Fixed an issue where files could not be downloaded via Windows’ terminal.
Fixed an issue where system cannot enter hibernation.
Fixed an issue where some folders with non-English names would become inaccessible via SMB.
Fixed an issue where volumes/iSCSI LUN cannot be displayed after the Synology High Availability system resumes from safe mode with UPS connected.
I installed the update on a DS1815+, DS415+, DS212+ and DS1511+ without any issues. It does reboot the NAS
DiskStation Manager 5.2 (DSM 5.2) has only been out a few days but they already released an update. DSM 5.2 Update 1 has been released.
The documented changes include:
Fixed an issue where users could fail to join domain when the domain admin account contains specific characters.
Improved the compatibility with USB devices.
Fixed a security vulnerability to prevent cross-site scripting attacks (XSS).
Upgraded PHP to 5.5.25 to address multiple security vulnerabilities (CVE-2006-7243, CVE-2015-4021, CVE-2015-4022, CVE-2015-4024, CVE-2015-4025, CVE-2015-4026).
Improved the compatibility with 3rd party DTV applications.
Fixed an issue where SSD cache volume information may not be displayed correctly in Resource Monitor.
Fixed an issue where users with guest accounts would be unable to create new files or folders via SMB protocol.
I haven’t encountered any of these issues in the short time I’ve been using DSM 5.2. I will be setting up a SSD cache in a week or so and the security fixes are always welcome so I immediately applied the update.
I applied the update to a DS1815+, DS415+ and DS212+ Synology NAS without having a problem. The update only took a couple of minutes but it did require a NAS reboot.
Today Synology Released DiskStation Manager 5.2 (a.k.a. DSM 5.2). I’ve been running the beta version since it was released and I’ve liked it. The beta has been problem free, at least for me, although the upgrade from the beta wasn’t. My problems appear beta related as a second Synology NAS, that was running the latest DSM 5.1, not the beta, didn’t have any problems.
The process I follow for upgrades is fairly straight-forward:
Update all installed packages to the latest version available.
Download and update DSM through the Control Panel.
The only beta upgrade issue I consider serious is that CloudSync no longer starts because of some version confusion1. After updating to DSM 5.2 the CloudStation package won;t start because it says it’s incompatible with the installed DSM version. The package won’t update because it’s a higher version number than what’s available for installation. The installed version is 1.0-0327 while the version available for install is 1.0-0263 and dates back to December 2014. I’m hoping Synology is just slow in updating the repository or can quickly update the version check and the package actually works. I’m going to give them a few days before I uninstall and then re-install the package. I’m concerned that the re-install will force a new sync which I’d prefer to avoid. [Updated 5/13 – Sure enough, the CloudSync package had an update waiting this morning and it’s fine after the update.]
The beta upgrade did not re-start any of the packages. Some started manually but some did not so I rebooted the NAS and they all started.
Neither of these problems occurred when I updated from DSM 5.1 to DSM 5.2.