TWO DSM 5.0 Update 2 but only later one fix heartbleed

[jokies]

To those who had previously updated DSM 5.0 to update 2 before GMT Apr 9, your DSM is still affected by the heartbleed security problem.

In order to apply the newer version of the update, you need to edit /etc.defaults/VERSION via ssh, change "smallfixnumber" value from "2" to "1" and redownload the patch.

You can also see builddate here, if it is not "2014/04/09", then you need to take action immediately.

In order to apply the patch, you still need the magic small script to be runned after you download the patch and before you proceed.

Good luck.

The earlier DSM 5.0 update 2 is released Apr 3, which does not include the fix.

Don't forget to regenerate your SSL certificate, otherwise you're still threatened.

Edited April 11, 2014 by Guest

[LayS]

work perfectly

 

OpenSSL 1.0.1g-fips 7 Apr 2014

 

 

thanks a lot;)

[Plasma]

Sorry for the noob question.

 

Once SSH'ed into Disk Station as root, I was able to locate the VOLUME file. What is the syntax (how do you edit the value) to 1.

 

Thanks

[jokies]

Sorry for the noob question.

 

Once SSH'ed into Disk Station as root, I was able to locate the VOLUME file. What is the syntax (how do you edit the value) to 1.

 

Thanks

After SSH to your diskstation, put in the following command exactly and press ENTER to enter text edit mode:

vi /etc.defaults/VERSION

move your cursor around until you find the row start with "smallfixnumber".

Then press "i" on your keyboard. Use backspace to delete "2", and press "1" on your keyboard. Now you finished modifying the file.

Press "ESC" and then press ":", "w" and "q" on your keyboard, followed by ENTER, the file is now saved with the change.

Go to your diskstation web UI, you should see it now display "Update 1" instead of "Update 2", otherwise something went wrong, try again.

Edited April 12, 2014 by Guest

[Plasma]

Sorry for the noob question.

 

Once SSH'ed into Disk Station as root, I was able to locate the VOLUME file. What is the syntax (how do you edit the value) to 1.

 

Thanks

After SSh to your diskstation, put in the following command exactly and press ENTER to enter text edit mode:

vi /etc.defaults/VERSION

move your cursor around until you find the row start with "smallfixnumber".

Then press "i" on your keyboard. Use backspace to delete "2", and press "1" on your keyboard. Now you finished modifying the file.

Press ":" and then press "w" and "q" on your keyboard, followed by ENTER, the file is now saved with the change.

Go to your diskstation web UI, you should see it now display "Update 1" instead of "Update 2", otherwise something went wrong, try again.

 

 

 

Worked Great Thank You very much.

[wenlez]

How do you update from Update 1 to Update 2? i get the following error:

 

Apr 12 22:11:10 MasterWaiter updater: updater.c:4890 Start of the updater...
Apr 12 22:11:10 MasterWaiter updater: updater.c:4994 This is X86 platform
Apr 12 22:11:10 MasterWaiter updater: updater.c:5008 The SynoBoot partitions exist.
Apr 12 22:11:10 MasterWaiter updater: updater.c:3128 SYNORedBootUpdCheckAndApply(3128): Skip bootloader update, no uboot_do_upd.sh exists
Apr 12 22:11:10 MasterWaiter updater: updater.c:340 fail to backup images. cp -f /tmp/bootmnt/rd.gz //synob@ckup
Apr 12 22:11:10 MasterWaiter updater: updater.c:394 Failed to open /tmp/bootmnt/checksum.syno [No such file or directory]
Apr 12 22:11:10 MasterWaiter updater: updater.c:474 Fail to get update [/bin/rm -f /tmp/checksum.syno.tmp] to checksum.syno.
Apr 12 22:11:10 MasterWaiter updater: updater.c:5140 failed to install images
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [rd.gz] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [grub_cksum.syno] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [updater] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [VERSION] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [checksum.syno] fail, remove it from synoboot
Apr 12 22:11:11 MasterWaiter updater: updater.c:5490 Failed to accomplish the update! (errno = 16)
Apr 12 22:11:11 MasterWaiter entry.cgi_SYNO.Core.Upgrade[1].start[28872]: smallupdate.cpp:1017 failed to exec updater -r
Apr 12 22:11:11 MasterWaiter entry.cgi_SYNO.Core.Upgrade[1].start[28872]: smallupdate.cpp:1206 failed to update flash
Apr 12 22:11:11 MasterWaiter entry.cgi_SYNO.Core.Upgrade[1].start[28872]: Upgrade.cpp:202 Fail to apply small update
Apr 12 22:11:11 MasterWaiter cupsd[32672]: [conf.c:1893] Filter "pstoraster" not found.
Apr 12 22:11:11 MasterWaiter synorelayd: register_api_key.cpp:226 failed to send https request to [apiauth.synology.com], err=[0x2000]
Apr 12 22:11:11 MasterWaiter synorelayd[455]: synorelayd.cpp:1221 stoped

