Date: Fri, 18 Aug 2017 11:43:10 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 221602] security/sshguard: configuration inconvenience wrt blacklisting Message-ID: <bug-221602-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221602 Bug ID: 221602 Summary: security/sshguard: configuration inconvenience wrt blacklisting Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: bengta@sics.se CC: dan.mcgregor@usask.ca CC: dan.mcgregor@usask.ca Flags: maintainer-feedback?(dan.mcgregor@usask.ca) The sshguard rc-script supplied with the FreeBSD port always sets the commandline parameter for blacklisting. This means that any blacklist configuration in sshguard.conf will never be used. So, if you want to tweak the blacklisting, you need to do that in rc.conf, = and since you anyway need to edit sshguard.conf to set the backend, it means th= at you have to configure sshguard in two places. I find that inconvenient. I therefore propose that the port removes the default setting of sshguard_blacklist from the rc.d script, and changes the default in sshguard.conf instead! (As this is a simple change, I didn't attach a patch - I would be happy to create one if needed!) --=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-13>