Info Latest versions of DSM/SRM and packages

[fredbert]

2021-11-29​

Utility : C2IdentityDockerMgmtTool ✎ : 1.0.1-00010 ⇩ ✱
Package : C2IdentityLDAPAgent ✎ : 1.0.0-0021 ⇩ ✱

2021-11-26​

Package : Calendar ✎ : 2.4.3-10925 ⇩ ✱

2021-11-25​

Package : phpMyAdmin ✎ : 4.9.7-1032 ⇩ ✱

2021-11-24​

Utility : C2IdentityAgent ✎ : 1.0.0-00182 ⇩ ✱

2021-10-29​

Package : Git ✎ : 2.33.0-1016 ⇩ ✱

 

[fredbert]

2021-11-24​

Package : ActiveInsight ✎ : 1.2.0-1214 ⇩ ✱

 

[Nolan.S.92]

Wicked job m8!

Changes listed alphabetically, if you prefer this way.

 

[fredbert]

2021-12-03​

Package : C2IdentityLDAPAgent ✎ : 1.0.0-0023 ⇩ ✱

2021-12-02​

Package : MailPlus-Server ✎ : 2.3.1-11067 ⇩ ✱

2021-12-01​

Utility : C2IdentityAgent ✎ : 1.0.0-00183 ⇩
Package : MailClient ✎ : 2.3.1-11448 ⇩ ✱

 

[fredbert]

Rounding up a few updates from the last week.

2021-12-20​

Package : HyperBackupVault ✎ : 3.0.2-2432 ⇩
Package : HyperBackup ✎ : 3.0.2-2432 ⇩

2021-12-14​

Utility : Assistant ✎ : 7.0.2-50046 ⇩

2021-12-10​

Utility : C2IdentityAgent ✎ : 1.0.0-00203 ⇩

2021-12-06​

Utility : C2IdentityDockerMgmtTool ✎ : 1.0.1-00020 ⇩
Utility : C2IdentityDirectoryExportTool ✎ : 1.0.0-00003 ⇩
Package : C2IdentityLDAPAgent ✎ : 1.0.0-0040 ⇩

2021-12-02​

Mobile : Android-SecureSignIn ✎ : 1.0.3-093 ⇩

 

[fredbert]

Changes listed alphabetically, if you prefer this way.

Changes posted as they get added in the Synology archive webpages. Alphabetically would just mean posting all the packages every time, regardless of updates.

Package Center should be alerting to updates but often, for me, it takes weeks or months for it to tell me. Sometimes CMS finds updates well ahead of Package Center.

 

[fredbert]

Latest updates up to this morning (0600 UK).

Today also has DSM 7.0.1-42218 Update 1 and 6.2.4-25556 Update 3 released in response to Synology-SA-22:01

Synology Security - Synology-SA-22:01 DSM

Multiple vulnerabilities allow remote attackers, or remote authenticated users to inject arbitrary web script or HTML via a susceptible version of DiskStation Manager (DSM). Continue reading... - - - Source: synology.com

www.synoforum.com

You can get your NAS's patch file (you have to be on either DSM 7.0.1-42218 and DSM 6.2.4-25556 first) and apply manually.

Synology Archive Download Site - Index of /download/Os/DSM/7.0.1-42218-1

archive.synology.com

Synology Archive Download Site - Index of /download/Os/DSM/6.2.4-25556-3

archive.synology.com

2022-01-10​

Package : ActiveBackup-Office365 ✎ : 2.3.0-12531 ⇩ ✱

2021-12-29​

Utility : C2IdentityDockerMgmtTool ✎ : 1.0.1-00061 ⇩
Utility : C2IdentityDirectoryExportTool ✎ : 1.0.0-00005 ⇩
Package : C2IdentityLDAPAgent ✎ : 1.0.0-0061 ⇩

2021-12-28​

Os : SRM ✎ : 1.2.5-8227-3 ⇩
Mobile : Android-DSfile ✎ : 4.14.0-468 ⇩

2021-12-27​

