similar to: LDAP authentication without Samba schema

On Fri, Sep 04, 2015 at 12:05:56PM +1200, Andrew Bartlett wrote: > On Wed, 2015-08-12 at 06:18 -0700, John Hixson wrote: > > Hi, > > > > I am in a position where I would like to have LDAP authentication for > > CIFS shares, but cannot modify the LDAP server. The LDAP server is > > Open > > Directory and does not have the Samba schema included or configured.

On Wed, 2015-08-12 at 06:18 -0700, John Hixson wrote: > Hi, > > I am in a position where I would like to have LDAP authentication for > CIFS shares, but cannot modify the LDAP server. The LDAP server is > Open > Directory and does not have the Samba schema included or configured. > I > only have read only access, a keytab, and possibly a read only bind > user. Is this

I am getting a bit confused about which methods to use to keep my passwords synced given the following scenario. Samba PDC using LDAP backend. LDAP uses {SASL}princ@REALM type passwords Sasl mechanism is saslauthd using kerberos5 I can use pam like: password required pam_smbpass.so password required pam_krb5.so use_first_pass and then passwd will set both passwords but how can I make it

I have a Synology NAS array appliance. It is linux based and uses samba for file sharing. Normally the config is done via a gui interface but you can ssh to the array. The domain controllers are running Samba 3.6.x in classic domain mode. I have member servers running 3.6.x and 4.3.8. no problem. I recently updated the Synology "OS." The current version of samba is

hello My windows client is a an ldap server member with an example.com domain. When we try to connect to the samba server, shared folders are visible correctly, but it's not possible to connect users. my smb.conf [global] workgroup = WORKGROUP netbios name = hpds security = user map to guest = Bad User dns proxy = no server string = %h server log level = 0 max log size = 10000 load

On both the synology (samba 4.1.20) and PDC (samba 3.6.25) testparm showed client schannel = Auto server schannel = Auto I don't know if the server even supports schannel. Maybe it doesn't any all the clients successfully negotiated not to use it. On the synology, I set client schannel = no This fixed my domain membership issue. Although

On Fri, Mar 24, 2017 at 12:47:51PM +1300, Andrew Bartlett wrote: > On Thu, 2017-03-23 at 16:23 -0700, John Hixson via samba wrote: > > Are there plans to migrate the samba python code to python3? If so, > > is > > there a roadmap? If not, why not?  > > There is work ongoing for this, thanks to a number of patient and > persistent engineers at Red Hat. > > It

I am absolutely loathe to necro a thread like this so far in the future but that's kind of the point here... It's 2019 and as much as I've tried (everything in this thread and more... like trying some weird trickery with pam_exec), I can't figure this out. I have clients with huge and elaborate OD environments that I absolutely would never have access to the terminal/desktop of,

Are there plans to migrate the samba python code to python3? If so, is there a roadmap? If not, why not? -- John Hixson iXsystems Enterprise Storage & Servers Driven By Open Source

Hi, Here is my desired configuration: An external LDAP server, Samba 4.1.8 (not configured as a member server or as a domain controller), and SSSD configured with the external LDAP server. Authentication locally and via ssh works fine using pam_sss.so. When attempting to authenticate a share on windows using an LDAP users credentials, the request fails with NT_STATUS_ACCESS_DENIED. I'd like

Dear all, I downloaded samba3.0-alpha21 and followed each step in "ADS-HOWTO.txt". But mapping a network directory from a Windows client failed (step 4: Test your server setup). (Succeeded in other steps.... Including step 5) Only local users in the samba server can access the share folder. (Please refer to the smb.conf listed below...) And "#kadmin -p administrator" fails

samba-3.0.21c, heimdal-0.7.2 The heimdal documentation[1] talks about a samba integration when both samba and heimdal are using ldap as their backends. I quote: "Now you can proceed as in See Using LDAP to store the database. Heimdal will pick up the Samba LDAP entries if they are in the same search space as the Kerberos entries." There is absolutely no further documentation. I tried

hi, all, I'm using MIT-krb5 and it seems it's not quite stable. Everything seemed fine and krb5, samba daemon started as well unless I tried to use "ad\xxx" to login a windows7 machine. Here is part coredump log, :Sep 25 15:08:54 pdc.ad.pthl.hk samba[2579]: /usr/sbin/krb5kdc: krb5k= dc: starting... :Sep 25 15:11:56 pdc.ad.pthl.hk samba[2579]: /usr/sbin/krb5kdc:

We run Apple's OD to support our Linux, Mac, and Windows clients and servers. We are under pressure to use AD because more and more software coming out for Windows requires it. We don't want to use AD, so Samba4 looks good. However, we don't want to pull apart our directory to implement samba4. Is there a way to get Samba 4 running so that it is able to use the existing LDAP and

Hi, When I have a service on a client that tries to use kerberos and I get errors such as these in the log.samba file: Kerberos: UNKNOWN -- host/ubuntu-test.mydomain.net @ MYDOMAIN.NET: no such entry found in hdb Does this mean that the kerberos authentication system is looking for the principal "host/ubuntu-test.mydomain.net @ MYDOMAIN.NET" in samba4's domain or in the

On Mon, Mar 27, 2017 at 12:26:35PM +1300, Andrew Bartlett wrote: > On Fri, 2017-03-24 at 08:04 -0700, John Hixson via samba wrote: > > On Fri, Mar 24, 2017 at 12:47:51PM +1300, Andrew Bartlett wrote: > > > On Thu, 2017-03-23 at 16:23 -0700, John Hixson via samba wrote: > > > > Are there plans to migrate the samba python code to python3? If > > > > so, >

Hi everyone, A quick question: Is check password script option working for ad dc setup? I believe, ad on it's own cannot provide password protection against dictionaries.

Hello, I have multiple samba DC for different domains running on a single box. I read a little bit up on time synchronisation and now configured it. It seems to work. My question is, what happens when multiple DCs go to the same ntp_signd/socket, will it work? Or should I configure one socket per DC instance? Cheers, Thomas

I've been installing OpenSSH 2.9p2 onto several RedHat Linux machines, after compiling in the GSSAPI/Kerberos5 patch from here: http://www.sxw.org.uk/computing/patches/openssh.html I've been using ssh both to let users in via passwords and Kerberos tickets, and both have been working fine... except for one irritating machine, which (for no good reason I can see) fails when using kerberos

How do I sync whem. I have tryied out this in my smb.conf unix password sync = yes passwd program = /usr/sbin/kadmin -l passwd %u passwd chat = "*Password:*" %n\n "*Password:*" %n\n "*" But then i try to change a passwd in windows it rejects it, and telling me that I dont have permissing to change the passwd. Anyone solved this issue?