Re: (ITS#5236) core.ldif differs from core.schema
by hyc＠symas.com
dieter(a)dkluenter.de wrote:
> Full_Name: Dieter Kluenter
> Version: HEAD
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (84.142.190.40)
>
>
> core.ldif
>
> olcAttributeTypes: ( 2.5.4.6 NAME ( 'c' 'countryName' )
> DESC 'RFC2256: ISO-3166 country 2-letter code'
> SUP name SINGLE-VALUE )
>
> core.schema
> attributetype ( 2.5.4.6 NAME 'c'
> DESC 'RFC2256: ISO-3166 country 2-letter code'
> SUP name
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.11
> SINGLE-VALUE )
>
> As far as I understand, core.schema is correct here.
Seems someone updated core.schema for RFC4519 but didn't update core.ldif. I'm
puzzled why RFC4519 drops the 'countryName' alias for this type from the
RFC2256 definition.
--
-- 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/
15 years, 10 months
(ITS#5236) core.ldif differs from core.schema
by dieter＠dkluenter.de
Full_Name: Dieter Kluenter
Version: HEAD
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (84.142.190.40)
core.ldif
olcAttributeTypes: ( 2.5.4.6 NAME ( 'c' 'countryName' )
DESC 'RFC2256: ISO-3166 country 2-letter code'
SUP name SINGLE-VALUE )
core.schema
attributetype ( 2.5.4.6 NAME 'c'
DESC 'RFC2256: ISO-3166 country 2-letter code'
SUP name
SYNTAX 1.3.6.1.4.1.1466.115.121.1.11
SINGLE-VALUE )
As far as I understand, core.schema is correct here.
-Dieter
15 years, 10 months
(ITS#5235) ppolicy leads to segfault
by dieter＠dkluenter.de
Full_Name: Dieter Kluenter
Version: HEAD
OS:
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (84.142.231.219)
I am testing ppolicy overlay with HEAD. When starting slapd it segfaults with:
....
ber_scanf fmt ({mm}) ber:
ber_dump: buf=0xa015009c ptr=0xa01500bc end=0xa01500e5 len=41
0000: 00 27 04 14 65 6e 74 72 79 45 78 70 69 72 65 54 .'..entryExpireT
0010: 69 6d 65 73 74 61 6d 70 04 0f 32 30 30 37 31 31 imestamp..200711
0020: 31 35 32 31 31 31 32 33 5a 15211123Z
end get_filter 0
end get_filter_list
end get_filter 0
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa0a51b90 (LWP 5703)]
0xb7a67139 in free () from /lib/libc.so.6
this is gdb backtrace
(gdb) bt
#0 0xb7a67139 in free () from /lib/libc.so.6
#1 0xb7ec128a in ber_memfree_x (p=0x2001, ctx=0x0) at memory.c:152
#2 0x0808f556 in ch_free ()
#3 0xb76f458c in ppolicy_restrict (op=0xa0a50d54, rs=0xa0a51148)
at ppolicy.c:1245
#4 0x080d564e in overlay_op_walk ()
#5 0x080d5bee in ?? ()
#6 0xa0a50d54 in ?? ()
#7 0xa0a51148 in ?? ()
#8 0x00000002 in ?? ()
#9 0x082695b0 in ?? ()
#10 0x08270c50 in ?? ()
#11 0xa0a50be8 in ?? ()
#12 0xa0a50cec in ?? ()
#13 0xa0a50ce8 in ?? ()
#14 0x00000002 in ?? ()
#15 0xa0a51148 in ?? ()
#16 0x08270c50 in ?? ()
#17 0x000003f2 in ?? ()
#18 0x00000000 in ?? ()
-Dieter
15 years, 10 months
Re: (ITS#5187) test020-proxycache failing in RE_2_4
by ghenry＠suretecsystems.com
Tested in HEAD again, on same machine with same cmd:
for i in `seq 1 100`; do ./run test020 >> test_results.log; done;
and grepped the log file for "Error" and -i "succeed".
Results:
100 Passes
0 Fails
Looks good to me.
Gavin.
--
Kind Regards,
Gavin Henry.
Managing Director.
T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 824887
E ghenry(a)suretecsystems.com
Open Source. Open Solutions(tm).
http://www.suretecsystems.com/
15 years, 10 months
Re: (ITS#5187) test020-proxycache failing in RE_2_4
by ghenry＠OpenLDAP.org
rhafer(a)suse.de wrote:
> On Donnerstag, 8. November 2007, you wrote:
>> <quote who="Ralf Haferkamp">
>>
>>> On Donnerstag, 8. November 2007, rhafer(a)suse.de wrote:
>>>> I think I found a way.
>>>> 1. The SLAPD_ABANDON/op->o_abandon part of the cleanup handler will now
>>>> only get executed if the final result for the search has not been
>>>> received
>>>> (caching_reason == PC_IGNORE).
>>>> 2. Additionally, to add the entries to the cache, I do no longer use the
>>>> original Connection Object but create a new one
>>>> (connection_fake_init()),
>>>> because the op->o_abandon will be set for the original connection as
>>>> soon
>>>> as the client closes it.
>>>>
>>>> I'll do some more testing locally an submit this to HEAD later for more
>>>> external testing.
>>> Fix submitted to HEAD. Please test (preferably on the machine that caused
>>> this
>>> test to fail most often ;) ).
>> I'll try this tonight.
>>
>> Just to clarify, this is a fix in the code, rather than the test, which I
>> thought Howard had changed?
> Yes, it is a fix in the pcache code. The fix in the testcase was only done
> temporarely in the RE24 branch (HEAD was not changed). I intend to remove it
> as soon as I get positive feedback.
>
Trying to test in HEAD, can't cant past test008-concurrency on bdb tests.
Using ldapsearch to retrieve all the entries...
Filtering ldapsearch results...
Filtering original ldif used to create database...
Comparing filter output...
comparison failed - database was not created correctly
>>>>> ./scripts/test008-concurrency failed (exit 1)
make[2]: *** [bdb-mod] Error 1
make[2]: Leaving directory `/anything/src/openldap/ldap/tests'
make[1]: *** [test] Error 2
make[1]: Leaving directory `/anything/src/openldap/ldap/tests'
make: *** [test] Error 2
testrun data:
ftp://ftp.openldap.org/incoming/test008.tar.gz
--
Kind Regards,
Gavin Henry.
OpenLDAP Engineering Team.
E ghenry(a)OpenLDAP.org
Community developed LDAP software.
http://www.openldap.org/project/
15 years, 10 months
Re: (ITS#5234) Feature request: mit-kr5 support in smbk5pwd
by hyc＠symas.com
openldap2007(a)mnagl.de wrote:
> Full_Name: Matthias Nagl
> Version:
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (137.248.132.104)
> The current stable version of mit-krb5 (http://web.mit.edu/Kerberos/) seems to
> have a much better support for LDAP-Backends than Heimdal. Sadly the
> smbk5pwd-overlay currently won't support password synchronization with the new
> MIT-schema. It would be great if smbk5pwd could be extended to work with the new
> mit-krb5.
You're welcome to submit a patch to provide the necessary support.
I'll note that the MIT schema is deficient in a number of areas too; we're
looking at writing up an IETF Draft defining a more comprehensive schema that
can be used by both MIT and Heimdal going forward.
As a total aside, the MIT code's stability leaves a lot to be desired. I won't
deploy it on any of my networks because I've seen it crash too many times. In
contrast, I've deployed Heimdal at numerous sites and never had to fuss with
it, it just works. Your Mileage May Vary, just relating my personal experience
accumulated over several years.
--
-- 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/
15 years, 10 months
