similar to: patch for 2.2.5 and check for start_tls with OpenLDAP 2.0.x libs

When building the mini initrd, previously we copied the modules into the initrd as-is, so for example if the module was xz-compressed, we copied the foo.ko.xz file to the initrd. This requires that the mini init binary is linked to zlib & lzma, so that it knows how to uncompress these modules when insmoding them at boot time. Also since the init is statically linked, it required _static_

I've just built samba debs from 2_2 head. looks like all is cool except pam_smbpass.so Jul 25 17:44:42 bitc passwd[18770]: PAM unable to dlopen(/lib/security/pam_smbpass.so) Jul 25 17:44:42 bitc passwd[18770]: PAM [dlerror: /lib/security/pam_smbpass.so: undefined symbol: ldap_value_free] Jul 25 17:44:42 bitc passwd[18770]: PAM adding faulty module: /lib/security/pam_smbpass.so ldd

Newbie trying to install wine in his Mac OSX, getting the old annoying message, home:~/Desktop/wine G3$ /Users/G3/Desktop/wine/tools/wineinstall WINE Installer v0.75 Running configure... configure: creating cache config.cache checking build system type... powerpc-apple-darwin8.7.0 checking host system type... powerpc-apple-darwin8.7.0 checking whether make sets $(MAKE)... no checking for gcc...

when i run ./configure in fedora 9 64 bit i get this error checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking whether make sets $(MAKE)... yes checking for gcc... gcc -m32 checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. this is

Hi, I downloaded wine source from winehq and installed all dependencies as per the wiki: http://wiki.winehq.org/WineOn64bit However when i run ./configure,its displays the following and exits: Code: $ ./configure ## --------- ## ## Platform. ## ## --------- ## hostname = localhost.localdomain uname -m = x86_64 uname -r = 2.6.26.5-45.fc9.x86_64 uname -s = Linux uname -v = #1 SMP Sat Sep 20

hi, it seems when dovecot use ldap user and password databases it's not possible to use tls connection and certificate with the ldap connection. wouldn't it be possible to use the same certificate on the ldap connection as used in the ssl_{cert,key}_file parameters in the dovecot conf (or would be possible to use it's own cert in the ldap conf file? yours. -- Levente

On Wed, 2015-01-28 at 10:11 -0600, Russell Poyner wrote: > I have 20+ freebsd 10 samba 4 servers joined to our local microsoft > active directory. At the moment things work well enough. However the > windows administrator wants to tighten his AD security by requiring tls > encrypted ldap. > > When I add: > ldap ssl = start_tls > ldap ssl ads = yes > cldap port = 389

I've encountered exact same issue as in this thread below, but I cannot figure out what the solution is https://lists.samba.org/archive/samba/2015-February/189012.html In short, my Samba 4.1.22 used to be a member of the domain, with these ldap ssl settings in the config: ldap ssl = start tls ldap ssl ads = Yes I've updated it to 4.3.8, and it now cannot talk to the domain, it shows

Hi, I've a problem in connecting samba 2.2.5 to LDAP with ldap ssl = start_tls. I've already patched the file pdb_ldap.c and configure.in and run autconf (as described in the Samba-LDAP-PDC howto). However, doing a rpcclient servername -U root%password -c "enumprinters" shows this in the log: [2002/08/23 16:50:44, 0] passdb/pdb_ldap.c:ldap_open_connection(181) Failed to

> Message: 8 > Date: Mon, 24 Jun 2002 18:13:33 -0500 (CDT) > From: "Gerald (Jerry) Carter" <jerry@samba.org> > To: samba@samba.org > Subject: [Samba] patch for 2.2.5 and check for start_tls with OpenLDAP 2.0.x libs > > This message is in MIME format. The first part should be readable text, > while the remaining parts are likely unreadable without

Dear list, More questions on my PDC travels ;-) 1. Is it ok, with roaming profiles on, to leave "logon drive = " empty, as this drive seems to be confusing users? 2. All my ldap stuff is using tls, and I just want to confirm that "ldap ssl = start_tls" is looking in /etc/ldap.conf for certificate locations etc.? 3. Is all traffic between Windows clients and the Samba

Andrew, Thanks for the pointers about looking into the ldap client libs. I think I've found a situation where tls connections to the AD server on port 389 have trouble. I've added the CA cert to ldap.conf, and to the ca_root_nss file on this system. First what works: 1. ldapsearch commands with -Z to force use of tls (configured in /usr/local/etc/ldap.conf) 2. ssl connections with

Hi, i was the one who had problems with the start_tls function. I applied the patch yesterday. But now the compiling doesn't work anymore. This is what happens : --------snipp---------- [Lots of compiling output cut away] Linking bin/smbd passdb/pdb_ldap.o: In function `pdb_setsampwent': passdb/pdb_ldap.o(.text+0x1730): multiple definition of `pdb_setsampwent'

I have 20+ freebsd 10 samba 4 servers joined to our local microsoft active directory. At the moment things work well enough. However the windows administrator wants to tighten his AD security by requiring tls encrypted ldap. When I add: ldap ssl = start_tls ldap ssl ads = yes cldap port = 389 the net ads commands fail: net ads testjoin Failed to issue the StartTLS instruction: Connect error

Hey All, I'm trying to compile Samba 3.0.12rc1 on a Redhat Linux Fedora Core 3 machine. I have the following LDAP RPMS installed: rpm -qa | grep ldap gives: openldap-2.2.13-2 python-ldap-2.0.1-2 openldap-clients-2.2.13-2 openldap-devel-2.2.13-2 openldap-servers-2.2.13-2 nss_ldap-220-3 I run configure in the following fashion: CFLAGS="-O2 -march=prescott

Allow an alternate libc, such as dietlibc, to be used for the init binary in the supermin appliance. Rich.

Joseph, Please try my modified versions of these patches. These are compile-tested on Fedora and they don't break any existing functionality, but I don't have either urpmi nor a statically-linked xz so I cannot fully test them. I have also fixed detection of zlib (2/3). Rich.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, While preparing packaging of te upcoming samba-2.2.5, we are looking at having samba packages with and without ldap enabled, however, we would like to try and minimize the duplication. But, it seems that most (all?) binaries resulting from a --with-ldapsam build en up linking to libldap. Are there really good reasons for nmblookup, smbcacls,

v1 -> v2: - If we split out the init program into a separate init/ directory, that makes it much easier to build against an alternate libc. I tried to build against uClibc, but uClibc requires an entire build chain, which looked like it was going to be a massive ballache. Rich.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the second beta release of the Samba 3.0.0 code base. While we are significantly closer to the final release, you should be reminded that this is a non-production release provided for testing only. The source code can be downloaded from : http://download.samba.org/samba/ftp/beta/ The