An embedded message was scrubbed... From: Tor.Egge at cvsup.no.freebsd.org Subject: sshd unable to restart Date: Sun, 25 May 2003 18:19:08 GMT Size: 2853 Url: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20030528/47273c0e/attachment.mht
Dag-Erling Smorgrav wrote:> In FreeBSD-CURRENT, sshd cores when it tries to restart after > receiving a SIGHUP, because the argv passed to execv() is not > terminated by a NULL pointer.This has already been addressed in the OpenSSH CVS tree: 20030515 - (djm) Bug #529: sshd doesn't work correctly after SIGHUP (copy argv correctly) -- Darren Tucker (dtucker at zip.com.au) GPG Fingerprint D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
Dag-Erling Smorgrav wrote:> In FreeBSD-CURRENT, sshd cores when it tries to restart after > receiving a SIGHUP, because the argv passed to execv() is not > terminated by a NULL pointer.Thanks, that was bug #529, a fix was committed a couple of weeks ago. -d
Reasonably Related Threads
- [Fwd: Kerberos buglet in OpenSSH-3.3p1]
- Perl version in -STABLE
- CVS Revision Tag Date Format Question
- [Bug 315] New: add miissing includes and defines for FREEBSD
- Option to limiting sshd "banner" to interactive/password-auth/tty (or something along those lines) sessions