[Bug 1692] sshd sometimes dies when sent multiple SIGHUPs in quick succession

[bugzilla-daemon at bugzilla.mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=1692

Darren Tucker <dtucker at zip.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dtucker at zip.com.au

--- Comment #1 from Darren Tucker <dtucker at zip.com.au> 2010-01-06 10:33:36 EST ---
Seems like a reasonable hypothesis, but I don't see the patch making
any difference.

The execv will result in an entirely new process address space
(including address layout randomization on platforms that have it) and
the disposition of the old process' signal handlers will be irrelevant.
 You'd still have a window until the signal handler is reinstalled
where the default action of SIGHUP would kill sshd.

You could minimize this window by moving the "signal(SIGCHLD,
main_sigchld_handler)" to the start of main().  This wouldn't eliminate
the window but it would shrink it a lot (particularly because the
generation of the protocol 1 ephemeral server key would no longer be in
the window).

-- 
Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.