Recommended Posts

It seems that Synology has released a security patch yesterday to address the potential vulnerability of DSM in relation to recent WannaCry attacks. Xpenology usually is quite stable once you got the bootloader all working bug free; but it is the time like these that could cause problem to xpenology users, just like synolock back in 2014. Xpenology users are limited to certain version, depends on the bootloader version they are using. For instance some user are still on DSM 5.x which their bootloader doesn't support further update or a complete upgrade of bootloader is require if to upgrade to DSM 6; same applies to those, and including myself, who yet to get the newer bootload which support DSM 6.1 to work with their machine.

 

My queries, with the difficulties mentioned above, how do we protect ourselves from security vulnerability?

 

Version: 6.1.1-15101-4

(2017/05/25)

Important Note

The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly.

Fixed Issues

Fixed a security vulnerability regarding samba service (CVE-2017-7494).

Share this post


Link to post
Share on other sites

But if you can not upgrade to the latest versions of Samba immediately, you can work around the vulnerability by adding the following line to your Samba configuration file smb.conf:

nt pipe support = no

Share this post


Link to post
Share on other sites

If you're using Jun's 1.0.2a2 loader it's pretty safe to update to U4. So far going from no update all the way to U4 has caused no issues for me.

Share this post


Link to post
Share on other sites
If you're using Jun's 1.0.2a2 loader it's pretty safe to update to U4. So far going from no update all the way to U4 has caused no issues for me.

 

Sure enough if you already got Jun's 1.0.2a2 or 1.0.2a working with your machine, then you are safe. I personally encountered Error 13 with both loader and just couldn't get it working with my rig. And this post is about people like me not able to update to these 2 loader with bug free DSM 6.1 installed.

 

Recommendation like Salah's is quite useful. There we have a hint what could be done if we could not upgrade to DSM 6.1.1-U4.

 

Now if Salah can elaborate more this method, that would be great.

Share this post


Link to post
Share on other sites
If you're using Jun's 1.0.2a2 loader it's pretty safe to update to U4. So far going from no update all the way to U4 has caused no issues for me.

Not true as update will mess with drivers

Share this post


Link to post
Share on other sites
If you're using Jun's 1.0.2a2 loader it's pretty safe to update to U4. So far going from no update all the way to U4 has caused no issues for me.

Not true as update will mess with drivers

 

Not really loader and syno version will work as no major changes where make it is still 6.1.1 Im on u4 baremetal

Share this post


Link to post
Share on other sites
2 часа назад, GaryM сказал:

Update to U4 is safe

all security updates (from 1 to 4) for DSM 6.1.1-15101 was safe for me.

 

В 26.05.2017 в 18:46, cuspess сказал:

how do we protect ourselves from security vulnerability?

install security updates in time after release, syno very careful about users and make updates so fast.

if you worry about "brick-station" after update - test it on virtual machines or on test enviroment before install.

AFAIK, minor updates (like a 15101 Update from 1 to 4) have less numbers of fails on XPENology than major updates (like a 6.1.2-15132 from 6.1.1-15101).

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.