openldap-technical March 2015

openldap-technical@openldap.org

51 participants
70 discussions

Re: Q: different SSF settings for ldapi:// than for ldap:
by Michael Ströder 30 Mar '15

30 Mar '15

Ulrich Windl wrote: > Isn't the SSF strength for ldapi:// zero? The SSF strength of ldapi:// is whatever you set with configuration directive localSSF. It's your local security policy decision. Personally on my systems I don't see any problem with setting it to an equal strength like a strongly encrypted TLS connection. YMMV. Ciao, Michael.

1 0

Re: Antw: Re: Q: different SSF settings for ldapi:// than for ldap:
by Michael Ströder 30 Mar '15

30 Mar '15

Ulrich Windl wrote: >>>> Michael Ströder<michael(a)stroeder.com> schrieb am 30.03.2015 um 11:24 in > Nachricht <55191633.90204(a)stroeder.com>: >> Ulrich Windl wrote: >>>>>> Michael Ströder<michael(a)stroeder.com> schrieb am 29.03.2015 um 12:12 in >>>> I have this in my config: >>>> >>>> # SSF value for ldapi:// >>>> localSSF 256 >>> >>> What I don't understand here is: Doesn't "256" _require_ encryption for >>> ldapi:// then? >> >> There is a reason for everything I write, especially this sentence: >> >> >> See slapd.conf(5) for details. >> >> Learn to read the fine docs. > > What really annoys me in this list are answers like "I know, you dont't. Try > to find out yourself!". Is it really too demanding to look up the text yourself when I point out a particular configuration directive *and* point to the relevant man page? My impression was that you did not read the text before asking back. > Here's what the manual page says: > -- > localSSF <SSF> > Specifies the Security Strength Factor (SSF) to be given > local > LDAP sessions, such as those to the ldapi:// listener. For > a > description of SSF values, see sasl-secprops's minssf > option > description. The default is 71. > -- > So where is the answer what 255 means? And what is the meaning of 71? (I guess > 71 bit encryption; so I guess 255 means 255-bit encryption, but you say I'm > wrong) Yes, the default is 71 which is lower than what you specified as minssf. Ciao, Michael.

1 0

Re: Antw: Re: external authentication source
by Hallvard Breien Furuseth 30 Mar '15

30 Mar '15

On 23. mars 2015 12:45, Ulrich Windl wrote: > Related question: If the command above fails with "stronger confidentiality required", and adding "-ZZ" fails with " TLS: hostname does not match CN in peer certificate", how should a proper certificate look like? Read the OpenLDAP Admin Guide, section 16 (TLS). In particular 16.1.1. Server Certificates. -- Hallvard

3 3

installing slapd no_configuration true
by Igor Shmukler 30 Mar '15

30 Mar '15

