Date: Wed, 17 Feb 2021 07:39:37 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 221602] security/sshguard: configuration inconvenience wrt blacklisting Message-ID: <bug-221602-7788-2h3KvWFx72@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221602-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-221602-7788@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=3D221602 --- Comment #5 from Kevin Zheng <kevinz5000@gmail.com> --- Created attachment 222508 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D222508&action= =3Dedit Patch I've attached a patch with the requested changes. More detail is in the pat= ch body, which is reproduced below: The sshguard_blacklist rcvar always overrides the setting in sshguard.conf. Since the rc.d script sets sshguard_blacklist, the blacklist option in sshguard.conf is never used. This patch removes the default rcvar setting, and instead enables blacklisting in the example sshguard.conf. (Note that this is a traditional FreeBSD ports default, not an upstream default.) New users (with no existing sshguard.conf) will see no change. Users with existing sshguard.conf will have blacklisting turned off until they update their sshguard.conf. Though, I want to ask those CC'd on the patch here, what do you think about leaving blacklisting off by default? --=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-221602-7788-2h3KvWFx72>