[Pkg-openssl-devel] Bug#665836: Bug#665836: openssh-server: segfault error 6 in libcrypto.so.1.0.0

[Michael Welsh Duggan]

Kurt Roeckx <kurt at roeckx.be> writes:

> On Mon, Mar 26, 2012 at 07:45:08PM +0200, Kurt Roeckx wrote:
>> On Mon, Mar 26, 2012 at 01:03:31PM -0400, Michael Welsh Duggan wrote:
>> > Kurt Roeckx <kurt at roeckx.be> writes:
>> > 
>> > > On Mon, Mar 26, 2012 at 09:20:47AM -0400, Michael Welsh Duggan wrote:
>> > >> Package: openssh-server
>> > >> Version: 1:5.9p1-4
>> > >> Severity: important
>> > >> 
>> > >> Dear Maintainer,
>> > >> 
>> > >> When connecting to my home machine while forwarding ports, I keep getting
>> > >> segfaults in sshd whenever the forwarded ports are used.  This includes
>> > >> X forwarding.  The errors that appear in my syslog look like this:
>> > >> 
>> > >> Mar 26 09:11:41 maru kernel: sshd[9320]: segfault at b8749000 ip
>> > >> b752f678 sp bfde6de0 error 6 in libcrypto.so.1.0.0[b74c6000+1a3000]
>> > >> Mar 26 09:11:52 maru kernel: sshd[10647]: segfault at b81fa008 ip
>> > >> b753b678 sp bf9d42d0 error 6 in libcrypto.so.1.0.0[b74d2000+1a3000]
>> > >> Mar 26 09:11:56 maru kernel: sshd[10680]: segfault at b8563000 ip
>> > >> b759b678 sp bfdff0a0 error 6 in libcrypto.so.1.0.0[b7532000+1a3000]
>> > >
>> > > I'm unable to reproduce this.
>> > >
>> > > I've tried using openssh-server 1:5.9p1-4 and libssl1.0.0 1.0.1-2 on the
>> > > server side, openssh-client 1:5.9p1-3 and libssl1.0.0 1.0.0h-1 on
>> > > the client side, and used ssh -X.
>> > 
>> > I am using OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 on the client side.
>> > (This client worked in previous versions.)
>> > 
>> > > I'm using an RSA key if that has anything to do with it.
>> > 
>> > I am using a DSA key.
>> > 
>> > > I didn't try anything like -L or -R, should I try those?
>> > 
>> > Did you attempt to pull use the tunneled X connection?  Nothing failed
>> > for me until I did.
>> 
>> I started a remote xterm and closed it, and then closed the ssh
>> session.
>> 
>> I've set up a tunnel using -L, and then used that tunnel.  I tried
>> to close the tunnel connection first, try to log out (and hang)
>> first, just closed the ssh connection (~.) ...
>> 
>> I'm not sure what else I can try.
>> 
>> I'm not sure what you mean with "to pull use".
>
> Can you attach gdb to the sshd, and then make it crash and
> send me a backtrace?

I'll attempt to do this, but it may take a while.  I can't do it from
here, as I am using ssh to log onto the machine running sshd, and
causing sshd to crash kills my ssh session.

-- 
Michael Welsh Duggan
(mwd at cert.org)