[jokies]

How do you update from Update 1 to Update 2? i get the following error:

 

Apr 12 22:11:10 MasterWaiter updater: updater.c:4890 Start of the updater...
Apr 12 22:11:10 MasterWaiter updater: updater.c:4994 This is X86 platform
Apr 12 22:11:10 MasterWaiter updater: updater.c:5008 The SynoBoot partitions exist.
Apr 12 22:11:10 MasterWaiter updater: updater.c:3128 SYNORedBootUpdCheckAndApply(3128): Skip bootloader update, no uboot_do_upd.sh exists
Apr 12 22:11:10 MasterWaiter updater: updater.c:340 fail to backup images. cp -f /tmp/bootmnt/rd.gz //synob@ckup
Apr 12 22:11:10 MasterWaiter updater: updater.c:394 Failed to open /tmp/bootmnt/checksum.syno [No such file or directory]
Apr 12 22:11:10 MasterWaiter updater: updater.c:474 Fail to get update [/bin/rm -f /tmp/checksum.syno.tmp] to checksum.syno.
Apr 12 22:11:10 MasterWaiter updater: updater.c:5140 failed to install images
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [rd.gz] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [grub_cksum.syno] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [updater] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [VERSION] fail, remove it from synoboot
Apr 12 22:11:10 MasterWaiter updater: updater.c:592 Restore [checksum.syno] fail, remove it from synoboot
Apr 12 22:11:11 MasterWaiter updater: updater.c:5490 Failed to accomplish the update! (errno = 16)
Apr 12 22:11:11 MasterWaiter entry.cgi_SYNO.Core.Upgrade[1].start[28872]: smallupdate.cpp:1017 failed to exec updater -r
Apr 12 22:11:11 MasterWaiter entry.cgi_SYNO.Core.Upgrade[1].start[28872]: smallupdate.cpp:1206 failed to update flash
Apr 12 22:11:11 MasterWaiter entry.cgi_SYNO.Core.Upgrade[1].start[28872]: Upgrade.cpp:202 Fail to apply small update
Apr 12 22:11:11 MasterWaiter cupsd[32672]: [conf.c:1893] Filter "pstoraster" not found.
Apr 12 22:11:11 MasterWaiter synorelayd: register_api_key.cpp:226 failed to send https request to [apiauth.synology.com], err=[0x2000]
Apr 12 22:11:11 MasterWaiter synorelayd[455]: synorelayd.cpp:1221 stoped

Welcome to the forum.

Please read this carefully: viewtopic.php?f=2&t=2809

On the bottom of page one antelo gave an example about how to do it.

[djelusion]

work perfectly

 

OpenSSL 1.0.1g-fips 7 Apr 2014

 

 

thanks a lot;)

 

 

how can you check to see what version of openssl you have?.

 

vi /etc.defaults/VERSION

majorversion="5"

minorversion="0"

buildphase="release"

buildnumber="4458"

smallfixnumber=2

builddate=2014/04/09

[jokies]

work perfectly

 

OpenSSL 1.0.1g-fips 7 Apr 2014

 

 

thanks a lot;)

 

 

how can you check to see what version of openssl you have?.

 

vi /etc.defaults/VERSION

majorversion="5"

minorversion="0"

buildphase="release"

buildnumber="4458"

smallfixnumber=2

builddate=2014/04/09

 

Please read posts carefully, I said if your builddate is earlier than 2014/04/09 then you should take action.

Also you can issue

openssl version

in your terminal to see your openssl version. The openssl 1.0.1g had the bug fixed.