noki Posted June 9, 2015 Share #1 Posted June 9, 2015 (2015/06/09) Important Information A thorough investigation has been done, and it is confirmed that DSM and its related packages are not impacted by the LogJam vulnerability because of the way Synology implements OpenSSL in our system. Fixed Issues 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. Is possible update without problem on XPEnoboot 5.2-5565.2 ??? Link to comment Share on other sites More sharing options...
Guest Posted June 9, 2015 Share #2 Posted June 9, 2015 Quick reply: Just tested in VMware Workstation with no volumes, iSCSI or packages installed and it looks like it works but no guarantees from me that it will work in all situations Link to comment Share on other sites More sharing options...
Hyphen Posted June 9, 2015 Share #3 Posted June 9, 2015 Just installed it on my nas with 1 volume and the phpvirtualbox package. The update "hangs" after install, so i just turned the power off and rebooted the nas. After the reboot i could start the vm running on the nas just fine. Link to comment Share on other sites More sharing options...
noki Posted June 9, 2015 Author Share #4 Posted June 9, 2015 Block phpvirtualbox or DSM? Link to comment Share on other sites More sharing options...
Hyperbit Posted June 9, 2015 Share #5 Posted June 9, 2015 Update 2 works for me - no problems on n40L Bare Metal Link to comment Share on other sites More sharing options...
noki Posted June 9, 2015 Author Share #6 Posted June 9, 2015 update run, I too have been stuck at 47%. Off brutally restart everything seems to work well! Xpenology run in Dell Optiplex USSF 760 Link to comment Share on other sites More sharing options...
DasMoritz Posted June 9, 2015 Share #7 Posted June 9, 2015 Works fine on HP Microserver Gen 8 bare metal. I have also to restart "hard" after the timer finished. Link to comment Share on other sites More sharing options...
derwoodbones Posted June 9, 2015 Share #8 Posted June 9, 2015 Working perfect on Bare Metal Dell Optiplex 755 Link to comment Share on other sites More sharing options...
Balrog Posted June 9, 2015 Share #9 Posted June 9, 2015 After updating my HP Microserver Gen 8 (baremetal) there are problems with SSL. No https-service runs correct. It must have to do with the certififcates... I will investigate this later. EDIT: So first workaround is to disable SSL: - make a SSH connection and logon as root - edit /etc/synoinfo.conf with your favorite editor (vi or nano I asume) - search "runHTTPS" and "runWebHTTPS" and change both entries to "no" - save file and reboot After the reboot SSL is deactivated but you can login. Now to step 2 and howto make SSL work again.... EDIT2: I make SSL working again Something in the update-process has destroyed the contents of files under /etc/httpd/conf/extra so e.g. the file "httpd-ssl.conf-cipher" was totally filled with garbage. I copied the files from /etc.defaults/httpd/conf/extra (which has correct files) to /etc/httpd/conf/extra. To make it complete I copied /etc.defaults/httpd/conf to /etc/httpd/conf. The last step is to remake the internal SSL-certificates: cd /usr/syno/etc/ssl/ ./mkcert.sh wait till the new internal certificates are created and then reboot Voila, after the reboot all SSL-Sites are up and running again! Link to comment Share on other sites More sharing options...
Balrog Posted June 9, 2015 Share #10 Posted June 9, 2015 My second DSM installation under Hyper-V runs without any issues but there I have not enabled any ssl-services (not under web-services and not under DSM itself). So be careful at upgrading if you have enabled SSL! Link to comment Share on other sites More sharing options...
johnduff Posted June 9, 2015 Share #11 Posted June 9, 2015 No SSL after a security update... wow ! Link to comment Share on other sites More sharing options...
kuma16830 Posted June 10, 2015 Share #12 Posted June 10, 2015 I updated my machine with update 2 and works fine. I will describe as below. My environment setup: mobo: Asus J1900I-C RAM: 4G SO-DIMM HD: Seagate 1T ST1000DM003 DSM installed ver: 5.2-5565 update 1 XPEnology ver: 5.2-5565.2 (07/06/2015) upgrade to 5.2-5565 update 2 method login in to web GUI, auto download the update file and upgrade form there. my issue I after applied 5.2 update 2, first reboot the system after the update, the console hanged at: ================== Start udevd ======================== ===== trigger device plug event ======= how to fix the issue I pressed the reset button and then it booted ok. Hope this will help to some people. The direct link for downloading the 3615xs update 2 is as below: http://usdl.synology.com/download/criti ... 3615xs.pat Version : 5.2-5565 Update 2 (2015/06/09) Important Information A thorough investigation has been done, and it is confirmed that DSM and its related packages are not impacted by the LogJam vulnerability because of the way Synology implements OpenSSL in our system. Fixed Issues 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. Link to comment Share on other sites More sharing options...
jakeandchase Posted June 10, 2015 Share #13 Posted June 10, 2015 I'm running 5.2-5565 directly on a N54L (without esxi). Do I just run the regular DSM update method? No need to change boot image/run any commands? Link to comment Share on other sites More sharing options...
Balrog Posted June 10, 2015 Share #14 Posted June 10, 2015 If you already have the actual boot-image (XPEnoboot 5.2-5565.2 (07/06/2015)) then you can do the update directly within the DSM like on real Synology. The first boot after the update might hang and you have to make a hard reset. If you want to make it safe, make a copy of /etc (e.g. with winscp) to your pc so you are able to recover important files if an error occours like at my installation (read a few posts up). Link to comment Share on other sites More sharing options...
docop1 Posted June 10, 2015 Share #15 Posted June 10, 2015 Just log over, do the dsm update and on the console of esxi it show Xpeno just hang after the reboot. I wait 15min and just do a hard reset and after i got the login promp again. fully working and my setting were all preserved. Very great released of the team. Link to comment Share on other sites More sharing options...
seanmor69 Posted June 10, 2015 Share #16 Posted June 10, 2015 Successful update to update 2 on N54L here. I disabled https in DSM just to be safe then re-enabled it after the upgrade. I did have the first boot get stuck and had to hard power down and power up. Second boot, everything was fine. Thanks! Link to comment Share on other sites More sharing options...
paradigm Posted June 11, 2015 Share #17 Posted June 11, 2015 No issues with HTTPS here, but I am using a cert that was generated by my CA rather than by the box itself. I did however have to give the box a power-cycle. Bare-Metal build on dual-core intel Atom D510, BCM IXBDN R10 ITX motherboard, in a Lacie EthernetDisk chassis. Link to comment Share on other sites More sharing options...
WiteWulf Posted June 12, 2015 Share #18 Posted June 12, 2015 I just did the same as kuma16830: was already running on Update 1, installed Update 2 through the web interface, rebooted, server locked up part way through boot, reset, booted successfully. All good now. Link to comment Share on other sites More sharing options...
Recommended Posts