On Mon, 28 Apr 2008, Russ Allbery wrote:
Brian May <[EMAIL PROTECTED]> writes:
Can I please confirm what version of Heimdal you are using? The initial
bug report seemed to quote the old version in testing, but here you seem
to indicate the latest version in unstable. I just want to make sure.
As far as I can tell, all exported symbols from libkrb5.24.0.0 use
HEIMDAL_KRB5_1.0 for the versioned symbol name.
ii heimdal-client 1.1-2
I'll check again tonight on amd64. The problem is specifically on amd64;
if you're checking on i386, you may not see it. I wasn't seeing any
symbol versioning in readelf.
Indeed, I have no issues on i368, only amd64... though even on i386,
I see a few @HEIMDAL_X509_1.0,
$readelf -s /usr/lib/libkrb5.so.24 | grep HEIMDAL_
$readelf -s /usr/lib/libheimntlm.so.0 | grep HEIMDAL_
$readelf -s /usr/lib/libhx509.so.3 | grepp HEIMDAL_
Whereas on i386, I see HEIMDAL_KRB5_1.0, and HEIMDAL_X509_1.0
If OpenSSH is linked against MIT Kerberos, like you say, then simply
proving that the segfault occurs inside MIT Kerberos is insufficient,
unfortunately, because we have to expect OpenSSH may call MIT Kerberos
functions at some point.
In which case, the issue should show up on i386 as well, no?
According to valgrind, the backtrace showed the segfaults definitely in
functions called by libpam-heimdal, not by openssh itself. I'll include
the backtrace when I get home and can reproduce it.
gdb doesn't produce a usable backtrace (probably because of the library
confusion). Only valgrind would work for me, and only with a rebuilt
libpam-heimdal with debugging information.
yes, I recompiled libpam-heimdal and ssh with debugging - gdb gave no
helpful information at all, and I never thought to try valgrind
--
Rick Nelson
Life'll kill ya -- Warren Zevon
Then you'll be dead -- Life'll kill ya
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
