Bug 690391 - When you send two SIGHUP signals to sshd in quick succession (to reload it configuration), sshd dies.
Summary: When you send two SIGHUP signals to sshd in quick succession (to reload it co...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openssh
Version: 6.0
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: 6.1
Assignee: Jan F. Chadima
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 682670
TreeView+ depends on / blocked
 
Reported: 2011-03-24 07:40 UTC by Brad Hubbard
Modified: 2018-11-14 13:37 UTC (History)
5 users (show)

Fixed In Version: openssh-5.3p1-51.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 13:31:05 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0598 0 normal SHIPPED_LIVE openssh bug fix and enhancement update 2011-05-19 09:37:32 UTC

Description Brad Hubbard 2011-03-24 07:40:43 UTC
Description of problem:
When you send two SIGHUP signals to sshd in quick succession (to reload it configuration), sshd dies.

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


How reproducible:
At will.

Steps to Reproduce:
1. killall -s SIGHUP sshd && killall -s SIGHUP sshd
2. service sshd status
3.
  
Actual results:
openssh-daemon dead but pid file exists

Expected results:
openssh-daemon (pid  2522) is running...

Additional info:

Comment 4 Jan F. Chadima 2011-03-30 14:19:33 UTC
added to openssh-5.3p1-51

Comment 7 errata-xmlrpc 2011-05-19 13:31:05 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 therefore 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/RHBA-2011-0598.html


Note You need to log in before you can comment on or make changes to this bug.