non port: security/sshguard/files/sshguard.in |
SVNWeb
|
Number of commits found: 21 |
Fri, 1 Apr 2022
|
[ 15:09 Dmitry Marakasov (amdmi3) ] dc24d94
security/sshguard: disable blacklisting by default
Blacklisting is now disabled by default to avoid overriding the setting in
sshguard.conf. To enable blacklisting, uncomment the BLACKLIST_FILE line in
sshguard.conf.
PR: 221602
Reported by: bahlgren@beah.se
Submitted by: kevinz5000@gmail.com
|
Tue, 6 Apr 2021
|
[ 14:31 Mathieu Arnold (mat) ] 135fdee (Only the first 10 of 2028 ports in this commit are shown above. )
all: Remove all other $FreeBSD keywords.
|
Fri, 19 Jul 2019
|
[ 02:09 adamw ]
sshguard: Fix rc(8) script, broken in update and then broken further in followup
commits
Also clean up some comments while here.
PR: 238458
Submitted by: Kevin Zheng
|
Sat, 6 Jul 2019
|
[ 15:33 adamw ]
sshguard: Update to 2.4.0 and fix rc(8) script
There is some strange new behaviour on the rc script in 2.4.0. It
would either hang on start, or hang on stop. A custom stop function
seemed the easiest way to achieve both.
PR: 238458
|
Mon, 1 Jul 2019
|
[ 17:56 adamw ]
Back out r505456. sshguard 2.4.0 misbehaves
SSHGuard has always exited cleanly on FreeBSD. In 2.4.0, sshguard fixed that.
It is impossible to terminate sshguard without manually killing each process.
So, apologies to everyone who's already updated, but you'll have to manually
kill all the processes:
pkill -f sshguard
pkill -f sshg-
pkill -f tail
rm /var/run/sshguard.pid
So, back this out while awaiting upstream fix.
PR: 238458
|
[ 00:57 adamw ]
Fix rc(8) script process detection
The pidfile points to a process named sh, not sshg-blocker
PR: 238458
|
Mon, 28 May 2018
|
[ 01:30 adamw ]
Increase the default blacklist threshold from 30 to 120, which is the upstream
default. 30 makes it far too easy to get locked out of your own server. 120 is
simply a safer starting point.
PR: 227016
Submitted by: Dan McGregor (maintainer)
MFH: 2018Q2
|
Mon, 24 Jul 2017
|
[ 10:56 woodsb02 ]
security/sshguard: Fix rc script, add UPDATING entry
sshguard usually looks at sshguard.conf for a list of files to monitor,
but lets you override it via the command line using -l arguments.
This change fixes an issue with the previous rc script which was
*always* setting the '-l' arguments even if sshguard_watch_logs wasn't
set in rc.conf.
This change also sets the defaults in the config file to match the
former defaults in the rc script, and adds an UPDATING entry to warn
of the change from default configuration via rc.conf the config file.
PR: 220906
Submitted by: Dan McGregor (maintainer)
Reported by: chris@cretaforce.gr
|
Thu, 20 Jul 2017
|
[ 15:34 feld ]
security/sshguard: Update to 2.0.0
PR: 219409
|
Mon, 2 May 2016
|
[ 16:49 feld ]
security/sshguard: Update man page, fix sshguard_reset_interval default
Upstream responded to my submitted man page patch and indicated that
sshguard_reset_interval (-s) has been changed to 1800 (30 mins) as well.
|
[ 16:26 feld ]
security/sshguard: Update to 1.6.4
- Add PID file support back to rc script
- Rename some rc script parameters to better align with sshguard(8)
sshguard_safety_thresh -> sshguard_danger_thresh
sshguard_pardon_min_interval -> sshguard_release_interval
sshguard_prescribe_interval -> sshguard_reset_interval
Release notes:
This release brings updated signatures, usability improvements, and bug
fixes. Highlights in this release include:
- Match Postfix pre-authentication disconnects (Only the first 15 lines of the commit message are shown above )
|
Tue, 8 Mar 2016
|
[ 16:20 feld ]
security/sshguard: Update to 1.6.3
Changelog: https://sourceforge.net/p/sshguard/mailman/message/34733464/
PR: 207511
Submitted by: <dcarmich@dcarmichael.net>
|
Thu, 8 Jan 2015
|
[ 13:42 feld ]
Add ability to pass additional custom arguments to sshguard daemon via
sshguard_flags in rc.conf
Declare LICENSE while here
Submitted by: wjw@digiware.nl
|
Mon, 3 Nov 2014
|
[ 21:56 feld ]
Make it possible to run sshguard without blacklist database by setting
in rc.conf:
sshguard_blacklist=""
This may fix reliability for some users.
PR: 174018
|
[ 21:11 feld ]
Do not hide stdout from users by sending it to syslog. Users need to be
able to readily view errors if they happen at startup.
PR: 193378
|
Thu, 2 Oct 2014
|
[ 12:28 feld ]
The default pardon and prescribe settings in the rc script were swapped
and did not match the documentation. Users should tune to their needs
instead of relying on the defaults, but if they are this will be an
improvement.
Submitted by: John Vinopal
|
Thu, 22 May 2014
|
[ 13:17 feld ]
Adopting security/sshguard
rc script passes rclint
Removed clever built-in sysadmin countermeasure:
Previously sshguard would automatically add a line to your
/etc/syslog.conf file. You could activate sshguard by uncommenting this
line. However, every time you reinstall/update sshguard this line will
also be automatically removed rendering the program inactive and your
system unprotected.
Sponsored by: SupraNet Communications, Inc
|
Fri, 25 Apr 2014
|
[ 13:08 crees ]
Fix rc script, which I made a bit of a mess of. Really sorry :(
Submitted by: se
While here, add error checking in pkg-install before replacing
syslog.conf with an unknown file!
|
Tue, 8 Apr 2014
|
[ 19:03 crees ]
Fix old sshguard bug; does not detect ssh invalid users logins
PR: ports/174571
Submitted by: Francois Charlier <fcharlier@ploup.net>
Reset maintainer after 16 month timeout
While here, stage, remove some insanity and fixup rc script
|
Fri, 1 Feb 2013
|
[ 15:04 ak ] (Only the first 10 of 137 ports in this commit are shown above. )
- Fix all cases of 'No newline at end of file' in ports tree
Approved by: portmgr (bapt)
|
Wed, 27 Jun 2012
|
[ 00:22 delphij ]
Add a rc.d script to daemonize sshguard.
Submitted by: delphij
PR: ports/166471
Approved by: maintainer timeout (~3 months)
|
Number of commits found: 21 |