similar to: [Announce] Samba 4.10.13 Available for Download

Release Announcements --------------------- This is the latest stable release of the Samba 4.11 release series. Changes since 4.11.5: --------------------- o Douglas Bagnall <douglas.bagnall at catalyst.net.nz> * BUG 14209: pygpo: Use correct method flags. o David Disseldorp <ddiss at samba.org> * BUG 14216: vfs_ceph_snapshots: Fix root relative path handling. o Torsten

======================================================== "Tell me and I forget. Teach me and I remember. Involve me and I learn." Benjamin Franklin ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.11 release series. Changes since 4.11.3: --------------------- o

======================================================== "Tell me and I forget. Teach me and I remember. Involve me and I learn." Benjamin Franklin ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.11 release series. Changes since 4.11.3: --------------------- o

Hi, trying to revert 4.8.0/1 issues with sambaundoguididx and getting following: Traceback (most recent call last): File "/root/sambaundoguididx", line 66, in <module> db.modify(modmsg) _ldb.LdbError: (32, 'ldb_wait from (null) with LDB_WAIT_ALL: No such object (32)') A transaction is still active in ldb context [0x56060ac2a310] on

Hi everyone, I like to connect azure ad to my samba4 installation via AD Azure Sync (with password passthrough authentication). Passthrough authentication and User synchronizations working with a Windows 2016 domain member server without any harm. But group membership synchronizations fails always because AD Azure Sync cannot parse the member attribute (reference-value-not-ldap-conformant).

Posted some time ago on 4.6 - updated it to 4.10.13-1 as released by IBM. Added a Kerberos configuration file, updated smb.conf, changed the startup order to nmbd first, winbindd next, then smbd. Now nmbd and smbd start, while winbindd does not. Content from log.winbindd: [2020/04/18 00:00:17.100243, 0] ../../source3/winbindd/winbindd.c:1731(main) winbindd version 4.10.13 started.

Posted some time ago on 4.6 - updated it to 4.10.13-1 as released by IBM. Added a Kerberos configuration file, updated smb.conf, changed the startup order to nmbd first, winbindd next, then smbd. Now nmbd and smbd start, while winbindd does not. Content from log.winbindd: [2020/04/18 00:00:17.100243, 0] ../../source3/winbindd/winbindd.c:1731(main) winbindd version 4.10.13 started.

Please disregard unless this conclusion is wrong. We would be running in AD mode, not NT4 mode with Server 2016. Regards, Bob Wyatt From: Bob Wyatt <bwyatt_sub at comcast.net> Sent: Tuesday, April 21, 2020 4:32 PM To: 'sambalist' <samba at lists.samba.org> Subject: Samba 4.10.13-1 as a domain member, AIX 7100-05-05 In perusing Red Hat manuals for a

In perusing Red Hat manuals for a different issue with Red Hat, this was in their RHEL 7 documentation: You can run Samba as: * An Active Directory (AD) or NT4 domain member * A standalone server * An NT4 Primary Domain Controller (PDC) or Backup Domain Controller (BDC) NOTE Red Hat supports these modes only in existing installations with Windows versions which support NT4 domains.

I am working on a FreeBSD jail (12.1p4) using samba410. I have joined this service to our existing Samab DC DOMAIN using samba-tool domain join. This worked as far as I can tell. I have these entries in smb4.conf # BOF # Global parameters [global] netbios name = SAMBA-02 realm = BROCKLEY-2016.HARTE-LYNE.CA server role = active directory domain controller workgroup = BROCKLEY-2016

======================================================== "Success is simply a matter of luck. Ask any failure." Earl Wilson ======================================================== Release Announcements --------------------- This is an additional bug fix release to address bug #14175 (CTDB: Incoming queue can be orphaned causing communication breakdown). Please see

======================================================== "Success is simply a matter of luck. Ask any failure." Earl Wilson ======================================================== Release Announcements --------------------- This is an additional bug fix release to address bug #14175 (CTDB: Incoming queue can be orphaned causing communication breakdown). Please see

The patch titled Subject: ufs: don't flush page immediately for DIRSYNC directories has been added to the -mm mm-unstable branch. Its filename is ufs-dont-flush-page-immediately-for-dirsync-directories.patch This patch will shortly appear at

On 03/11/2019 11:37, Michael Lueck via samba wrote: > Greetings Samba team, > > It has been a long time since I needed to ask a Samba technical question. > > Server and workstation are both running the latest Samba packages via > Ubuntu 16.04 LTS. I recently applied the security updates... actually > that was yesterday I applied them. > > >> samba

Hi, I'm setting up NUT on a raspberry pi 4, following the guide here: https://melgrubb.com/2016/12/11/rphs-v2-ups/ OS version: Raspian Buster NUT version: 2.7.4.8 Installed via: apt package install Device: Legrand Keor Multiplug connected via USB The problem I am experiencing is that *NOTIFYCMD* never runs. I can connect to the device via *upsc*, and I receive WALL messages when I connect

>I just went through the same issue. Take a look at my thread. >Double check that upsmon.conf:NOTIFYCMD /sbin/upssched is not still commented. Thanks for the response, can you link to it? I'm not finding it in the search. I'm not using /sbin/upssched, I have NOTIFYCMD set up as: NOTIFYCMD /home/pi/Documents/scripts/ups-log.py and it's not commented out. On Tue, Feb 11, 2020

Hello. Samba 4.1.0pre1-GIT-aad669b, joined as a DC to an existing domain. At least 6 accounts behave like this: Kerberos: AS-REQ techgroup at KLIN.KIFATO-MK.COM from ipv4:192.168.1.31:33822 for krbtgt/KLIN.KIFATO-MK.COM at KLIN.KIFATO-MK.COM ldb: ldb_trace_request: SEARCH dn: <rootDSE> scope: sub expr: (&(objectClass=user)(userPrincipalName=techgroup at KLIN.KIFATO-MK.COM)) control:

Release Announcements --------------------- These are security releases in order to address the following defects: o CVE-2019-10218: Client code can return filenames containing path separators. o CVE-2019-14833: Samba AD DC check password script does not receive the full password. o CVE-2019-14847: User with "get changes" permission can crash AD DC LDAP server via

Release Announcements --------------------- These are security releases in order to address the following defects: o CVE-2019-10218: Client code can return filenames containing path separators. o CVE-2019-14833: Samba AD DC check password script does not receive the full password. o CVE-2019-14847: User with "get changes" permission can crash AD DC LDAP server via

The Wine development release 5.19 is now available. What's new in this release (see below for details): - Wine Mono engine updated to 5.1.1, with WPF text formatting support. - KERNEL32 library converted to PE. - DSS cryptographic provider. - Windowing support in the new console host. - A number of exception handling fixes. - Various bug fixes. The source is available from the