Bug#332863: SEGV on connect to sshd
> On Mon, Oct 10, 2005 at 06:43:00AM -0400, Simon Raven wrote:
>> On 10 October, 2005 04:51, Colin Watson wrote:
>> > Very likely you have some PAM modules linked against an older version of
>> > OpenSSL; you will have to push to get those upgraded so that they're in
>> > sync with sshd's linkage (0.9.8). There's nothing I can do about this in
>> > OpenSSH because OpenSSL doesn't use versioned symbols; if I'd waited for
>> > the PAM modules to be upgraded, you'd still have seen segfaults, just
>> > (so to speak) the other way round.
>>
>> oh ok. so i can wait around for that to happen, and/or fix it up myself
>> locally, until then. thanks dude (hope you don't mind the "dude" thing).
>
> I'll close this for now, then. If you can identify which modules are
> problematic for you and let us know, that would be useful.
sure, go ahead, make my day ;p. but seriously, doesn't openssl 0.9.8x have
versioned symbols now? not sure exactly what that means, except my suspicion
that the symbols present in the library(ies) have versions, hence an indicator
on how to treat it, for instance, building things against it (AIUI).
i suspect it'd be pam_ldap and pam_heimdal, if anything. i found that on
openldap 2.2.26, built against openssl 0.9.7x, the kerby stuff fails to work
properly when i do a 'ldapwhoami', but with say oldap 2.3.7+patches (fixes for
mem leaks, rootdn grokking for cn=config/back-config, and other ones), it
works fine.
i know part of what i'm doing is unsupported, but i suppose doing this also
helps to find bugs in things.
HTH
sr/
> Cheers,
>
> --
> Colin Watson [cjwatson@debian.org]
>
Reply to: