Date: Wed, 06 Dec 2017 22:00:31 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 221233] security/sshguard: version 2.0 acts like a fork bomb with syslogd pipes Message-ID: <bug-221233-13-cdnKHh7G1l@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221233-13@https.bugs.freebsd.org/bugzilla/> References: <bug-221233-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221233 Kevin Zheng <kevinz5000@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kevinz5000@gmail.com --- Comment #11 from Kevin Zheng <kevinz5000@gmail.com> --- I'm from SSHGuard upstream. One of the intentional breaking changes in 2.x was that you're not supposed= to run SSHGuard from syslogd. Many people have been reporting that syslogd correctly SIGHUPs its child processes when it receives a SIGHUP from newsys= log. It seems that the changes weren't breaking enough; people are still able to pipe to SSHGuard even though we explicitly don't support that. I can try to get SSHGuard to exit immediately after it looks like you're tr= ying to use it with syslog if that's the appropriate fix. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221233-13-cdnKHh7G1l>