search for: vetoing

Since the list responsiveness seems to be at a high, le me take the opportunity to repost a message that got no answers in March: I've searched the list, and I can't find reference to this being implemented: reverse veto files - a list of files *allowed* rather than the current list of files *denied*. Possibly implemented by just allowing a ! in the veto files directive. eg: veto

Im currently having a very long list of veto files, just to be sure that the people ONLY can write documents and styleshets. Is there any plan to have a "reverse veto files" to ONLY allow this type of file? Because when I have a lot of veto files the samba gets too slow, even if it dosen't use regex, with regex i would be able to do the reverse veto. But without regex and without

Hello- I upgraded Samba from 4.6 to 4.8 on a FreeBSD 11.2 server. After the upgrade, users cannot access the HOME folder share but they can access other shares just fine. I am using the RID backend on this member server that connects to Windows-based domain controllers. I apologize for the lengthy smb4.conf but here it is: #======================= Global Settings

Hi people, im new on the list. I have a samba 3.0.10 working as a PDC with roaming profiles for win2003 clients. The problem is that the windows 2003 uses a lot of desktop.ini "hiden files" that when i save this on my roaming profile and i log back in for the second time i lost this "hiden bit" on the desktop.ini files and i see them everywhere. Even on the

Hi guys, I use "veto files = /.mp3/.mpg/" etc. on the [homes] share to prevent users from storing media files on a Samba server in the home directories. My client now wishes to make this restriction apply to users who are members of only certain groups. E.g. This restriction must apply to users who are members of the "Students" group and not apply to users in the

Hi ! I would like to remove from listing the "Icon?" files created by mac user when they customize their folder icon. So I did in my smb.conf : veto files = /Icon?/ ok it's working, but "Icone" "Iconx" "Icons" will be removed too. I tried veto files = /Icon\?/ but it's not working, Is there a way to use question mark (?) but not as a wild-card ?

Our current environment is Samba 3 with an LDAP backend. I want to move to Samba 4 with an AD backend. We already have the AD servers in place and Samba 3 servers are using AD absolutely perfectly. The last remaining piece is to move Samba 3->4. My existing Samba 3 configuration looks like this: [global] server string = 1220 Boothost Server netbios name = BOOTHOST-1220

While working on my existing member file server smb.conf config file I found an entry for "veto files" like the following: veto files = /.bash_logout/.bash_profile/.bash_history/.bashrc/ The "man smb.conf" entry says: veto files (S) This is a list of files and directories that are neither visible nor accessible. Each entry in the list must be

How can I *veto* dot files? The naive approach of using /.*/ fails in so far as no file at all appears on the NT side :-) Hiding isn't enough for me, as I do want to see all hidden files on the NT side of things - I just don't want to see the Linux dot files on the NT side. This is Samba 2.0.6 (RH6.2) with the below configuration. TIA, Stefan ************ # Samba config file

linux 2.2.19/rh6x I use in a share veto files = /.*/ whenever you connect to it the client process hangs, the smbd starts consuming cpu time and cannot be killed but with "kill -9". This is the last part of the smbd log [2002/05/16 05:49:51, 3] smbd/sec_ctx.c:set_sec_ctx(319) 3 user groups: 100 6 19 [2002/05/16 05:49:51, 3] smbd/trans2.c:call_trans2findfirst(863)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, I'm using Samba 3 on a Debian 5.0 (Lenny), the package is version 3.4.7 (from Debian backports, the full version 2:3.4.7~dfsg-2~bpo50+2). We use some 'veto files' on our shares to avoid users to have multimedia files (movies, mp3 and so on). Now we have a true demand to allow certain users to store corporate videos (about our

from the man page. I've never tried veto oplocks. But it looks like something that might be useful... > veto oplock files (S) > > This parameter is only valid when the oplocks parameter is turned > on for a share. It allows the Samba administrator to selectively > turn off the granting of oplocks on selected files that match a >

I have been using the "username map" parameter for some time on various versions of Samba 2, and it has worked nicely. Last week I upgraded to Samba 3 and integrated with Active Directory. Since I am using Solaris 8, and "nsswitch.conf" doesn't support winbindd, I am using the "add user script" parameter to add users. What is happening is that users in

I am running RHES 3.0 with Samba 3.0.22 and Open Ldap 2.1.22 ldapsam and when I use User Manager for Domains and try to change a user password as root or any other Domain Admin account I get the following error: "The following error occurred changing the properties of the user jcampbell. The group name could not be found." When you look at groups under user manager Domain Users is set

I've been playing around a little bit with the "veto files" option for the [homes] shares we have on our Samba servers (2.2.1a & 2.2.3a). I've discovered that: veto files = /.*/ works marvelously for not letting the users muck with their .dotfiles, which is exactly what we want, however, I've also discovered that it also clobbers the special directory entries

Hi, there I have a question about Veto files in smb.conf: Can we use this option to hidden files not belonging to myself in a shared folder? If not, how do we implement this functionality in Samba? Thanks, Allen

We're running Samba 2.2.2 on an RS/6000 (AIX 4.3.3) using Windows 95 clients. We've tried the "hide files" and "veto files" option in smb.conf, but when the shares are mapped, we can still see the contents in Windows Explorer. We used the wildcard for all the contents of the shares (ex. hide files = /*.*/). The Samba manual only makes reference to Windows 98, so

Good night. I am behind a way so that in my backup share it is possible to only write files in the format of the application that I use to execute the backup routines, for this I searched the internet for a solution that works like Allow Files, however it is Complicated to find. Talking on forums a user informed me that he could use the parameter to follow in smb.conf, however in my tests it did

Hi, I am running the latest Samba (p8) on Solaris 2.6. The PC clients are running win95 OSR2. I am using encrypted passwords. I have some files vetoed: veto files = /.rssrc/.desktop/ I'm not using 'hide dot files'. If I have a folder with one file in, and that file is a vetoed file, I cannot delete the folder. I have unix permissions to delete both. The windows error message is:

Hi all.. I'm update my samba, from 2.2.8a to 3.0.2a, and now my 'veto oplock files' do no work... I set my option like this: veto oplock files = /*.mdb/*.MDB/ but after the first user open our software (that opens a file .mdb in a samba share) the second user can't open... he gets the error message: 'Couln't lock the file' Even setting all locking options = no, the