openldap-bugs

openldap-bugs@openldap.org

1 participants
20965 discussions

(ITS#5766) smbkrb5 overlay doesn't honour kerberos principal expiration
by Guillaume.Rousse＠inria.fr 22 Oct '08

22 Oct '08

Full_Name: Guillaume Rousse Version: 2.4.11 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (193.55.250.67) When using the smbkrb5 overlay, the {K5KEY} password can be used to make autentication use kerberos credentials. However, this redirection doesn't honour krb5ValidEnd or sambaKickoffTime attribute, positionned by either heimdal or smbkrb5 overlay when setting an expiration date to the kerberos principal. Whereas kdc refuses to provides a ticket for the user, openldap still allows the user to authenticate.

1 0

RE: (ITS#5765) Can not set log file with configdb
by emmanuel.duru＠atosorigin.com 22 Oct '08

22 Oct '08

OK it works, thank you.

1 0

Re: (ITS#5765) Can not set log file with configdb
by ando＠sys-net.it 22 Oct '08

22 Oct '08

emmanuel.duru(a)atosorigin.com wrote: Should be fixed in HEAD; please test. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

1 0

(ITS#5765) Can not set log file with configdb
by emmanuel.duru＠atosorigin.com 22 Oct '08

22 Oct '08

Full_Name: Emmanuel Duru Version: 2.4.11 OS: Windows URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (80.78.0.137) I have a slapd.conf with a logfile directive. When converting the conf to LDIF (slapd -f slapd.conf -F /path/configdb), this directive is lost. When I try to add an olcLogFile attribute to cn=config, I get an "object class violation" error. I suppose the olcLogFile attribute is missing in the hard-coded schema for olcGlobal object class.

1 0

(ITS#5764) addpartial patch
by dhawes＠vt.edu 21 Oct '08

21 Oct '08

Full_Name: David Hawes Version: 2.4.12 OS: URL: ftp://ftp.openldap.org/incoming/david-hawes-081021.patch Submission from: (NULL) (128.173.38.164) This patch includes the following changes: - -fPIC added to the Makefile for compilation on x86_64 systems. - No longer use be_search() to retrieve the entry that is to be compared. Use be_entry_get_rw() instead. - No need to use strlen.

1 0

Re: (ITS#5757) back-null returns an error when any critical extension is specified
by jclarke＠linagora.com 21 Oct '08

21 Oct '08

ando(a)sys-net.it a écrit : > ando(a)sys-net.it wrote: >> A different fix is in HEAD. Please test. p. > > A more thorough fix is now in HEAD. Please re-test. Just tested, it works as expected: - searches with a non-critical control propagate the control to "glued-sub-backends" which use it if possible. - searches with a critical control propagate the control to "glued-sub-backends" and return error 12 if it is not supported. This is indeed a much better approach that I originally proposed - respecting control criticality as required, and reminded by Kurt. Thanks ando! Regards, Jonathan -- Jonathan Clarke Open Source Identity Management --------------------------------------------------------------- Linagora 27 rue de Berri, 75008 Paris Tel: 01 58 18 68 28 / 06 99 60 03 10 --------------------------------------------------------------- Ldap Synchronization Connector (LSC) - http://lsc-project.org/ ---------------------------------------------------------------

1 0

(ITS#5763) libRSAglue bug in OpenLDAP configure script
by epj＠newpointtech.com 21 Oct '08

21 Oct '08

Full_Name: Eric Johanson Version: 2.4.12 OS: Debian Linux 4.0 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (64.80.228.78) The "configure" script has a bug when TLS is enabled, which causes it to fail when using recent versions of OpenSSL. The bug is found on line 18759 of the "configure" script in OpenLDAP 2.4.12. The line currently reads: LIBS="-lssl -lcrypto -lRSAglue -lrsaref $LIBS" But the -lRSAglue and -lrsaref are old OpenSSL libraries that are not in use any more. I modified the above line to read: LIBS="-lssl -lcrypto $LIBS" This solves the problem. However, perhaps someone wants to add logic to detect which version of OpenSSL is being used and then vary the LIBS variable accordingly when the configure script tests for the linkability of the ssl3_accept() function. Note that many Linux systems, even those that have a recent OpenSSL, may still have the -lRSAglue and -lrsaref libraries (just for compatibility reasons). To reproduce this bug, you will have to search your system and remove all files with the names libRSAglue.a and librsaref.a.

1 0

(ITS#5762) ldap_create_page_control might return wrong error code
by ralf＠OpenLDAP.org 21 Oct '08

21 Oct '08

Full_Name: Ralf Haferkamp Version: RE24, Head OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (89.166.241.0) Submitted by: ralf ldap_create_page_control_value doesn't reset ld_errno to LDAP_SUCCESS therefor it will return the result code of the previous LDAP API call instead of LDAP_SUCCESS. (If the previous LDAP API call set ld_errno do something different than LDAP_SUCCESS). The same seems to be true for the corresponding function in at least: sortctrl.c, vlvctrl.c and stctrl.c Fix will follow.

1 0

Re: (ITS#5755) Schema file not always converted to LDIF and slapdwon't restart
by hyc＠symas.com 21 Oct '08

21 Oct '08

emmanuel.duru(a)atosorigin.com wrote: > OK this works. > My mistake, the concerned character is in fact a Windows character (CP1252) > I hadn't noticed when I converted my schema to a text file. With the patch in HEAD your schema file now yields: config_build_attrs: error 21 on olcAttributeTypes value #3 config_build_entry: build "cn={0}test" failed: "" backend_startup_one: bi_db_open failed! (-1) slapd stopped. Probably we should be detecting this problem earlier, when parsing slapd.conf, instead of when generating the cn=config entries. >> -----Message d'origine----- >> De : Hallvard Breien Furuseth [mailto:h.b.furuseth@usit.uio.no] >> Envoyé : lundi 20 octobre 2008 19:39 >> À : Emmanuel Duru >> Cc : openldap-its(a)OpenLDAP.org >> Objet : RE: (ITS#5755) Schema file not always converted to LDIF and >> slapdwon't restart >> >> The problem is the 8-bit Latin-1 character in the certificate's DESC. >> It works if you convert the schema file to UTF-8. >> >> Slapd should have refused to start with a non-UTF-8 attribute DESC. >> Possibly that should wait for OpenLDAP 2.5 though, and just log a >> warning for now. >> >> -- >> Hallvard > > > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

RE: (ITS#5755) Schema file not always converted to LDIF and slapdwon't restart
by emmanuel.duru＠atosorigin.com 21 Oct '08

21 Oct '08

OK this works. My mistake, the concerned character is in fact a Windows character (CP1252) I hadn't noticed when I converted my schema to a text file. > -----Message d'origine----- > De : Hallvard Breien Furuseth [mailto:h.b.furuseth@usit.uio.no] > Envoyé : lundi 20 octobre 2008 19:39 > À : Emmanuel Duru > Cc : openldap-its(a)OpenLDAP.org > Objet : RE: (ITS#5755) Schema file not always converted to LDIF and > slapdwon't restart > > The problem is the 8-bit Latin-1 character in the certificate's DESC. > It works if you convert the schema file to UTF-8. > > Slapd should have refused to start with a non-UTF-8 attribute DESC. > Possibly that should wait for OpenLDAP 2.5 though, and just log a > warning for now. > > -- > Hallvard

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs