Thread 3 "slapd" hit Breakpoint 1, 0x00007ffff741a1c0 in krb5_init_context ()
from /usr/lib/x86_64-linux-gnu/libkrb5.so.3
(gdb) bt
#0 0x00007ffff741a1c0 in krb5_init_context () from
/usr/lib/x86_64-linux-gnu/libkrb5.so.3
#1 0x00007ffff68e486c in smbk5pwd_modules_init (pi=<optimized out>) at
smbk5pwd.c:1000
That is the wrong krb5_init_context, we want the Heimdal one!
# ldd /usr/lib/ldap/smbk5pwd.so | grep krb5
libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26
(0x00007f78ce2f3000)
libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2
(0x00007f78cdb87000)
libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3
(0x00007f78cdaaa000)
libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0
(0x00007f78cd340000)
This looks like a change in libsasl2-2:
Package: libsasl2-2
Version: 2.1.27~101-g0780600+dfsg-3
Depends: libsasl2-modules-db (>= 2.1.27~101-g0780600+dfsg-3), libc6 (>= 2.15)
Package: libsasl2-2
Version: 2.1.27~rc8-1
Depends: libsasl2-modules-db (>= 2.1.27~rc8-1), libc6 (>= 2.15), libcom-err2 (>=
1.43.9), libgssapi-krb5-2 (>= 1.6.dfsg.2), libk5crypto3 (>= 1.6.dfsg.2), libkrb5-3 (>=
1.6.dfsg.2)
(I really need to create some autopkgtests to catch this sort of thing!)
