Why allow “everyone” to have read write permission to shared folders in order to run container manager? Wouldn’t this be insecure?
Why allow “everyone” to have read write permission to shared folders in order to run container manager? Wouldn’t this be insecure?
To add to this, SMB implementations on Linux today simply respect the archaic model MS developed for LAN Manager (Windows 3.1, 1980’s), before Windows had local user permissions (NT 3.51 mid 90’s).
MS saw share permissions as a mechanism to provide admins some level of control for the small networks.
Once NT became the standard in business, we started ignoring share permissions and just letting file system permissions manage everything (since that could be managed via domain credentials).
It’s a whole lot easier and more secure to manage Groups in the Domain than a bunch of share permissions, and they’re lots more granular.
So we’re stuck with share permissions though they’re not all that useful - so most people (everyone?) simply ignore them and use just file system perms, which you have to manage even without shares.
TL:DR Share perms are a legacy thing and can simply be set to everyone read/write