similar to: Modifying ACL's from client without using winbind

Dear all, I am struggling around with Windows ACLs and cannot find a solution nor how to troubleshoot that. I have two samba3 hosts. Hostname "donald" is my domain controller with samba 3.x + OpenLDAP server running. Hostname "pluto" is my other samba 3.x server which was joined to my domain. I use LDAP for my users+groups. I dont have winbind on my machines. On hostname

I modified the CUPS access rights (defined in cupsd.conf). Before that only users of administrative group had access to the printer configuration parts. Now I removed all access restrictions, so that anyone can access all CUPS services (printers, jobs, ...) (we use this, because sometimes we need to hold printers manually ...). But, as I mentioned, I don't find the relationship between this

Hi, I'm getting confused about the role that kerberos authentication plays. What exactly is the point of using kerberos to join a samba server to an AD domain? If using kerberos still requires you to rely on winbindd for all the nsswitch stuff then what is the point? I can just as easily specify workgroup = wkgrp security =

passdb appears a lot of times in smba logs, even if it uses LDAP as a backend, as in my config. Maybe the log message should be changed in the code for something easier to debug... But this error message you said, only appears if you try to add or delete the user twice from LDAP, so you should remove "-a" from the add user script and comment out the user delete script if you intend to

I noticed a while back in the lists that there was mention of supporting zfs' nfs4v acls. Does anyone know if this made it into 3.0.25pre1? Thanks, Christian McHugh Northern Arizona University

Hi all *Context:* I'm trying to use the s4bind scripts ( http://linuxcostablanca.blogspot.com.es/p/s4bind.html) k5start is running So far, i've succeeded in * modifying (posixifying) the built-in "Domain Users" * adding a user to this group and i can login with this user (ssh), create files that are correctly owned, etc... The user also shows up correcly in ADUC. * retrieving

Release Announcements --------------------- This is the sixth release candidate of Samba 4.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. In this release candidate, we have a significant number of improvements to our Access Control List (ACL) code,

Release Announcements --------------------- This is the sixth release candidate of Samba 4.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. In this release candidate, we have a significant number of improvements to our Access Control List (ACL) code,

Running into a lot of people upgrading to the 3.0.6 package that all of a sudden begin to experience the "Failed to verify incoming ticket!" errors etc., that are generally associated with a kerberos package incompatibility. However many of these people are running later versions of kerberos *and* reverting to a previous version of Samba appears to fix the issue. Is there something new

Hello, have some little problems adding user to domain with USRMGR.EXE My System runs on SuSE 9.1 (2.6.5-7.75-default), samba-3.0.4, smbldap-tools-0.8.5, openldap2-2.2.6 If I try to add a new user with USRMGR.EXE I get an error "Access denied", but if I look into LDAP the new user was correctly added to LDAP. If I confirm the error-message and then cancel the "NEW USER"

I have a samba3 server (ubuntu, 3.4.7) joined to a samba4 that has been working very nicely but today I got errors: net ads testjoin says the join is OK, but wbinfo -t says checking the trust secret via RPC calls failed Could not check secret and winbind logs on that machine (samba3) says: lsa_lookupsids call failed with NT_STATUS_NO_MEMORY - retrying... However, another samba3 machine

Hi all, The part that I don’t understand is why the behavior is different when there are ACLs involved. Take the below example: # This share is chmod 777, [share1] path = /srv/share1 # mode is 0777, no ACLs readonly = no create mask = 0660 [share2] path = /srv/share2 # mode is 0770, ACLs readonly = no inherit acts = yes create mask = 0660 share1 acts exactly as expected — I get a 0660

Why isnt anybody thinking about ldap? Pam_ldap in special. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Christian Naumer via samba > Verzonden: woensdag 24 mei 2017 13:43 > Aan: Rowland Penny; samba at lists.samba.org > CC: Daniele Bernazzi > Onderwerp: Re: [Samba] samba 4 in AD 2008R2 without

That was a good hint! Yes, I've installed SP2, and it realy seems to be the Problem. Now I've checked that on a machine with SP1 - and the jobs from the same printqueue are removed correctly there! -------- Original Message -------- Subject: Re: [Samba] Samba 3.0.9 doesn't remove printjobs ? (14-Dez-2004 19:13) From: novosirj@umdnj.edu To: t.pompe@architekt-prinz.at >

Hi Denis, on both samba hosts (donald and pluto) these commands work great: id johndoe getent group getent passwd My pluto:/etc/nsswitch.conf looks like that: [...] passwd: compat ldap group: compat ldap shadow: compat ldap [...] I want to add, that the described problem works fine if I try it on a share on "donald", my domain controller. The users are

Hi, I have discovered a bug when using CIFS mounted shares from Samba4 on a Linux machine. We use custom ACLs to allow certain groups extra access to home shares, setting 'user:staff:r-x' using setfacl, along with the related 'default' ACL so that it propagates to newly created directories. For this to work, we also set 'mask::rwx'. These shares have group and other

Hi, Am running Samba 3.3.7 on FreeBSD 7.1. All Windows clients (W2K & WXP) can connect fine but cannot connect any OS X clients (version 10.4 & 10.5). These OS X client receive an error message saying it cannot connect. The log indicates the following: [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(40) =============================================================== [2009/09/04

Thanks to some of the guys on #samba-technical (obnox in particular!), I now have a working samba configuration. The environment: In our setup each user has an entry in both openldap (no samba schemes) and AD. Each account has the same name and even has a Unix UID entry in AD. Our users ssh into Linux boxes, authenticating off of openldap. Files are shared via samba. Due to the account

Hello folks, I have some directories within a samba 3.x share which I want to give granulated security settings for various users and groups. I could use of course "setfacl" and POSIX ACLs to accomplish that, but some of these ACL should be also able to be set by some users. These users of course has no access to my linux host where samba3 is running, so they only can do that by

Hello Marco, I am speaking about POSIX ACLs, yes. When I create a file via shell I get a 660 file. When I create a file via Samba I get a 770 file. I don’t understand why they would be different. Without ACLs shell / Samba created files get consistent permissions. Christian > On Dec 20, 2018, at 12:29 AM, Marco Gaiarin via samba <samba at lists.samba.org> wrote: > > Mandi!