stanza

Guide to update 4.3-3827-beta7 to Update 6 andHeartbleed fix

Recommended Posts

BE WARNED, it's best to make a backup....or perform this on a test system to make sure it is going to work before proceeding

=================================================

=================================================

 

OK here is a quick guide on how to update Trantors 4.3-3827 beta7 to fix the Heartbleed problem

 

Just as with the 4.3-4810 update 4 fix to stop your system getting a virus / trojan

 

You should update your 4.3-3827 if you have your system accessible from the internet

 

This is a similar but slightly different way to update your system to my other thread

http://xpenology.com/forum/viewtopic.php?f=2&t=2049

 

1st step make sure SSH is enabled

 

Open Control Panel and select the Terminal icon

1.png

 

2.png

 

Select "Apply" and return to Control Panel

 

2nd Step The Update Check

 

Select "DSM Update"

 

2a.png

 

Select "Update Settings"

 

3.png

 

Choose "Important Updates Only"

 

4.png

 

Select "OK"

 

It will now check and show there is an "Update 2 Available for download"

 

5.png

 

Select the "Download Button" and wait for it to arrive

 

BUT DO NOT SELECT "Update Now"

BUT DO NOT SELECT "Update Now"

BUT DO NOT SELECT "Update Now"

 

6.png

7.png

 

BUT DO NOT SELECT "Update Now"

 

Now we have to SSH into our Xpenology box and run 2 commands to enable the update to work

 

eg replace 10.0.0.29 with the IP Address of your Xpenology box

 

ssh root@10.0.0.29
root@10.0.0.29's password: 


