Please DISCARD the previous email where I've erroneously posted the
libraries linked to kpasswd and not to kpasswdd.
On Fri, 2018-08-03 at 14:05 -0400, Viktor Dukhovni wrote:
> > On Aug 3, 2018, at 1:43 PM, ASV <a...@inhio.net> wrote:
> >
> > No, no crashes using "kadmin -l".
>
> This shows that "kadmin" and the libkadm5srv.so library work fine.
>
> Which libraries is "kadmin" linked with (post ldd output)?
# ldd /usr/local/heimdal/bin/kadmin
/usr/local/heimdal/bin/kadmin:
Start End Type Open Ref GrpRef Name
0000031952d00000 0000031952f1c000 exe 2 0 0
/usr/local/heimdal/bin/kadmin
0000031be7982000 0000031be7b8f000 rlib 0 1 0
/usr/local/heimdal/lib/libkadm5clnt.so.3.0
0000031c15b68000 0000031c15d6c000 rlib 0 9 0
/usr/local/lib/libcom_err.so.21.0
0000031c1b05f000 0000031c1b2f5000 rlib 0 4 0
/usr/local/heimdal/lib/libkrb5.so.22.0
0000031bfbe9d000 0000031bfc147000 rlib 0 7 0
/usr/local/heimdal/lib/libasn1.so.22.0
0000031b81fe8000 0000031b821fd000 rlib 0 9 0
/usr/local/heimdal/lib/libroken.so.3.0
0000031b99afb000 0000031b99d08000 rlib 0 10 0
/usr/lib/libutil.so.13.0
0000031c2c46a000 0000031c2c694000 rlib 0 6 0
/usr/local/heimdal/lib/libwind.so.3.0
0000031c3a5b1000 0000031c3a7c1000 rlib 0 7 0
/usr/local/heimdal/lib/libheimbase.so.2.0
0000031b96fec000 0000031b97240000 rlib 0 5 0
/usr/local/heimdal/lib/libhx509.so.1.0
0000031ba3106000 0000031ba3348000 rlib 0 6 0
/usr/local/heimdal/lib/libhcrypto.so.0.0
0000031bb87b9000 0000031bb8b95000 rlib 0 7 0
/usr/lib/libcrypto.so.43.1
0000031bcda56000 0000031bcdd54000 rlib 0 5 0
/usr/local/heimdal/lib/libheimsqlite.so.1.0
0000031c30a61000 0000031c30c77000 rlib 0 1 0
/usr/local/heimdal/lib/libkadm5srv.so.3.0
0000031c213fe000 0000031c21625000 rlib 0 2 0
/usr/local/heimdal/lib/libhdb.so.3.0
0000031bed128000 0000031bed32e000 rlib 0 1 0
/usr/local/heimdal/lib/libsl.so.1.0
0000031bef6db000 0000031bef912000 rlib 0 2 0
/usr/local/heimdal/lib/libheimedit.so.1.0
0000031c26ee6000 0000031c2713c000 rlib 0 3 0
/usr/lib/libcurses.so.14.0
0000031bbe100000 0000031bbe309000 rlib 0 13 0
/usr/lib/libpthread.so.25.1
0000031b86a1f000 0000031b86cff000 rlib 0 1 0
/usr/lib/libc.so.92.3
0000031bbc700000 0000031bbc700000 ld.so 0 1 0
/usr/libexec/ld.so
> Which libraries is "kpasswdd" linked with (post ldd output) and make
> sure you're reporting the results for the right executable.
# ldd /usr/local/heimdal/libexec/kpasswdd
/usr/local/heimdal/libexec/kpasswdd:
Start End Type Open Ref GrpRef Name
00001a995ac00000 00001a995ae08000 exe 2 0 0
/usr/local/heimdal/libexec/kpasswdd
00001a9c00c4d000 00001a9c00e63000 rlib 0 1 0
/usr/local/heimdal/lib/libkadm5srv.so.3.0
00001a9b8f900000 00001a9b8fb04000 rlib 0 8 0
/usr/local/lib/libcom_err.so.21.0
00001a9ba5981000 00001a9ba5c17000 rlib 0 3 0
/usr/local/heimdal/lib/libkrb5.so.22.0
00001a9b7f5e9000 00001a9b7f893000 rlib 0 6 0
/usr/local/heimdal/lib/libasn1.so.22.0
00001a9b6757d000 00001a9b67792000 rlib 0 8 0
/usr/local/heimdal/lib/libroken.so.3.0
00001a9c23577000 00001a9c23784000 rlib 0 9 0
/usr/lib/libutil.so.13.0
00001a9c1dc73000 00001a9c1de9d000 rlib 0 5 0
/usr/local/heimdal/lib/libwind.so.3.0
00001a9c2b942000 00001a9c2bb52000 rlib 0 6 0
/usr/local/heimdal/lib/libheimbase.so.2.0
00001a9b5f9db000 00001a9b5fc2f000 rlib 0 4 0
/usr/local/heimdal/lib/libhx509.so.1.0
00001a9c2e2b5000 00001a9c2e4f7000 rlib 0 5 0
/usr/local/heimdal/lib/libhcrypto.so.0.0
00001a9c287f4000 00001a9c28bd0000 rlib 0 6 0
/usr/lib/libcrypto.so.43.1
00001a9b66371000 00001a9b6666f000 rlib 0 4 0
/usr/local/heimdal/lib/libheimsqlite.so.1.0
00001a9bc584c000 00001a9bc5a73000 rlib 0 2 0
/usr/local/heimdal/lib/libhdb.so.3.0
00001a9c40344000 00001a9c4054d000 rlib 0 11 0
/usr/lib/libpthread.so.25.1
00001a9b62ed2000 00001a9b631b2000 rlib 0 1 0
/usr/lib/libc.so.92.3
00001a9c07800000 00001a9c07800000 ld.so 0 1 0
/usr/libexec/ld.so
And yes, these are the right executable called by the rc scripts.
> > With "it worked well" I was just referring to the fact that "kadmin
> > -l cpw ..." doesn't work when kpasswdd is down
>
> That's not possible. The "kadmin -l cpw" command makes local changes
> directly in the HDB and does not use "kpasswdd". Its behaviour
> cannot
> depend on whether kpasswdd is running or not. It is operates
> silently.
Sorry that was my bad. I've verified it and the only circumstance this
could possibly happen is when the two passwords do not match. So they
did not match and it failed, silently, and it tricked me.
> > Unfortunately I don't know why you do not get enough debug.
>
> Presumably you did not install an executable with the debug symbols.
About this I do not know what to say, I've seen the CFLAGS in the
compiling output lines and I even posted in the email.
I will try again as soon as I can.
Thank you.
