valid users has no effect on share visibility.
Do you perchance have a regular share called
administrator or something like that?
That’s somewhat correct. Manual changes to files in
/etc/… that contain the template warning will be overwritten, that’s right. You could change the templates the files are generated from, though. They’re located in
/etc/univention/templates/files. The drawback is that you’ll have to migrate those changes whenever the originals are updated via package updates. Therefore it’s highly preferable not to modify those templates.
To me this looks like a bug was fixed in Samba. On my UCS 4.3 servers the user home is still visible even though the share’s
browseable setting is set to
no. On my UCS 4.4 servers, though, the share isn’t visible anymore, even though the definitions of the
[homes] share hasn’t changed.
browseable = yes only causes a share called
homes to be shown, not a share by the user name.
man smb.conf reveals the following in the section about the
The browseable flag for auto home directories will be inherited from the global browseable flag, not the [homes] browseable flag. This is useful as it means setting browseable = no in the [homes] section will hide the [homes] share but make any auto home directories visible.
Unfortunately this doesn’t make much sense either as the same
man smb.conf states that the
browseable flag is a share-specific flag, not a global one. Adding insult to the injury is that adding
browseable = yes in the
[global] section doesn’t change a thing.
Either I completely misunderstand the man page, or there’s simply a bug there.
Anyway, I don’t think you can get Samba to re-display the auto-created home share at the moment.