Yes, but we have to wait and see.
What keeps on the top of my head still is, why we just can keep using the unit if is not Remote Access activated?
Besides the factory reset script, I mean if root cause is be exposed and somehow we can assure that we’re not exposed somehow (port filtering, something else)
Why is a solution to change the drive? I just dont get it, sorry.
MBL in my case serves as a network share for multimedia and its backed up somewhere else regulary.
Thats why I stay sceptical to WD statements…
Agreed. The opportunity and offset in cost to simply shift units of new NAS models as replacement (even with reduced profit) is the preference when a patch to switch all outbound & inbound traffic would be welcomed by users not hit by the problem.
I’ve also asked WD the question on Twitter regarding a code fix / patch to make the MBL’s LAN only, but thus far they haven’t replied to that suggestion.
My guess is what I said above. New unit at reduced cost. The cost will be the straw that breaks my back if it’s too high for being forced to bin 2 perfectly functional bits of kit. Well, until this fiasco anyway…
If you put stuff in the private share you get a mapped drive on your Windows login via the desktop app and you can just drag and drop etc. And use via the mobile apps
The public share is accessible over the network generally via a unc path
Upshot is I have to store music in one place for Sonos to browse over the LAN , and all other stuff in the private share to access through the mapped drive and app
Maybe there’s a better way but if there is then I haven’t found it yet…
I heared a lot of good things about Synology, but also a few bad things like security vulerabilities.
After this vulnerability, I would not trust a device once the firmware is EOL, even if the vendor has a good reputation
Actually, they charged me nothing and they, not me, ran the software. I’ve read the BBB reviews you posted. I did not buy any software and certainly didn’t run the software itself. No billing or warranty problems. Hey, it worked and I shared my experience. Stellar in my experience dedicated hours to my project.
I too would be happy with a firmware update that simply makes the device LAN only, no WAN or Internet connectivity whatsoever.
However, I suspect they’ve decided that there is less liability in providing replacement drives at a discount than releasing a firmware update that still might not be fully secure. I’m amazed that they’re offering data recovery to affected users, so props to them for that. Maybe they’ll surprise us with new firmware as well.
I’m interested to hear what the trade-in offer will be, but the current My Cloud Home devices don’t appear to be as functional as I would like. Maybe the My Cloud Expert devices will be an option. I’m leaning more towards a Synology DS220+, although that would be a significant unplanned investment.
Well, my data hasn’t been deleted, I was lucky and gotten it offline. But wd’s site doesnt show I registered it, and I am not lucky enough to have my receipt of purchase… so even if I wanted to trade it in, I’m sure they wouldnt do it… so I’ll be looking for a replacement. Guess I should feel lucky my data is still intact.
By the way, what I really LIKE about the MBL is that you can change files on your system and they stay. For example things like /root/.ssh keys or hotfixes like the ones we did.
On the MyCloud EX2, all system files get reverted when you boot it… good for defending botnets/malware, but bad for custom stuff! (Or is there a trick to make permanent file changes to the EX2 ?)
I had been meaning to replace my MBL with a DS220+ and this incident has finally prompted me to get one (with a Seagate HDD). I should have done this years ago. I love it already. It really shows just how pitiful WD’s "NAS"es are.
