Bug 167886

Summary:	init script kills all running sshd's if listening server is stopped
Product:	Red Hat Enterprise Linux 3	Reporter:	Tomas Mraz <tmraz>
Component:	openssh	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED ERRATA	QA Contact:	Brian Brock <bbrock>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.0	CC:	tao
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:	RHSA-2006-0298	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-07-20 12:53:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	170468, 181405

Description Tomas Mraz 2005-09-09 07:36:46 UTC

+++ This bug was initially created as a clone of Bug #67624 +++

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020412
Debian/1.2.0-6

Description of problem:
The init script /etc/init.d/sshd uses the function killproc from
/etc/rc.d/init.d/functions. This falls back to using the pidof command to get
PIDs for the daemon, if /var/run/[service].pid does not exist. This means that
if the ssh server is already stopped, instead of failing with "ssh server is not
running" or something similiar, it kills all other running sshd's, which,
obviously, kills everyone's connections to the server. This has a high inpact
if the server is remote and there is no easy console access.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Log on via ssh
2.run /etc/init.d/sshd stop
3.run /etc/init.d/sshd stop again.
	

Actual Results:  All ssh connections to the server were closed.

Expected Results:  It should have returned with a failure to find a process to kill.

Additional info:

-- Additional comment from bbrock on 2002-07-02 13:21 EST --
which version of openssh is installed (and showing the error)?

-- Additional comment from dom on 2002-07-08 09:06 EST --
openssh-3.1p1-5 -- the most recent security update.

-- Additional comment from tmraz on 2005-02-03 10:17 EST --
I have patch for this.

-- Additional comment from kpowell on 2005-09-08 17:57 EST --
Tomas,
    We had an Issue Tracker ticket opened on this today. Do you know when your
patch will be included in an openssh-server errata for RHEL 3 and RHEL 4? I
checked openssh-server-3.6.1p2-33.30.6 from the RHEL 3 U6 beta and it's not there.

Comment 13 Bob Johnson 2006-04-11 15:56:44 UTC

This issue is on Red Hat Engineering's list of planned work items 
for the upcoming Red Hat Enterprise Linux 3.8 release.  Engineering 
resources have been assigned and barring unforeseen circumstances, Red 
Hat intends to include this item in the 3.8 release.

Comment 16 Red Hat Bugzilla 2006-07-20 12:53:38 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2006-0298.html