TOS 4.2.43(ARM) is Released for Update

[TMRyan]

TOS 4.2.43 (ARM) Release Notes

Applicable models: F2-210, F4-210

This update includes the following bug fixes for the previous version:
1. Updated netatalk version to 3.1.14 with all CVE fixes in 3.1.15.
2. Modified the workgroup name to WORKGROUP.
3. Updated the tnas.link certificate and terra-master.com certificate.
4. Fixed the issue with AFP permissions.
5. Fixed the issue where the guest user was not disabled by default during system installation.
6. Fixed the issue of being unable to customize wallpapers.
7. Fixed the issue where SMB was not enabled by default during system installation.

Important Notes
1. This update is only for TOS 4.2.08 or later versions. If your TOS is 4.2.08 or an earlier version, please refer to here.
2. Under normal circumstances, the system update will not affect the data in your hard drives, but for your data safety, it is strongly recommended that you back up your data before the update!

How to update your TOS?

Online update:
1. Go to TOS > Control Panel > General settings > Software update;
2. Check the option "Online update", click "Apply";
3. Follow the prompt to finish the update;

Manual update:
1. Download the update package: Update package for ARM models(md5:8c7d646824ebd266079872abd97b68d4)
2. Go to TOS> Control Panel> General Settings> Update & Restore, and click “Manual Update”;
3. Click "Browse" to select the update package;
4. Click "Apply";

Issue report
If you encounter issue during using, please report to TerraMaster official forum “TOS update”.

[crisisacting]

{L_BUTTON_AT}StephenM

This is the update you've been requesting forever …

[macmpi]

1. Updated netatalk version to 3.1.15.

Thanks for the update: that was a very-long awaited security update for ARM platform: somehow reassuring that platform is still maintained, albeit not very frequently.

Any how, can you clarify this (shh log below)?

Code: Select all

$ netatalk -v
afpd 3.1.14 with CVEs fixed in 3.1.15 - Apple Filing Protocol (AFP) daemon of Netatalk
Fixed issues related to CVE-2022-43634 CVE-2022-45188

It does not seem to be full 3.1.15 as mentioned in release note, but rather a hacked 3.1.14, potentially leaving out many other bugfixes.

[onemeshnig]

6. Fixed the issue of being unable to customize wallpapers.

Finally!

[TMroy]

1. Updated netatalk version to 3.1.15.

Thanks for the update: that was a very-long awaited security update for ARM platform: somehow reassuring that platform is still maintained, albeit not very frequently.

Any how, can you clarify this (shh log below)?

Code: Select all

$ netatalk -v
afpd 3.1.14 with CVEs fixed in 3.1.15 - Apple Filing Protocol (AFP) daemon of Netatalk
Fixed issues related to CVE-2022-43634 CVE-2022-45188

It does not seem to be full 3.1.15 as mentioned in release note, but rather a hacked 3.1.14, potentially leaving out many other bugfixes.

This statement was added by our engineer, and it is clearly stated that it is a netatalk 3.1.14 with CVEs fixed in 3.1.15. Netatalk 3.1.15 is not able to run in ARM TOS 4.2 environment with kernel 4.14.

[macmpi]

This statement was added by our engineer, and it is clearly stated that it is a netatalk 3.1.14 with CVEs fixed in 3.1.15.

Good they did: thanks for adapting release note since.

Netatalk 3.1.15 is not able to run in ARM TOS 4.2 environment with kernel 4.14.

It is very strange & uncommon that such minor package version bump would suddenly break compatibility: there is no mention of specific kernel limitation or other dependency in netatalk 3.1.15 release notes...
I do not see any related issue opened in netatalk github: TM engineering should probably open one to get that resolved.
3.1.15 brings lots of other beneficial fixes, and maintenance would also be easier than cherry-picking fixes here & there.

[crisisacting]

It is very strange & uncommon that such minor package version bump would suddenly break compatibility: there is no mention of specific kernel limitation or other dependency in netatalk 3.1.15 release notes...
I do not see any related issue opened in netatalk github: TM engineering should probably open one to get that resolved.
3.1.15 brings lots of other beneficial fixes, and maintenance would also be easier than cherry-picking fixes here & there.

You are overlooking the fact that that GitHub is almost purely focused on the ×86/×64 release, not an AArch32/AArch64 release.

TOS 4 on ARM is running on an older kernel release with a mix of libraries from RealTek and some OpenWRT resources (per the last post in this thread); the latter has already removed netatalk on newer releases, so it should truly be appreciated that a Terra-Master developer managed to get a newer release with patches to function upon TOS 4.× instead of just dropping it outright.

RealTek may have already depreciated the RTL1296 SoC since most resources aren't publicly available/accessible, so libraries for newer Linux kernel releases may not even be available, which is possibly part of the reason that TOS 5 on the 210 series devices may not ever be released if the 211 series devices release cannot be backported because of that.

[macmpi]

You are overlooking the fact that that GitHub is almost purely focused on the ×86/×64 release, not an AArch32/AArch64 release.

No, netatalk is actively supported, even on ARM platforms.
Let's not try to claim very broad statement & theories on a very specific issue on such a minor revision.

When 3.1.14 works and 3.1.15 does not, then best-effort approach is to look for the very specific reason why: as netatalk is opensource project with active community, opening a detailed issue about it is very straightforward, and it is likely community may help fix the (unexpected) issue.
If that does not resolve it, then OK one may consider 3.1.15 can't run on that specific environment without a more significant involvement, which may/may not be worth it.
Just common sense practice I'm sure professional TM dev team has.

[TMroy]

You are overlooking the fact that that GitHub is almost purely focused on the ×86/×64 release, not an AArch32/AArch64 release.

No, netatalk is actively supported, even on ARM platforms.
Let's not try to claim very broad statement & theories on a very specific issue on such a minor revision.

When 3.1.14 works and 3.1.15 does not, then best-effort approach is to look for the very specific reason why: as netatalk is opensource project with active community, opening a detailed issue about it is very straightforward, and it is likely community may help fix the (unexpected) issue.
If that does not resolve it, then OK one may consider 3.1.15 can't run on that specific environment without a more significant involvement, which may/may not be worth it.
Just common sense practice I'm sure professional TM dev team has.

I have told you the truth. If we can, why don't we? It actually takes more time to merge 3.1.14 and 3.1.15 than to just apply 3.1.15.

[sianderson]

online update doesnt see the update from 4.2.41 (not sure what happened to 4.2.42)

but downloaded 4.2.43 and updated without any issues