Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#47667 - [sshguard] threshold and -l parameters
Attached to Project:
Community Packages
Opened by till busch (buti) - Friday, 08 January 2016, 09:48 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 08 January 2016, 13:05 GMT
Opened by till busch (buti) - Friday, 08 January 2016, 09:48 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 08 January 2016, 13:05 GMT
|
Detailsfor some reason the threshold parameter in -b has become mandatory, also the semantics of -l has changed. please consider the following changes:
remove -l- from sshguard-journalctl rationale: sshguard will parse stdin if no -l option is given. it will also not do excessive logging. this means you can remove this "patch"/hack: sed -i 's|sshguard_log(LOG_INFO, "Refreshing sources showed|sshguard_log(LOG_DEBUG, "Refreshing sources showed|' src/sshguard_logsuck.c change threshold for blacklisting to 120 rationale: i think 120 was the previous default. while 40 blacklists the ip forever immediately 120 will block temporarily two times and blacklist on the third attack – each attack being 4 (?) failed logins. |
This task depends upon
0001-remove-l-option.patch