[Bug 221233] security/sshguard: version 2.0 acts like a fork bomb with syslogd pipes

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221233

Kevin Zheng <kevinz5000 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kevinz5000 at gmail.com

--- Comment #11 from Kevin Zheng <kevinz5000 at 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 newsyslog.

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 trying
to use it with syslog if that's the appropriate fix.

-- 
You are receiving this mail because:
You are the assignee for the bug.