Package : NBR ✎ : 10.5.1.61510-3001 ⇩
Package : NBR-Transporter ✎ : 10.5.1.61510-3001 ⇩

2021-12-21​

Package : ArchiwareP5 ✎ : 7.0.6-1008 ⇩

 

[Danabw]

So allow me my one (hopefully) dumb question for the day - none of these patches are released as package updates in DSM?

If you don't find and update manually you don't get these, or don't get them until Synology decides they have enough to release a package update via DSM? Oops...just saw this above:

Package Center should be alerting to updates but often, for me, it takes weeks or months for it to tell me. Sometimes CMS finds updates well ahead of Package Center.

But my Hyper Back up version below, which DSM seems to think is current appears to be waaay older than the version in the patch list. Is the gap between patches and package updates that huge that I can be on 2.2.8.x and current is 3.0.2.x, or am I misunderstanding...

My current version:

Version in patch list above:

 

[marco]

After some time the new packages are available on Package Center. If someone don't want to wait, can install the update manually.

 

[Danabw]

After some time the new packages are available on Package Center. If someone don't want to wait, can install the update manually.

Thanks...the "after some time" lag certainly feels lengthy. I'm not anxious to update for the sake of updating, but I am interested in getting security update/patches sooner than later.

Ahhh...nvm on this particular update - the DSM 6.x current release is what I have, the patch list above seems to be for DSM 7.

DSM 6:

DSM 7:

 

[fredbert]

My script gets the latest version’s info. Since DSM 7’s release this is usually a version number for it but there is usually a matching DSM 6 package update, I just don’t know how to determine which it would be.

 

[fredbert]

No update included for DSM (odd!). Oh the download seems to have been pulled but release notes and SA-22:01 still refer to it.

2022-01-11​

Utility : SynologyDriveClient ✎ : 3.0.3-12689 ⇩ ✱

2022-01-07​

Package : SynologyDrive ✎ : 3.0.3-22689 ⇩ ✱

 

[akahan]

Disconcerting that Synology has yet again posted a DSM update to their ftp site, and then taken it back down. I need to learn to stop installing these things as soon as they're released, but when they fix security issues it's hard to resist. It's a godddam Sophie's Choice.

 

[Telos]

Disconcerting that Synology has yet again posted a DSM update to their ftp site, and then taken it back down. I need to learn to stop installing these things as soon as they're released

As posted in the other thread, Synology will inevitably replace the patch with one with the same build number, leaving you no simple ability to install the lastest "fix".

 

[Danabw]

As posted in the other thread, Synology will inevitably replace the patch with one with the same build number, leaving you no simple ability to install the lastest "fix".

Lovely...damned if you do, damned if you don't.

 

[Telos]

Lovely...damned if you do, damned if you don't.

ICBW, but I recall that a mode 2 reset, will then enable you to reinstall all update patches. You may also be able to "trick" DSM by editing the patch file to make it appear as the next numerical update... Though I've not tried that.

 

[Danabw]

ICBW, but I recall that a mode 2 reset, will then enable you to reinstall all update patches. You may also be able to "trick" DSM by editing the patch file to make it appear as the next numerical update... Though I've not tried that.

Yabbut as you say, not incrementing the build number is a complete foobar and just hard to comprehend why they would do that, other than internal laziness/fear of retribution (e.g., new build number kicks off new testing requirements and/or notification of management that they screwed up again and had to re-release a patch, etc.).

We should not have to resort to resets and tricks to have a stable system. I worked w/FW and SW teams for decades, and if we released two different patches w/the same build number heads would have rolled...can't believe it's standard practice w/Synology.

 

[Telos]

it's standard practice w/Synology

I believe it's due to embarrassment and "face saving". Synology can pretend that "Update X" is perfect in every respect, after re-releasing it countless times.

 

[Jan Janowski]

Why I await final Update + 2-4 weeks!

Gee... Is it THAT HARD to update a number?

 

[Danabw]

Why I await final Update + 2-4 weeks!

Gee... Is it THAT HARD to update a number?

It's like having to tell your parents: "Mom, Dad, I'm sorry, but I crashed the car again..." ;-)