similar to: 4.21-rc: ldb_version.h is missing

31.07.2024 08:30, Douglas Bagnall via samba ?????: > On 30/07/24 22:20, Michael Tokarev via samba wrote: >> When building libldb as public library, its install target does not >> install ldb_version.h header file, which is included from ldb.h, so >> the resulting header files are unusable. > > It may be that 625fb48326ec62a33ce0abdbfb0f6f3d33d7cc64 accidentally reversed

On 30/07/24 22:20, Michael Tokarev via samba wrote: > When building libldb as public library, its install target does not > install ldb_version.h header file, which is included from ldb.h, so > the resulting header files are unusable. It may be that 625fb48326ec62a33ce0abdbfb0f6f3d33d7cc64 accidentally reversed the logic:

On Sat, 2024-08-03 at 21:33 +0300, Michael Tokarev wrote: > 31.07.2024 08:30, Douglas Bagnall via samba ?????: > > On 30/07/24 22:20, Michael Tokarev via samba wrote: > > > When building libldb as public library, its install target does not > > > install ldb_version.h header file, which is included from ldb.h, so > > > the resulting header files are unusable.

I'm trying to build 4.21-rc packages for debian, and noticed that a new form of version info symbol appeared (only tried tdb for now). In addition to usual TDB.1.4.11 at TDB.1_4.11 symbol, it now also adds TDB_1_4_11 at TDB_1_4_11 (with dots replaced with underscores), but for single version only. It doesn't look right :) Thanks, /mjt -- GPG Key transition (from rsa2048 to

Hi all, After upgrading my first Samba AD DC from el7.4 to el7.5, I had the pain of being greeted with a non-fonctional Samba. When I used samba-tool, I was greeted with that message: root at dc00 ~]# samba-tool dbcheck ldb: module version mismatch in ../source4/dsdb/samdb/ldb_modules/acl.c : ldb_version=1.2.2 module_version=1.1.29 ldb: failed to initialise module /usr/lib64/samba/ldb/acl.so :

Samba 4.0.8, from the tarball, compiled with ./configure make sudo make install # /usr/local/samba/sbin/samba -b Samba version: 4.0.8 Build environment: Build host: Linux template.wetron.local 3.8.13.4-server-1.mga3 #1 SMP Thu Jul 4 14:04:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Paths: BINDIR: /usr/local/samba/bin SBINDIR: /usr/local/samba/sbin CONFIGFILE:

In the smbstatus output, "Locked files" section, there's a list of locked files (effectively opened files, since windows always locks a file which it opens) and corresponding pid of smbd process. How to map this information to user ID? Thanks, /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1

26.05.2024 13:13, Andrew Bartlett wrote: > On Sat, 2024-05-25 at 14:25 +0300, Michael Tokarev via samba wrote: >> Hi! >> >> I'm trying to find where various components of samba belongs to and where they're used. >> There are quite a few files with unknown purpose. For example, a cpython library >> (python code which is to be linked to from a C program)

With the new signature file I was able to verify, but there was still a bad signature: "gpg: key 0x0FC3042E345AD05D: 1 bad signature" which I highlighted below. Didn't seem to be a problem, but thought I'd point it out. I'd be glad to do additional tests if you'd like. $ gpg --list-keys /home/wink/.gnupg/pubring.kbx ----------------------------- pub

Hi! In the samba wiki there's this page: https://wiki.samba.org/index.php/Raising_the_Functional_Levels which basically says that the maximum supported functional level is 2008_R2, and that 2012 (and 2012_R2) are included but not supported. This page mentions maximum samba version 4.4 and has been modified in 2017 (besides some formatting changes). What's the current situation? Also,

06.06.2024 19:33, Michael Tokarev via samba wrote: > For quite some time I'm trying to find what's going on with MSDFS referrals. > Samba version is 4.19.6. .. > However, when opening the directory in question from client, this name is not > shown in the listing.? Samba skips this name from the listing when looping over > readdir entries: So, the same config just works in

07.06.2024 09:39, Stefan G. Weichinger via samba wrote: > I run 2 DCs at a site, Debian 12.5, so far samba-4.19.6 from backports. > > Today I upgraded one of them, this brought samba-4.20.1 > > Now on this one DC stuff like "wbinfo -g" fails: > > # wbinfo -g > could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE > could not obtain

Hi! This is a heads-up for now, more debugging to follow. I had to downgrade samba from 4.20.1 to 4.19.6 because 4.20 broke case insensitive file access entirely. Only exact case filename works, no matter which value is set in "case sensitive" parameter. In 4.19, things works again. /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key:

07.06.2024 19:27, Jeremy Allison wrote: > On Fri, Jun 07, 2024 at 04:59:29PM +0300, Michael Tokarev via samba wrote: >> It boils down to having wide links = yes (and unix extensions = no). > > Wide links is problematic. I'd love to just remove it :-). I don't see anything problematic in wide links. I'd say it's samba who views it as problematic (just like in a

Hi! I just uploaded binaries of samba versions 4.19.7-1 and 4.20.1-5 for ubuntu and debian to the usual location, http://www.corpit.ru/mjt/packages/samba/ . There are a few changes in there. First, I changed debian release suffix to be like: 4.20.1+dfsg-5~mjt-deb11 4.20.1+dfsg-5~mjt-ubt24 This should not change anything, just make it easier to track if neded, hopefully. And for 4.20

07.06.2024 10:13, Kees van Vloten via samba wrote: > There is a little difference with your config: I am not using symlinks in the filesystem but 'msdfs proxy' in smb.conf.? Not sure if that can be > related to your finding? msdfs proxy is not affected in this context. It is the access to msdfs-symlink *files* which broke. Thanks, /mjt -- GPG Key transition (from rsa2048 to

20.06.2024 15:16, Rowland Penny via samba wrote: > On Thu, 20 Jun 2024 15:07:11 +0300 > Michael Tokarev via samba <samba at lists.samba.org> wrote: > >> 20.06.2024 15:03, Michael Tokarev via samba wrote: >> Still, it'd be nice if samba-tool domain leave displayed some more >> appropriate error message, and no insecure-password-on-command-line >> warning

20.06.2024 17:01, Ralph Boehme wrote: > On 6/20/24 2:03 PM, Michael Tokarev via samba wrote: >> How to remove this machine from a domain? > net ads leave ... Yeah, I tried that one right after `samba-tool domain leave` - it complains there's no way to leave a domain if joined as a DC. I *guess* this is the error `samba-tool domain leave` faces too, just without proper error

07.07.2024 16:05, Sonic via samba wrote: > On Fri, Jul 5, 2024 at 3:55?AM Michael Tokarev via samba > <samba at lists.samba.org> wrote: > ... >> Please don't suppress *NEWS* entries. > ... > > As someone that was bitten by this change I have to admit I've never > seen these NEWS entries, or never realized I had. My Debian servers > are cli only (no X or

08.07.2024 17:18, Sonic wrote: > On Mon, Jul 8, 2024 at 6:46?AM Michael Tokarev <mjt at tls.msk.ru> wrote: > ... >> I think the main ingredient here is to have apt-listchanges package >> installed (which, while part of standard install, is optional). > ... > > I've always installed using the netinstall.iso which does not install > that package. Will add it