Many security_mode=share issues here, what's the problem?

I have been dealing with support re this.

Please see the latest update from L3 Engineer: I debugged this issue again in 4.1.10 yesterday. After ReadyNAS firmware upgrade from 4.1.8 to 4.1.10, the samba model also upgrade from 3.0.37 to 3.5.16. If user created a new share when NAS run firmware 4.1.10, it would add a new property for the share. Below is the key information: nas-06-3F-A6:/etc/samba# cat smbpasswd test-4.1.8:1003:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:[NU ]:LCT-00000000: test-4.1.10:1004:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:[NDU ]:LCT-00000000: #　which means samba disallow user access this share. If you edit this configuration file delete parameter “D”, restart the samba, then it would be access without password. I did not know whether this is samba 3.5.16 issue or our NAS FrontView issue. My colleague told me the NAS and Samba 3.5.16 has some compatibility issue when it worked “Share” mode. Our recommend solution is changed to “User” mode, and most of our user accepted our suggestion. I am sorry I give you unclear information, because the ReadyNAS NV+ 4.1.10 is stable firmware, I did not know when we will release a new firmware, so I give you a unclear feedback. Now there are 2 solutions: Now there are 2 solutions: 1. Changed to “User” mode, 2. Edit the /etc/samba/smbpasswd configuration file and delete the parameter “D”, then it would be worked. - Question: Why the share be create in 4.1.8 can be access without password? - Answer: because when NAS worked in 4.1.8, and user create a share, it has not parameter “D”, so it can be work.

I replied that what would be better would be to find what is incorrectly putting the "D" there and fixing it.

In the mean time, if you want to use 'Share' mode go back to 4.1.8.

I'm holding my breath...