Your message dated Tue, 22 Dec 2009 09:49:34 +1100
with message-id <20091221224934.gb4...@sys11.in.vpac.org>
has caused the report #561850,
regarding Segfaults with smartcard
to be marked as having been forwarded to the upstream software
author(s) heimdal-b...@h5l.se
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
561850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Hello,
I received this bug report against Heimdal. For the full report, including the
first stack trace I omitted, see http://bugs.debian.org/561850.
My initial thought was this might be another case of library symbols
conflicting from different shared libraries. If I had to gamble, I would say
that is not the case though.
Unfortunately I have never used smartcard support, so am not familiar with how
it works.
Thanks
On Sun, Dec 20, 2009 at 05:50:00PM +0100, Guido Günther wrote:
> since the upgrade to 1.3.1.dfsg.1 I'm seeing:
>
> [....]
>
> once I turn of smartcard usage (PKCS11:/usr/lib/opensc/opensc-pkcs11.so)
> krb5-auth-dialog works as expected. I didn't dig further yet since
> heimdal doesn't ship a debugging package.
On Mon, Dec 21, 2009 at 09:39:11PM +0100, Guido Günther wrote:
> There's a backtrace with debug symbols:
>
> #0 0xb6b23bf2 in _hx509_ks_type (context=0x0, name=0xb6b3cf12
> "MEMORY:locks-internal", flags=0, lock=0x0, certs=0x92738e8) at keyset.c:71
> #1 hx509_certs_init (context=0x0, name=0xb6b3cf12 "MEMORY:locks-internal",
> flags=0, lock=0x0, certs=0x92738e8) at keyset.c:141
> #2 0xb6b2943e in hx509_lock_init (context=0x0, lock=0xbfb66258) at lock.c:71
> #3 0xb769b37d in _krb5_pk_load_id () from /usr/lib/libkrb5.so.26
>
> The problem is that were dereferencing context in _hx509_ks_type which
> is NULL.
--
Brian May <b...@snoopy.debian.net>
--- End Message ---
