Richard A Nelson [EMAIL PROTECTED] writes:
It got further (into pam_session), and having learned from Russ, I fired
up valgrind and found it failing in another MIT routine, but after
rebuilding libpam_heimdal, it looks like things are once again golden :)
Brian, you may want to request
30 apr 2008 kl. 23.39 skrev Russ Allbery:
Love Hörnquist Åstrand [EMAIL PROTECTED] writes:
How about using libtool ? Can you test this patch ?
http://www.h5l.org/fisheye/changelog/heimdal/?cs=23146
Yup, this works, although it produces a bunch of spurious output in
the
middle of the
Love Hörnquist Åstrand [EMAIL PROTECTED] writes:
How about using libtool ? Can you test this patch ?
http://www.h5l.org/fisheye/changelog/heimdal/?cs=23146
Yup, this works, although it produces a bunch of spurious output in the
middle of the configure run (I think because libtool is trying to
To provide a bit of additional information (I should have pasted in
the
config.log output as well), the existing check fails on x86_64
because it
uses -shared to link the test object but doesn't use -fPIC. This
works on
x86, but other platforms, such as x86_64, require all objects that
Love Hörnquist Åstrand [EMAIL PROTECTED] writes:
How about using libtool ? Can you test this patch ?
http://www.h5l.org/fisheye/changelog/heimdal/?cs=23146
Oh, yeah, that's a good idea. I'll be able to test this tomorrow evening.
--
Russ Allbery ([EMAIL PROTECTED])
Russ Allbery wrote:
I spent an hour this evening tracking this down. The problem is that
Heimdal isn't using symbol versioning in its shared libraries.
libpam-heimdal therefore binds to unversioned symbols, which works fine if
the calling program doesn't load any other Kerberos library.
Brian May wrote:
It occurred to me that the stack trace is probably in the Debian bug
report, I will check that now.
I can't seem to find the stack trace with debugging information, if you
still have a copy can you please send it to the BTS?
Thanks.
--
To UNSUBSCRIBE, email to [EMAIL
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
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.
Richard A Nelson wrote:
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_
This was
Russ Allbery [EMAIL PROTECTED] writes:
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.
On Mon, 21 Apr 2008, Russ Allbery wrote:
I spent an hour this evening tracking this down. The problem is that
Heimdal isn't using symbol versioning in its shared libraries.
libpam-heimdal therefore binds to unversioned symbols, which works fine if
the calling program doesn't load any other
Richard A Nelson [EMAIL PROTECTED] writes:
I found some odd news!
After building openssh on a recent Sid box, the pam account module
now works as expected - no segv :) This, along with the fact that
there's a new openssh version (with supposed changes in this area),
makes it seem like
On Sun, 13 Apr 2008, Matthijs Mohlmann wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Can you try with ssh and debugging symbols on ? Probably you get more
information with gdb then.
Being that there are no debug packages for openssh, I rebuilt it
on a current Sid machine (with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Can you try with ssh and debugging symbols on ? Probably you get more
information with gdb then.
I'll ask also the upstream maintainer.
Russ: Can you take a look at this bug report. It seems that sshd is
segfaulting on AMD64 when using the
Matthijs Mohlmann [EMAIL PROTECTED] writes:
Can you try with ssh and debugging symbols on ? Probably you get more
information with gdb then.
I'll ask also the upstream maintainer.
Russ: Can you take a look at this bug report. It seems that sshd is
segfaulting on AMD64 when using the
# /usr/sbin/sshd -Dddd ~/log 21
Segmentation fault
The last lines of log:
debug3: mm_auth_password entering
debug3: mm_request_send entering: type 11
debug3: mm_auth_password: waiting for MONITOR_ANS_AUTHPASSWORD
debug3: mm_request_receive_expect entering: type 12
debug3: mm_request_receive
Ah, a little more information - this segv only happens when using
password authentication (ssh keys work fine)
sshd_config has
UsePAM yes
PubkeyAuthentication yes
PasswordAuthentication yes
ChallengeResponseAuthentication no
Richard Nelson wrote:
# /usr/sbin/sshd -Dddd ~/log 21
Segmentation
18 matches
Mail list logo
