Segmentation fault in 'sshd'

Bug #7415 reported by Debian Bug Importer
8
Affects Status Importance Assigned to Milestone
openssh (Debian)
Incomplete
Unknown
openssh (Ubuntu)
Invalid
High
Rudresh

Bug Description

Automatically imported from Debian bug report #265348 http://bugs.debian.org/265348

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #265348 http://bugs.debian.org/265348

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 12 Aug 2004 21:53:04 +0200
From: Markus Baertschi <email address hidden>
To: <email address hidden>
Subject: Segmentation fault in 'sshd'

Package: ssh
Version: 3.8.1p1-8
Severity: Critical

The sshd program segfaults after receiving the password from the
remote side.

userlinux:/var/log# sshd -ddd > /tmp/sshd.log 2>&1
(connecting to this server and attempt to login)
Segmentation fault

Please find included the logfiles from the client and server and the
coredump of the server.

I do have a similar problem with 'loadkeys' who is also coredumping on
this install (bug #265285). The cause might be in a library used by both
programs.

This is happening on a fresh install of Debian (UserLinux) in a VMWare
partition.
I've started with the latest businesscard 11th aug ISO and chose
'unstable' as documented for a UserLinux install.

Markus
--
  Markus Baertschi Phone: ++41 (21) 807 1677
  Bas du Ross�4b Fax : ++41 (21) 807 1678
  CH-1163, Etoy Email: <email address hidden>
  Switzerland Homepage: www.markus.org

Revision history for this message
In , Colin Watson (cjwatson) wrote : Re: Bug#265348: Segmentation fault in 'sshd'

On Thu, Aug 12, 2004 at 09:53:04PM +0200, Markus Baertschi wrote:
> Package: ssh
> Version: 3.8.1p1-8
> Severity: Critical
>
> The sshd program segfaults after receiving the password from the
> remote side.
>
> userlinux:/var/log# sshd -ddd > /tmp/sshd.log 2>&1
> (connecting to this server and attempt to login)
> Segmentation fault
>
> Please find included the logfiles from the client and server and the
> coredump of the server.

These were missing; I'll need them, please.

> I do have a similar problem with 'loadkeys' who is also coredumping on
> this install (bug #265285). The cause might be in a library used by both
> programs.
>
> This is happening on a fresh install of Debian (UserLinux) in a VMWare
> partition.

Do UserLinux modify any packages?

Cheers,

--
Colin Watson [<email address hidden>]

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 12 Aug 2004 23:28:23 +0100
From: Colin Watson <email address hidden>
To: Markus Baertschi <email address hidden>, <email address hidden>
Subject: Re: Bug#265348: Segmentation fault in 'sshd'

On Thu, Aug 12, 2004 at 09:53:04PM +0200, Markus Baertschi wrote:
> Package: ssh
> Version: 3.8.1p1-8
> Severity: Critical
>
> The sshd program segfaults after receiving the password from the
> remote side.
>
> userlinux:/var/log# sshd -ddd > /tmp/sshd.log 2>&1
> (connecting to this server and attempt to login)
> Segmentation fault
>
> Please find included the logfiles from the client and server and the
> coredump of the server.

These were missing; I'll need them, please.

> I do have a similar problem with 'loadkeys' who is also coredumping on
> this install (bug #265285). The cause might be in a library used by both
> programs.
>
> This is happening on a fresh install of Debian (UserLinux) in a VMWare
> partition.

Do UserLinux modify any packages?

Cheers,

--
Colin Watson [<email address hidden>]

Revision history for this message
In , Markus (markusb) wrote : 265285/265348: The kernel is the problem

Alastair, Colin,

I've done some more testing and found the the problem is dependent
of the kernel version. If I use the 2.6.7-1 kernel I have the segfaults,
when
using the 2.4.26-1 kernel everything is working.
I've heard of a problem between vmware and the 2.6 kernel since and
will follow that up.

Markus

--
  Markus Baertschi Phone: ++41 (21) 807 1677
  Bas du Rossé 14b Fax : ++41 (21) 807 1678
  CH-1163, Etoy Email: <email address hidden>
  Switzerland Homepage: www.markus.org

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 13 Aug 2004 15:56:31 +0200
From: Markus Baertschi <email address hidden>
To: <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: 265285/265348: The kernel is the problem

Alastair, Colin,

I've done some more testing and found the the problem is dependent
of the kernel version. If I use the 2.6.7-1 kernel I have the segfaults,
when
using the 2.4.26-1 kernel everything is working.
I've heard of a problem between vmware and the 2.6 kernel since and
will follow that up.

Markus

--
  Markus Baertschi Phone: ++41 (21) 807 1677
  Bas du Ross�4b Fax : ++41 (21) 807 1678
  CH-1163, Etoy Email: <email address hidden>
  Switzerland Homepage: www.markus.org

Revision history for this message
Matt Zimmerman (mdz) wrote :

Sounds like INVALID to me. Colin, do you agree?

Revision history for this message
Colin Watson (cjwatson) wrote :

Agreed. I'll downgrade it in Debian.

Revision history for this message
In , Colin Watson (cjwatson) wrote :

severity 265348 normal
tags 265348 moreinfo unreproducible
thanks

On Fri, Aug 13, 2004 at 03:56:31PM +0200, Markus Baertschi wrote:
> I've done some more testing and found the the problem is dependent
> of the kernel version. If I use the 2.6.7-1 kernel I have the segfaults,
> when
> using the 2.4.26-1 kernel everything is working.
> I've heard of a problem between vmware and the 2.6 kernel since and
> will follow that up.

OK, thanks. Let me know if you discover whether it's purely a VMware bug
or whether sshd is doing something wrong.

Cheers,

--
Colin Watson [<email address hidden>]

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 19 Aug 2004 01:19:06 +0100
From: Colin Watson <email address hidden>
To: Markus Baertschi <email address hidden>
Cc: <email address hidden>, <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: 265285/265348: The kernel is the problem

severity 265348 normal
tags 265348 moreinfo unreproducible
thanks

On Fri, Aug 13, 2004 at 03:56:31PM +0200, Markus Baertschi wrote:
> I've done some more testing and found the the problem is dependent
> of the kernel version. If I use the 2.6.7-1 kernel I have the segfaults,
> when
> using the 2.4.26-1 kernel everything is working.
> I've heard of a problem between vmware and the 2.6 kernel since and
> will follow that up.

OK, thanks. Let me know if you discover whether it's purely a VMware bug
or whether sshd is doing something wrong.

Cheers,

--
Colin Watson [<email address hidden>]

Revision history for this message
In , Colin Watson (cjwatson) wrote : categorisation

user <email address hidden>
reassign 63460 openssh-server
usertags 63460 sshd
usertags 70560 sshd
reassign 73611 openssh-server 1:2.2.0p1-1
usertags 73611 sshd
usertags 91378 ssh
reassign 117318 openssh-server 1:2.9p2-6
usertags 117318 sshd
reassign 118615 openssh-client 1:2.9p2-6
usertags 118615 ssh-add
reassign 133634 openssh-server 1:3.0.2p1-6
usertags 133634 sshd
reassign 147201 openssh-server 1:3.0.2p1-9
usertags 147201 packaging
reassign 151719 openssh-server 1:3.4p1-0.0woody1
usertags 151719 sshd
usertags 184250 sshd
usertags 197037 packaging
reassign 211424 openssh-client 1:3.6.1p2-7
usertags 211424 sftp
reassign 212787 openssh-server 1:3.6.1p2-9
usertags 212787 sshd
usertags 222839 ssh
reassign 224405 openssh-server 1:3.6.1p2-10
usertags 224405 sshd
reassign 236306 openssh-server 1:3.4p1-1.woody.3
usertags 236306 sshd
reassign 237272 openssh-server 1:3.8p1-1
usertags 237272 sshd
reassign 241119 openssh-client 1:3.6.1p2-10
usertags 241119 ssh-keyscan
reassign 265348 openssh-server 1:3.8.1p1-8
usertags 265348 sshd
reassign 298427 openssh-server 1:3.8.1p1-8.sarge.4
usertags 298427 sshd
usertags 303168 ssh
reassign 317777 openssh-server 1:3.8.1p1-8.sarge.4
# thread support was disabled in 1:4.1p1-1, so the old title no longer
# makes sense; borrow the upstream bug title instead
retitle 317777 PAM modules relying on module-private data (pam_dhkeys, pam_krb5, AFS) fail
forwarded 317777 https://bugzilla.mindrot.org/show_bug.cgi?id=688
usertags 317777 sshd
reassign 321523 openssh-client 1:3.8.1p1-8.sarge.4
usertags 321523 ssh
reassign 326027 openssh-server 1:3.8.1p1-8.sarge.4
usertags 326027 sshd
usertags 350825 ssh
usertags 350826 ssh
usertags 352508 sshd
reassign 357469 openssh-client 1:3.8.1p1-8.sarge.4
usertags 357469 ssh-agent
usertags 365884 ssh
usertags 389338 packaging
usertags 390344 ssh-copy-id
usertags 398789 packaging
usertags 419574 packaging
usertags 428082 sftp
usertags 429243 packaging
usertags 448589 scp
usertags 465104 packaging
usertags 475107 ssh-keygen
usertags 481133 sshd
usertags 481238 ssh
usertags 481250 ssh
usertags 481251 sshd
usertags 482806 packaging
usertags 486287 scp
usertags 500192 sshd
usertags 500573 ssh
usertags 505293 packaging
usertags 505657 ssh
usertags 509443 ssh
usertags 517641 ssh-copy-id
usertags 531070 sshd
usertags 531561 sftp
usertags 543683 sshd
usertags 546923 sshd
reassign 550260 openssh-server 1:5.1p1-8
usertags 550260 sshd

--
Colin Watson [<email address hidden>]

Rudresh (rudresh)
Changed in openssh (Ubuntu):
assignee: Colin Watson (cjwatson) → Rudresh (rudresh)
Revision history for this message
Rudresh (rudresh) wrote :

Subject: The kernel version is the problem

Rudresh,

I think the problem you are facing is dependent on the kernel version.
Try using different kernel version.
I've heard of a problem between vmware and the kernel(the version which you are using now).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.