openldap-bugs

openldap-bugs@openldap.org

1 participants
20963 discussions

(ITS#5003) issue about upper_needs_cast
by caojunliang＠huawei.com 07 Jun '07

07 Jun '07

Full_Name: Cao Junliang Version: openldap-2.3.35 OS: windows xp URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (210.21.230.126) Hello, when I set the option upper_needs_cast as Yes.It only takes effect on id_query when adding an entry,but does not take effect on child id query when deleting an entry. I found that in the src file back-sql/init.c line 374 --379 there are not operation about upper cast. I want to know if what I think is right. Cao Junliang

1 0

Re: (ITS#5002) Windows Service: logoff causes shutdown
by hyc＠symas.com 07 Jun '07

07 Jun '07

This bug was fixed several years ago. You should update to a current release. This ITS will be closed. mark.lakes(a)alcatel-lucent.com wrote: > Full_Name: Mark Lakes > Version: 2.1.22 > OS: Windows > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (198.206.187.100) > > > Summary: LDAP service stops when user logs off. > > The LDAP server is registered as a Windows Service and works correctly with > SCM. > It is registered as an automatic service so should be running all the time. > When a user logs off from the box, the logoff triggers the service to stop > running. > This happens on WindowsXP and Windows 2003 Server that are configured on a > Domain. > > I have a solution. > The problem is that despite the fact it is a service, it receives an event > called CTRL_LOGOFF_EVENT. Since it is not handling this event, the default > behavior by Windows is to shutdown the service. > Add the following code to the source at an appropriate place(probably somewhere > in ntservice.c) for when it runs as a service: > > /** > This is used to handle CTRL_LOGOFF_EVENT from shutting us down when we are > running as a service. > Return TRUE works. We dont really care what the crtlType is. > */ > BOOL WINAPI > WinSigHANDLER_ROUTINE(DWORD ctrlType) > { > /* > char logstr[256]; > sprintf(logstr, "NTservice: caught signal(%d)\n", ctrlType); > writeStatusLog(logstr); > switch (ctrlType) > { > case CTRL_LOGOFF_EVENT: > ... > default: > > } */ > return TRUE; > } > > Then, register the above function in the appropriate place as follows: > SetConsoleCtrlHandler(WinSigHANDLER_ROUTINE, TRUE); > > > > -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#5002) Windows Service: logoff causes shutdown
by mark.lakes＠alcatel-lucent.com 07 Jun '07

07 Jun '07

Full_Name: Mark Lakes Version: 2.1.22 OS: Windows URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (198.206.187.100) Summary: LDAP service stops when user logs off. The LDAP server is registered as a Windows Service and works correctly with SCM. It is registered as an automatic service so should be running all the time. When a user logs off from the box, the logoff triggers the service to stop running. This happens on WindowsXP and Windows 2003 Server that are configured on a Domain. I have a solution. The problem is that despite the fact it is a service, it receives an event called CTRL_LOGOFF_EVENT. Since it is not handling this event, the default behavior by Windows is to shutdown the service. Add the following code to the source at an appropriate place(probably somewhere in ntservice.c) for when it runs as a service: /** This is used to handle CTRL_LOGOFF_EVENT from shutting us down when we are running as a service. Return TRUE works. We dont really care what the crtlType is. */ BOOL WINAPI WinSigHANDLER_ROUTINE(DWORD ctrlType) { /* char logstr[256]; sprintf(logstr, "NTservice: caught signal(%d)\n", ctrlType); writeStatusLog(logstr); switch (ctrlType) { case CTRL_LOGOFF_EVENT: ... default: } */ return TRUE; } Then, register the above function in the appropriate place as follows: SetConsoleCtrlHandler(WinSigHANDLER_ROUTINE, TRUE);

1 0

(ITS#5001) Incorrect SSF display
by quanah＠OpenLDAP.org 07 Jun '07

07 Jun '07

Full_Name: Quanah Gibson-Mount Version: 2.3.35 OS: NA URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (71.202.148.128) I was playing with SASL connections on an TLS encrypted connection, and noticed the SSF displayed is not correct in the SASL part. Jun 7 12:51:27 ldap-dev1 slapd[11858]: conn=4494 fd=29 TLS established tls_ssf=256 ssf=256 Jun 7 12:51:27 ldap-dev1 slapd[11858]: conn=4494 op=4 BIND dn="uid=quanah,cn=accounts,dc=stanford,dc=edu" mech=GSSAPI ssf=56 I believe that the second line above should really display "sasl_ssf=56", or probably even better, "sasl_ssf=56 ssf=256", similar to how the first line has "tls_ssf=256 ssf=256", so that it is clear that there are different security factors in play here. --Quanah

1 0

Re: (ITS#4965) slapd stops if access to cn=monitor is restricted
by ando＠sys-net.it 07 Jun '07

07 Jun '07

HEAD as of now: <slapd.conf> # ... access to * by * none database bdb suffix "dc=example,dc=com" directory /home/masarati/Lavoro/sysnet/Ldap/ldap-devel/tests/testrun/db.1.a rootdn "cn=Manager,dc=example,dc=com" rootpw secret index objectClass eq index cn,sn,uid pres,eq,sub database monitor </slapd.conf> $ slapd -d stats @(#) $OpenLDAP: slapd 2.X (Jun 7 2007 17:39:58) $ masarati@mbdyn-pm:/home/masarati/Lavoro/sysnet/Ldap/ldap-devel/servers/slapd bdb_db_open: Warning - No DB_CONFIG file found in directory /home/masarati/Lavoro/sysnet/Ldap/ldap-devel/tests/testrun/db.1.a: (2) Expect poor performance for suffix dc=example,dc=com. monitor_back_register_entry_attrs(""): base="cn=databases,cn=monitor" scope=one filter="(namingContexts:distinguishedNameMatch:=dc=example,dc=com)": unable to find entry slapd starting It seems fine to me. Are you sure there isn't anything else? You might be disguised by a warning that has nothing to do with your real issue. Or, you're not posting enough info. p. ali.pouya(a)free.fr wrote: > Hi Pierangelo; > Unfortunately I reproduced the problem with the HEAD dated June 5. > If I do not add a rootdn to the monitor database, slapd cannot start. > At the end of the log I find : > > monitor_back_register_entry_attrs(""): base="cn=databases,cn=monitor" scope=one > filter="(namingContexts:distinguishedNameMatch:=c=fr)": unable to find entry > > ====> bdb_cache_release_all > backend_startup_one: bi_db_open failed! (-1) > slapd shutdown: initiated > ====> bdb_cache_release_all > bdb_db_close: alock_close failed > slapd destroy: freeing system resources. > slapd stopped. > connections_destroy: nothing to destroy. > > Is the rootdn mandatory for monitor ? > Best Regards > Ali > > > > 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 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5000) slapd with invalid url causes crashes
by hyc＠symas.com 07 Jun '07

07 Jun '07

This is most likely the same as ITS#4957 which has already been fixed in the new release candidate. This ITS will be closed. jl+openldap(a)lists.wasmer.ca wrote: > Full_Name: Jean-Luc Wasmer > Version: 2.3.32 > OS: NetBSD 4.0 Beta2 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (70.50.240.203) > > > > When slapd is started with an invalid url, it looks like it's trying to destroy > an uninitialized mutex: > > Program received signal SIGABRT, Aborted. > 0xbb87dfff in kill () from /usr/lib/libc.so.12 > (gdb) backtrace > #0 0xbb87dfff in kill () from /usr/lib/libc.so.12 > #1 0xbb94adb3 in pthread__errorfunc () from /usr/lib/libpthread.so.0 > #2 0xbb9491fe in pthread_mutex_destroy () from /usr/lib/libpthread.so.0 > #3 0xbbbbd1eb in ldap_pvt_thread_mutex_destroy () from > /usr/pkg/lib/libldap_r-2.3.so.0 > #4 0x0805a756 in ?? () > #5 0x0819e4fc in __ps_strings () > #6 0x00000002 in ?? () > #7 0xbfbfe8e8 in ?? () > #8 0x0805a713 in ?? () > #9 0x00000286 in ?? () > #10 0x00000001 in ?? () > #11 0xbfbfe958 in ?? () > #12 0x0804e2c1 in ?? () > #13 0xbfa00000 in ?? () > #14 0xbb92cdd0 in tzname () from /usr/lib/libc.so.12 > #15 0x00000002 in ?? () > #16 0x00000000 in ?? () > > Invalid argument that triggered the bug: > -h 'ldap://127.0.0.1 ldaps://<external ip>' > with no interfaces on the system configured with <external ip> > > > . > -- -- Howard Chu Chief Architect, 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#4965) slapd stops if access to cn=monitor is restricted
by ali.pouya＠free.fr 07 Jun '07

07 Jun '07

Hi Pierangelo; Unfortunately I reproduced the problem with the HEAD dated June 5. If I do not add a rootdn to the monitor database, slapd cannot start. At the end of the log I find : monitor_back_register_entry_attrs(""): base="cn=databases,cn=monitor" scope=one filter="(namingContexts:distinguishedNameMatch:=c=fr)": unable to find entry ====> bdb_cache_release_all backend_startup_one: bi_db_open failed! (-1) slapd shutdown: initiated ====> bdb_cache_release_all bdb_db_close: alock_close failed slapd destroy: freeing system resources. slapd stopped. connections_destroy: nothing to destroy. Is the rootdn mandatory for monitor ? Best Regards Ali

1 0

(ITS#5000) slapd with invalid url causes crashes
by jl+openldap＠lists.wasmer.ca 06 Jun '07

06 Jun '07

Full_Name: Jean-Luc Wasmer Version: 2.3.32 OS: NetBSD 4.0 Beta2 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (70.50.240.203) When slapd is started with an invalid url, it looks like it's trying to destroy an uninitialized mutex: Program received signal SIGABRT, Aborted. 0xbb87dfff in kill () from /usr/lib/libc.so.12 (gdb) backtrace #0 0xbb87dfff in kill () from /usr/lib/libc.so.12 #1 0xbb94adb3 in pthread__errorfunc () from /usr/lib/libpthread.so.0 #2 0xbb9491fe in pthread_mutex_destroy () from /usr/lib/libpthread.so.0 #3 0xbbbbd1eb in ldap_pvt_thread_mutex_destroy () from /usr/pkg/lib/libldap_r-2.3.so.0 #4 0x0805a756 in ?? () #5 0x0819e4fc in __ps_strings () #6 0x00000002 in ?? () #7 0xbfbfe8e8 in ?? () #8 0x0805a713 in ?? () #9 0x00000286 in ?? () #10 0x00000001 in ?? () #11 0xbfbfe958 in ?? () #12 0x0804e2c1 in ?? () #13 0xbfa00000 in ?? () #14 0xbb92cdd0 in tzname () from /usr/lib/libc.so.12 #15 0x00000002 in ?? () #16 0x00000000 in ?? () Invalid argument that triggered the bug: -h 'ldap://127.0.0.1 ldaps://<external ip>' with no interfaces on the system configured with <external ip>

1 0

(ITS#4999) Dead Link
by ghenry＠OpenLDAP.org 06 Jun '07

06 Jun '07

Full_Name: Gavin Henry Version: N/A OS: N/A URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.159.59.85) Dead link: http://www.openldap.org/project/software/repo.html Thanks, Gavin.

1 0

Re: (ITS#4998) overlays/ppolicy.c: invalid pointer due to free() of unallocated buffer
by msl＠calivia.com 04 Jun '07

04 Jun '07

Howard Chu wrote: > msl(a)calivia.com wrote: >> Full_Name: Michael Steinmann >> Version: 2.3.35 / HEAD >> OS: Linux >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (80.254.173.218) >> >> >> This is while testing a custom pwdCheckModule. >> In function check_password_quality(), char *txt is free()'d, slapd >> crashes with >> "invalid pointer". > > The code works as designed (and as documented). Re-read the > slapo-ppolicy(5) manpage. This ITS will be closed. Got it, thanks. Sorry for the noise. -- mike

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