BusyBox v1.16.1 (2014-02-11 20:19:16 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

MicroDS2>

 

Now we can have a look at what the Update package contains, by changing to the hidden @smallupd@te_deb Directory stored on your volume1

 

to save you the trouble.....here is the list

 

MicroDS2> cd @smallupd@te_deb/

MicroDS2> ls
apache-2.2.x-virtual-worker-bromolow-bin_2.2.25-3827-s2_all.deb
flashupdate_4.3-3827-s1_all.deb
iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb
libsynosdk-bromolow-bin_4.3-3827-s1_all.deb
libsynosdk-bromolow-bin_4.3-3827-s2_all.deb
lnxscemd-2.0-bromolow-bin_4.3-3827-s1_all.deb
lnxsdk-bromolow-bin_4.3-3827-s1_all.deb
openssl-1.0.x-bromolow-bin_1.0.1f-3827-s1_all.deb
openssl-1.0.x-bromolow-bin_1.0.1g-3827-s2_all.deb
php-5.3.x-bromolow-bin_5.3.28-3827-s1_all.deb
samba-3.6.x-bromolow-bin_3.6.9-3827-s1_all.deb
smallupdate_4.3-3827-s2_all.deb
synosearchagent-bromolow-bin_4.3-3827-s2_all.deb

 

Now we make sure we are in the root directory (Top Level Directory)

 

MicroDS2> cd /

 

Having a look we can see there is an autoupd@te.info file

 

MicroDS2> ls -asl

 

Should show something similar to

 

MicroDS2> ls -asl
  4 drwxr-xr-x   23 root     root          4096 Apr 30 19:50 .
  4 drwxr-xr-x   23 root     root          4096 Apr 30 19:50 ..
  4 drwxr-xr-x    2 root     root          4096 Apr 30 01:06 .old_patch_info
  4 -rw-------    1 root     root          1024 Apr 30 01:07 .rnd
  4 drwxr-xr-x    2 root     root          4096 Apr 30 01:07 .system_info
  4 -rw-r--r--    1 root     root           817 Apr 30 19:50 autoupd@te.info <<<<<<<<<<<<<<<<<<<<<<
  4 drwxr-xr-x    2 root     root          4096 Apr 30 01:06 bin
 56 drwxr-xr-x   10 root     root         57344 Apr 30 19:31 dev
  4 drwxr-xr-x   26 root     root          4096 Apr 30 19:38 etc
  4 drwxr-xr-x   24 root     root          4096 Apr 30 19:31 etc.defaults
  4 drwxr-xr-x    2 root     root          4096 Feb 12 18:06 initrd
 20 drwxr-xr-x   20 root     root         20480 Apr 30 19:49 lib
  4 drwxr-xr-x    2 root     root          4096 Apr 30 01:06 lib64
  4 drwx------    2 root     root          4096 Feb 12 17:58 lost+found
  4 drwxr-xr-x    2 root     root          4096 Feb 12 17:48 mnt
  0 dr-xr-xr-x  175 root     root             0 Apr 30 19:31 proc
  4 drwxr-xr-x    3 root     root          4096 Apr 30 01:06 root
  4 drwxr-xr-x    2 root     root          4096 Apr 30 01:06 sbin
  0 drwxr-xr-x   12 root     root             0 Apr 30 19:31 sys
  0 drwxrwxrwt   10 root     root          1280 Apr 30 19:53 tmp
  4 drwxr-xr-x    8 root     root          4096 Apr 30 01:06 usr
  4 drwxr-xr-x   14 root     root          4096 Apr 30 19:31 var
  4 drwxr-xr-x   11 root     root          4096 Apr 30 01:06 var.defaults
  4 drwxr-xr-x   14 root     root          4096 Apr 30 19:50 volume1
  4 drwxr-xr-x    3 root     root          4096 Apr 30 19:31 volumeUSB1

 

We need to change this file to allow the update to work properly

 

To change the file all we need is to run two simple commands

 

MicroDS2> sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1

 

then

 

MicroDS2> mv /autoupd@te.info1 /autoupd@te.info

 

Be warned, the system will reboot once we perform the next step...so make preparations in case you are in the middle of a file copy etc.

 

So now back in Xpenology web interface we can select the Update Button

 

Once the system have rebooted, you can check if all went ok by once again selecting "DSM Update" inside control panel

 

Which should show (if all went correctly)

 

8.png

 

.

Edited by Guest

Share this post


Link to post
Share on other sites

Great, I would like to update it but weirdly my Xpenology says I have the newest DSM version (4.3 Beta 7). Is there some packed update that I can sideload via FTP (I mean pack like beta 7).

 

EDIT: Nevermind it seems it needed some more time cause it just found the update in the morning.

Share this post


Link to post
Share on other sites

Hi to all and a big thank to the community for this work on the DSM,

This is my first post so I have a trouble ! i'm french, so sorry for my poor english...

 

The update 2 fails for me, so I dug a little and I would like you to give me some ideas that I have not tried.

Of course after downloading the update 2 I launched the 'sed' command to adjust the autoupd@te.info file before finalizing the update and when I updated everything seems ok, the evidence :

3apIEwx.png

 

But after reboot the log shows 11 errors update corresponding to 11 packages of the update 2 :

JhUWQ0y.png

 

'var/log/dpkg_upgrade.log' shows the problem:

2014/05/09 20:38:31 ===========[-x /volume1//@smallupd@te_deb/smallupdate_4.3-3827-s2_all.deb /smallUpd@teTempFolder]===========

2014/05/09 20:40:01 ===========[-i /smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb ]===========

Authenticating /smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb ...

gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/pubring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/pubring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/pubring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/pubring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/pubring.gpg': No such file or directory

debsig: Failed verification for /smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb.

dpkg: error processing /smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb (--install):

verification on package /smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb failed!

Errors were encountered while processing:

/smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb

 

or even

 

2014/05/09 20:40:03 Failed to install -i/smallupd@te/libsynosdk-bromolow-bin_4.3-3827-s2_all.deb

2014/05/09 20:40:03 ===========[-i /smallupd@te/openssl-1.0.x-bromolow-bin_1.0.1g-3827-s2_all.deb ]===========

Authenticating /smallupd@te/openssl-1.0.x-bromolow-bin_1.0.1g-3827-s2_all.deb ...

gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/pubring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/pubring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/pubring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/pubring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

gpg: keyblock resource `/var/services/homes/root/.gnupg/pubring.gpg': No such file or directory

debsig: Failed verification for /smallupd@te/openssl-1.0.x-bromolow-bin_1.0.1g-3827-s2_all.deb.

dpkg: error processing /smallupd@te/openssl-1.0.x-bromolow-bin_1.0.1g-3827-s2_all.deb (--install):

verification on package /smallupd@te/openssl-1.0.x-bromolow-bin_1.0.1g-3827-s2_all.deb failed!

Errors were encountered while processing:

/smallupd@te/openssl-1.0.x-bromolow-bin_1.0.1g-3827-s2_all.deb

2014/05/09 20:40:04 Failed to install -i/smallupd@te/openssl-1.0.x-bromolow-bin_1.0.1g-3827-s2_all.deb

 

'secret ring' and 'public ring' in /root folder are absent :

Gtc8xzX.png

 

Another check shows that the update has not occurred :

YaYwDFK.png

 

Are you well on being update 2 ?

Do you have these files 'secret ring' and 'public ring' ?

 

Thank you for your advice and audits

Share this post


Link to post
Share on other sites

Yes everything is working here :

 


fileshanker> pwd
/root
fileshanker> ls -la
drwxr-xr-x    5 root     root          4096 May  7 23:59 .
drwxr-xr-x   24 root     root          4096 May  3 13:47 ..
-rw-------    1 root     root            16 May  7 23:59 .esd_auth
drwx------    2 root     root          4096 May  2 19:42 .gnupg
-rw-r--r--    1 root     root           366 Feb 14 12:08 .profile
drwx------    2 root     root          4096 May  8 00:43 .pulse
-rw-------    1 root     root           256 May  7 23:59 .pulse-cookie
drwxr-xr-x    2 root     root          4096 May  2 19:15 pci
-rw-r--r--    1 root     root        249507 Feb 22 11:45 syno-i686-bootstrap_1.2-7_i686.xsh
fileshanker> openssl version
WARNING: can't open config file: /usr/syno/ssl/openssl.cnf
OpenSSL 1.0.1g-fips 7 Apr 2014

 

The dpkg_upgrade.log :

 

2014/05/02 16:40:28      ===========[-x /volume1//@smallupd@te_deb/smallupdate_4.3-3827-s2_all.deb /smallUpd@teTempFolder]=====
2014/05/02 16:42:16      ===========[-i /smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb ]===========
Authenticating /smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb ...
passed
Selecting previously unselected package iptables-1.4.2-bromolow-bin.
(Reading database ... 0 files and directories currently installed.)
Unpacking iptables-1.4.2-bromolow-bin (from .../iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb) ...
Setting up iptables-1.4.2-bromolow-bin (1.4.2-3827-s1) ...
2014/05/02 16:42:17      ===========[-i /smallupd@te/libsynosdk-bromolow-bin_4.3-3827-s1_all.deb ]===========
Authenticating /smallupd@te/libsynosdk-bromolow-bin_4.3-3827-s1_all.deb ...
passed

etc etc

 

A quick google search leads me to believe that this is a permissions issue. Maybe try to run the update as admin? Also did you run the commands as root?

 

Also, these are strange to me :

 

gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

 

because i don't have these directories either. I don't have User Homes enabled though, maybe you do and it's causing issues? Control Panel > Users > User Home

 

p.s tu peux aussi ouvrir un thread dans la section FR du forum, même si ton anglais n'est pas mauvais à mon avis.

Share this post


Link to post
Share on other sites

Thank you for this detailed answer,

I also think it's a rights issue but i'm not understand why et how solve it...

I tried with and without homes enabled users but it is similar, although I run the 'sed' command as root.

 

If you sent me the contents of your /root folder do you think it could be work ?

Share this post


Link to post
Share on other sites

A quick question.

Can I update my NAS to Update2 Heartbleed fix directly from beta3 insteal of beta7?

Thanks.

Share this post


Link to post
Share on other sites

hi guys just some feed back :

 

i'm with the beta8, and i've done the update 2 fix but with a little issue :

 

i've done the tutorial once, but the fist time i was'nt able to download, maybe the system does it itself ! anyway i've followed the instruction, and at the end, during the update , the dsm send me a blank message with just "ok". and after the false update, the update screen on the dsm was like the tutorial, (i can download the update)

So second attempt, and it was the one :smile: it was done perfectly !

 

Beta9 DSM 4.3-3827 update 2 here

 

thanks again

Share this post


Link to post
Share on other sites

Hi. i have a question. cant an img be done whit all the uppdates from trantor? for noobs like me? or can samone link to the img i start with and the uppdates in order i have to uppdate?

Share this post


Link to post
Share on other sites
hi guys just some feed back :

 

i'm with the beta8, and i've done the update 2 fix but with a little issue :

 

i've done the tutorial once, but the fist time i was'nt able to download, maybe the system does it itself ! anyway i've followed the instruction, and at the end, during the update , the dsm send me a blank message with just "ok". and after the false update, the update screen on the dsm was like the tutorial, (i can download the update)

So second attempt, and it was the one :smile: it was done perfectly !

 

Beta9 DSM 4.3-3827 update 2 here

 

thanks again

 

Same thing happened to me. but i cant update...

I'm with Beta4... Maybe i need to update to beta8...

 

Strange as i thought the beta's only included drivers.

Share this post


Link to post
Share on other sites

Hi,

 

Just updated successfully to DSM 4.3-3827 Update 4 running on Trantor's BETA 8 using your method!

 

Many thanks for this tutorial! :grin:

 

 

EDIT: Update 5 is working too!!!

Share this post


Link to post
Share on other sites

Hi guys, unable to get this working, even after following the steps to the letter.

 

I just get a blank box.

 

Any ideas, please?

Share this post


Link to post
Share on other sites

Updated both my "back-up" and "main" N54L, running Trantor 4.3-3827 beta7 today, and have now Update 5 running :cool:

Share this post


Link to post
Share on other sites
Hi guys, unable to get this working, even after following the steps to the letter.

 

I just get a blank box.

 

Any ideas, please?

 

Can you give us more details? Which DSM version are you running? Which boot (Trantor's, Nanoboot, ...) Take a screenshot maybe?

Share this post


Link to post
Share on other sites

We have a new update (Update 6)and works fine with the same instructions.

Whats new? : update.synology.com/autoupdate/whatsnew.php?model=DS3612xs

:wink:

Share this post


Link to post
Share on other sites
We have a new update (Update 6)and works fine with the same instructions.

Whats new? : update.synology.com/autoupdate/whatsnew.php?model=DS3612xs

:wink:

You mean update 5 and not 6

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
We have a new update (Update 6)and works fine with the same instructions.

Whats new? : update.synology.com/autoupdate/whatsnew.php?model=DS3612xs

:wink:

You mean update 5 and not 6

 

 

Sent from my iPhone using Tapatalk

 

No he means update 6

 

5 was and is a minor update, 6 has a bit more :wink:

 

DSM 4.3-3827 Update 6

(2014/8/26)
Fixed Issues
Upgraded OpenSSL to Version 1.0.1i to fix multiple security issues (CVE-2014-3505, CVE-2014-3506, CVE-2014-3507, CVE-2014-3508, CVE-2014-3509, CVE-2014-3510, CVE-2014-3511, CVE-2014-3512, and CVE-2014-5139).
Implemented fixes for Kerberos 5 to address multiple security issues that allow remote attackers to cause a denial of service (CVE-2012-1013, CVE-2014-4341, CVE-2014-4342, CVE-2014-4344).
Updated to the last version of PHP 5.3, announced EOL by the official PHP development team, to address multiple security vulnerabilities (CVE-2014-3981, CVE-2014-3515, CVE-2013-6712, CVE-2014-0207, CVE-2014-0238, CVE-2014-0237, CVE-2014-4049).

==========================

DSM 4.3-3827 Update 5

(2014/7/24)
Improvements
Improved the stability of volume expansion.

 

.

Share this post


Link to post
Share on other sites