My Cloud Home Firmware 9.7.0-104 Release Notes. Samba 4.17 backported to Debian 11

My Cloud Home My Cloud Home Single Bay
1

Samba 4.17 backported to Debian 11 WD OS4 with Samba version 4.17.12+dfsg-0+deb12u1~bpo11+1 to resolve CVE-2023-4154. Previous Samba 4.13.13+dfsg-1~deb11u5.

My Cloud Home Firmware 9.7.0-104 Release Notes

Version: 9.7.0-104

Release Date: 12/9/2024

Supported Devices: My Cloud Home, My Cloud Home Duo

Updates In This Release

  • Updated open-source Samba package to version 4.17.12+dfsg-0+deb12u1~bpo11+1 to resolve CVE-2023-4154 that exposed passwords and secrets to users with privileges and Read-Only Domain Controllers.
  • Updated open-source curl package to version 7.74.0-1.3+deb11u13 to resolve CVE-2023-38545 that crashed curl application because of heap-based overflow and CVE-2023-38546 which allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met.
1 Like
3

Very good performance with SSD, 118 MBps with multithreaded sequential read write, may have optimization with large socket buffers and data caching before flush to disk

# Cache data before flushing to disk:
  write cache size = 2097152
  min receivefile size = 16384
  getwd cache = true

History of the last 6 OTA to the My Cloud Home is available in the OTA log

Imgur

4

This update broke 2/3 of my MyCloud Home’s.
I can see them on the web and app, however on latest Windows 11, it throws an error, that it cannot find the network path.
And no, simply clearing device settings did not solve it, neither did disabling and re-enabling local accounts, nor deleting credentials in credentials manager nor restarting file explorer, nor restarting the computer twice, nor did creating a completely different login + pass combo on the web interface.
It detects when mapping network drives via IP rather than it’s network name, but it won’t let me log-on, saying that my system doesn’t allow insecure guest log-ons. Flushing DNS cache didn’t do anything either, neither did switching DNS provider.
Incidentally, it is the 2 only ones with Plex Server on it, the 3rd working one, doesn’t have Plex Server on it.
Has anybody else got a similar experience, do any of you have any ideas?

5

What you have described may have nothing to do with FW 9.7.0-104 but rather it is coincident with Windows 11 24H2 update.

Have you tried disabling Win 11 24H2 SMB signing?

After 24H2 Update - #2 by NoPlex
This has been circulated for a few months on the Microsoft techcommunity, try #6 Disable the SMB client signing requirement.
Solution
Possible related Windows 11 24H2 Security Changes

6

You are right in fact it worked, after I followed the steps in the links you provided. For all other users having a similar issue, I am using Windows 11 Pro and I enabled SMB 1.0, changed both group policy settings, and simply used the broadcasted MyCloud Home network drive that was populated under Network in File Explorer.

1 Like