[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Smbk5pwd and Heimdal 0.7 not playing nice?
So, I printed out the value of context->mutex, and it's null (as seen
In regards to smbk5pwd, however, it seems any error results in slapd
coredumping. Witness Jose's problem here
The problem that's blocking progress here seems to be that heimdal is
reporting that the encryption type(s) specified in /var/heimdal/m-key aren't
supported?? In this case:
[root@ares ~]# /usr/heimdal/sbin/ktutil -k /var/heimdal/m-key list
Vno Type Principal
2 des3-cbc-sha1 K/M@GOFTI.COM
1 des3-cbc-sha1 K/M@GOFTI.COM
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com] On Behalf Of Love
> Hörnquist Åstrand
> Sent: Monday, August 01, 2005 12:19 AM
> To: Perry Nguyen
> Cc: firstname.lastname@example.org
> Subject: Re: Smbk5pwd and Heimdal 0.7 not playing nice?
> The api changed because one of the element was named
> ->close() and that
> collided with system close rewrite to support largefile. Instead of
> renameing one element, I renamed them all.
When did this name change occur, and why hasn't smbk5pwd been updated to
support this change? It seems like smbk5pwd has been a recent development
(perhaps I should ask on the openldap list, since it's "their" module). The
name change must have happened a long time ago?
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread -1208486208 (LWP 10954)]
> > 0x0077eaa2 in pthread_mutex_lock () from /lib/libpthread.so.0
> > (gdb) bt
> > #0 0x0077eaa2 in pthread_mutex_lock () from /lib/libpthread.so.0
> > #1 0x002285d6 in krb5_clear_error_string (context=0x8c50d48)
> > at error_string.c:53
> Can you print out context->mutex in thi frame, it looks like
> inits never
Breakpoint 1, krb5_clear_error_string (context=0x8a7f0d8) at
(gdb) print context->mutex
$1 = (void *) 0x0
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.7/60 - Release Date: 7/28/2005