Hello, I have been trying to install slapd without configuration, so I could do the configuration manually [specifically to customize my "organization" objectClass]. I have been using debconf-set-selections and noninteractive install. It worked fine when I would do non interactive config database configuration and also DIT database configuration. When I set "slapd slapd/no_configuration boolean true" setup fails. The error is below: Omitting slapd configuration as requested. * No configuration file was found for slapd at /etc/ldap/slapd.conf. invoke-rc.d: initscript slapd, action "start" failed. dpkg: error processing package slapd (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for ufw (0.34~rc-0ubuntu2) ... Errors were encountered while processing: slapd E: Sub-process /usr/bin/dpkg returned an error code (1) I understand that the issue might be debian-related and have little to do with OpenLDAP, per say. Still, to be sure that I did not do something completely wrong, and to tap into collective wisdom; I would love for someone experienced to comment. What would be the easiest way to install slapd, ideally with config database setup, without a DIT database? I want to manually add DIT database[s] later. I got that part down. Sincerely, Igor Shmukler

5 6

Re: Q: different SSF settings for ldapi:// than for ldap:
by Michael Ströder 30 Mar '15

30 Mar '15

Ulrich Windl wrote: >>>> Michael Ströder<michael(a)stroeder.com> schrieb am 29.03.2015 um 12:12 in >> I have this in my config: >> >> # SSF value for ldapi:// >> localSSF 256 > > What I don't understand here is: Doesn't "256" _require_ encryption for > ldapi:// then? There is a reason for everything I write, especially this sentence: >> See slapd.conf(5) for details. Learn to read the fine docs. Ciao, Michael.

1 0

Re: Antw: Re: external authentication source
by Dirk Kastens 29 Mar '15

29 Mar '15

Hi Ulrich, > Thanks for the hint, but I fail to use it: > > First it seems I cannot use it in olcSecurity (as I can use update_ssf), and then I fail to set it at the database level: It's a global option. Just set it as an attribute of cn=config. dn: cn=config olcLocalSSF: 256 Then use ldapsearch without TLS. This should work. Regards, Dirk

1 0

LMDB use of sparse or non-sparse data file
by Geoff Swan 29 Mar '15

29 Mar '15

I had to duplicate an LMDB database for replication recently, and used mdb_copy to do so. One server is using the original data.mdb database (which is sparse) and the other is using the mdb_copy non-sparse data.mdb file. The two servers are identical (hardware, OS, software and configuration). OpenLDAP-2.4.39 is being used, 64 bit Linux OS. mdb_stat shows the map size as the same, which is expected. Will the use of the non-sparse file cause any performance issues? The reason for asking is that I am seeing a difference in search times between the two. With 20 million objects, a search on modifyTimestamp (which is indexed) gives: server 1: approx 1s server 2: approx 60s server 2 started with the same search time as server 1 when the databases were originally copied, but has slowly increased its search time over about a week for this same search.

3 7

Re: LMDB use of sparse or non-sparse data file
by Quanah Gibson-Mount 29 Mar '15

29 Mar '15

--On Wednesday, March 25, 2015 5:11 PM +1100 Geoff Swan <gswan3(a)bigpond.net.au> wrote: >> Question is irrelevant since both are sparse files. > Thanks for the clarification Howard. > The data file from the mdb_copy snapshot was transferred over the > network to the other server using scp, which I understand does not > recognise sparse files, so the copy is likely to be non-sparse. I guess > this would be considered a corruption and best to start with a fresh copy? I've had no issue scp'ing files created from mdb_copy. Original host: zimbra@zre-ldap002:~/data/ldap/mdb/db$ ls -l total 432 -rw------- 1 zimbra zimbra 85899345920 Mar 25 14:53 data.mdb -rw------- 1 zimbra zimbra 8192 Mar 25 14:54 lock.mdb zimbra@zre-ldap002:~/data/ldap/mdb/db$ mkdir /tmp/mdb/ zimbra@zre-ldap002:~/data/ldap/mdb/db$ mdb_copy . /tmp/mdb zimbra@zre-ldap002:~/data/ldap/mdb/db$ ls -l /tmp/mdb/ total 428 -rw-r--r-- 1 zimbra zimbra 438272 Mar 25 14:54 data.mdb Destination host: [build@zre-ldap003 zcs-NETWORK-8.7.0_BETA1_1149.RHEL6_64.20150324181030]$ scp build@zre-ldap002:/tmp/mdb/data.mdb /tmp/mdb.002/ data.mdb 100% 428KB 428.0KB/s 00:00 [build@zre-ldap003 zcs-NETWORK-8.7.0_BETA1_1149.RHEL6_64.20150324181030]$ su Password: [root@zre-ldap003 zcs-NETWORK-8.7.0_BETA1_1149.RHEL6_64.20150324181030]# chmod a+rx /tmp/mdb.002 [root@zre-ldap003 zcs-NETWORK-8.7.0_BETA1_1149.RHEL6_64.20150324181030]# chmod a+r /tmp/mdb.002/data.mdb [root@zre-ldap003 zcs-NETWORK-8.7.0_BETA1_1149.RHEL6_64.20150324181030]# su - zimbra [zimbra@zre-ldap003 ~]$ cd data/ldap/mdb [zimbra@zre-ldap003 mdb]$ ls db.orig [zimbra@zre-ldap003 mdb]$ mkdir db [zimbra@zre-ldap003 mdb]$ ls db db.orig [zimbra@zre-ldap003 mdb]$ cd db [zimbra@zre-ldap003 db]$ cp /tmp/mdb.002/data.mdb . [zimbra@zre-ldap003 db]$ ls -l total 428 -rw-r-----. 1 zimbra zimbra 438272 Mar 25 14:57 data.mdb [zimbra@zre-ldap003 db]$ ldap start Started slapd: pid 32518 [zimbra@zre-ldap003 db]$ ls -l total 432 -rw-r-----. 1 zimbra zimbra 85899345920 Mar 25 14:57 data.mdb -rw-------. 1 zimbra zimbra 8192 Mar 25 14:57 lock.mdb --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

2 2

Questionable log entries
by Timo Eissler 29 Mar '15

29 Mar '15

Hello, i have found some weird messages in my syslog since i setup openldap and switched my users from local passwd/shadow to openldap. I have two notebooks using sssd and the openldap server is configured with pam_ldap/nss_ldap authentication. I didn't have any problems, but i'm unsure why those message are logged and so i decided to ask this on the list. Those are the messages in question: Mar 22 20:10:01 foobarsrv1 slapd[16923]: connection_input: conn=12652 deferring operation: binding Mar 22 15:36:33 foobarsrv1 slapd[16923]: connection_read(29): no connection! Mar 22 15:37:36 foobarsrv1 slapd[16923]: conn=10375 op=6 ABANDON msg=6 Mar 15 09:00:59 foobarsrv1 slapd[28731]: connection_input: conn=16081 deferring operation: too many executing Mar 12 18:33:54 foobarsrv1 slapd[699]: slap_global_control: unrecognized control: 1.3.6.1.4.1.42.2.27.8.5.1 I have tried to find a solution or reason for this since two weeks or so, but i couldn't find the answer/solution. Regarding the "deferring operation: binding" message i'm just concerned, because their is absolutely no load on the system and i'm not sure what would happen if i had more than 3 clients (including the server) which use ldap. I already tried to match those messages with other things going on on the system, but i could get any match. Currently i get the "deferring operation: binding" anything between 2 and 10 times a day. I know that this may be more than one issue, but i hope that you are willing to help me solve this. This is my slapd.conf: Konsole output include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/nis.schema include /etc/openldap/schema/misc.schema include /etc/openldap/schema/samba.schema pidfile /var/run/openldap/slapd.pid argsfile /var/run/openldap/slapd.args security tls=1 simple_bind=128 access to dn.base="" by * read access to dn.base="cn=Subschema" by * read access to attrs=userPassword by self write by anonymous auth by * none access to * by self write by * read access to * by dn.exact="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth" manage by * none TLSCipherSuite HIGH:MEDIUM:-SSLv2:-SSLv3 TLSCertificateFile /etc/openldap/ssl/slapdcert.pem TLSCertificateKeyFile /etc/openldap/ssl/slapdkey.pem database hdb suffix "dc=foobar,dc=local" checkpoint 32 30 rootdn "cn=Manager,dc=foobar,dc=local" rootpw {SSHA}XXXX directory /var/lib/openldap-data index objectClass eq index uid pres,eq index memberUid pres,eq index uidNumber pres,eq index gidNumber pres,eq index uniqueMember pres,eq index sambaSID pres,eq index mail pres,sub,eq index cn pres,sub,eq index sn pres,sub,eq index dc eq database config My /etc/ldap.conf Konsole output host 127.0.0.1 base dc=foobar,dc=local uri ldap://localhost/ ldap_version 3 scope one bind_policy soft idle_timelimit 3600 pam_filter objectclass=posixAccount pam_member_attribute memberuid pam_min_uid 1000 pam_password exop nss_base_passwd ou=People,dc=foobar,dc=local?one nss_base_shadow ou=People,dc=foobar,dc=local?one nss_base_group ou=Groups,dc=foobar,dc=local?one nss_base_hosts ou=Hosts,dc=foobar,dc=local?one ssl start_tls nss_initgroups_ignoreusers root,bin,daemon,adm,lp,sync,shutdown,halt,news,uucp,operator,portage,nobody,man,sshd,cron,mail,postmaster,ldap,m ysql,mediatomb,dovecot,dovenull,apache,openvpn,clamav,bacula,asterisk,ntp The openldap server is an up to date Gentoo system. If you need more informations just let me know. Kind regards, Timo -- Timo Eissler Senior Project Engineer / Consultant Am Zuckerberg 54 D-71640 Ludwigsburg Tel.: +49 7141 4094003 Mobil.: +49 151 20650311 Email: timo(a)teissler.de

3 10

Q: different SSF settings for ldapi:// than for ldap:
by Ulrich Windl 29 Mar '15

29 Mar '15

Hi! I've configured slapd to require excryption (confidentiality). Now connections via ldapi:// fail with "13 Confidentiality required". When adding "-ZZ" for ldapsearch (e.g.), the connection fails, because the certificate does not match ldapi:// (I asked about that before, but got no answer). How can I configure slapd not to require confidentiality? Regards, Ulrich

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical March 2015