Menu
▾
▴
sshguard-users
|
From: Kevin Z. <kev...@gm...> - 2017-11-09 08:28:17
Attachments:
signature.asc
|
SSHGuard 2.1.0 is available. Added - Add **nftables** backend - Add monitoring support for new service: Cockpit, Linux server dashboard - Match "maximum authentication attempts" for SSH - Match Debian-style "Failed password for invalid user" for SSH - Add monitoring support for new service: Common webserver probes, in Common Log Format - Match 'Disconnecting invalid user' for SSH - Add monitoring support for new service: WordPress, in Common Log Format - Add monitoring support for new service: SSHGuard - Firewall backends now support blocking subnets. - Add new IPV6_SUBNET and IPV4_SUBNET configuration options. Defaults to traditional single-address blocking. Changed - Log whitelist matches with higher priority Fixed - Match port number in "invalid user" attack - FirewallD backend reloads firewall configuration less often. -- Kevin Zheng kev...@gm... | ke...@be... | PGP: 0xC22E1090 |
|
From: Jos C. <ssh...@cl...> - 2017-12-02 19:26:08
|
Dear team,, Thanks, that is good news! Just to inform you that currently sshguard-2.0.0_1 is the most recent update of the FreeBSD ports collection. Dan, can you push 2.1.0 to our FreeBSD ports community? Thanks and keep up the good work, BR, Jos Op 9-11-2017 om 9:28 schreef Kevin Zheng: > SSHGuard 2.1.0 is available. > > Added > - Add **nftables** backend > - Add monitoring support for new service: Cockpit, Linux server dashboard > - Match "maximum authentication attempts" for SSH > - Match Debian-style "Failed password for invalid user" for SSH > - Add monitoring support for new service: Common webserver probes, in > Common Log Format > - Match 'Disconnecting invalid user' for SSH > - Add monitoring support for new service: WordPress, in Common Log Format > - Add monitoring support for new service: SSHGuard > - Firewall backends now support blocking subnets. > - Add new IPV6_SUBNET and IPV4_SUBNET configuration options. Defaults to > traditional single-address blocking. > > Changed > - Log whitelist matches with higher priority > > Fixed > - Match port number in "invalid user" attack > - FirewallD backend reloads firewall configuration less often. > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > sshguard-users mailing list > ssh...@li... > https://lists.sourceforge.net/lists/listinfo/sshguard-users -- With both feed on the ground you will never make a step forward |
|
From: Jos C. <ssh...@cl...> - 2017-12-06 19:37:44
|
Is there a port maintainer who can respond? Thanks, Jos Op 2-12-2017 om 20:05 schreef Jos Chrispijn: > Dear team,, > > Thanks, that is good news! > > Just to inform you that currently sshguard-2.0.0_1 is the most recent > update of the FreeBSD ports collection. > > Dan, can you push 2.1.0 to our FreeBSD ports community? > > Thanks and keep up the good work, > BR, Jos > > > Op 9-11-2017 om 9:28 schreef Kevin Zheng: >> SSHGuard 2.1.0 is available. >> >> Added >> - Add **nftables** backend >> - Add monitoring support for new service: Cockpit, Linux server dashboard >> - Match "maximum authentication attempts" for SSH >> - Match Debian-style "Failed password for invalid user" for SSH >> - Add monitoring support for new service: Common webserver probes, in >> Common Log Format >> - Match 'Disconnecting invalid user' for SSH >> - Add monitoring support for new service: WordPress, in Common Log Format >> - Add monitoring support for new service: SSHGuard >> - Firewall backends now support blocking subnets. >> - Add new IPV6_SUBNET and IPV4_SUBNET configuration options. Defaults to >> traditional single-address blocking. >> >> Changed >> - Log whitelist matches with higher priority >> >> Fixed >> - Match port number in "invalid user" attack >> - FirewallD backend reloads firewall configuration less often. |
|
From: Kevin Z. <kev...@gm...> - 2017-12-06 22:38:11
|
On 12/06/2017 11:37, Jos Chrispijn wrote: > Is there a port maintainer who can respond? I've submitted an update here, pending maintainer approval: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224153 -- Kevin Zheng kev...@gm... | ke...@be... | PGP: 0xC22E1090 |
|
From: Jason de C. <ja...@av...> - 2017-12-06 20:08:46
|
Hey all! Last time there was a major upgrade on FreeBSD it was a more draconian experience than graceful one... In their defense, it was only lacking in documentation not implementation esp. the consolidation of the related fw ports into a single one and new config setup. Good to see some FreeBSD folks here! Oclair On 12/6/17 20:37, Jos Chrispijn wrote: > Is there a port maintainer who can respond? > Thanks, Jos > > Op 2-12-2017 om 20:05 schreef Jos Chrispijn: >> Dear team,, >> >> Thanks, that is good news! >> >> Just to inform you that currently sshguard-2.0.0_1 is the most >> recent update of the FreeBSD ports collection. >> >> Dan, can you push 2.1.0 to our FreeBSD ports community? >> >> Thanks and keep up the good work, >> BR, Jos >> >> >> Op 9-11-2017 om 9:28 schreef Kevin Zheng: >>> SSHGuard 2.1.0 is available. >>> >>> Added >>> - Add **nftables** backend >>> - Add monitoring support for new service: Cockpit, Linux server dashboard >>> - Match "maximum authentication attempts" for SSH >>> - Match Debian-style "Failed password for invalid user" for SSH >>> - Add monitoring support for new service: Common webserver probes, in >>> Common Log Format >>> - Match 'Disconnecting invalid user' for SSH >>> - Add monitoring support for new service: WordPress, in Common Log Format >>> - Add monitoring support for new service: SSHGuard >>> - Firewall backends now support blocking subnets. >>> - Add new IPV6_SUBNET and IPV4_SUBNET configuration options. Defaults to >>> traditional single-address blocking. >>> >>> Changed >>> - Log whitelist matches with higher priority >>> >>> Fixed >>> - Match port number in "invalid user" attack >>> - FirewallD backend reloads firewall configuration less often. > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > sshguard-users mailing list > ssh...@li... > https://lists.sourceforge.net/lists/listinfo/sshguard-users |
|
From: Kevin Z. <kev...@gm...> - 2017-12-06 21:51:00
|
On 12/06/2017 11:50, Jason de Cordoba wrote: > Hey all! > > Last time there was a major upgrade on FreeBSD it was a more draconian > experience than graceful one... > > In their defense, it was only lacking in documentation not > implementation esp. the consolidation of the related fw ports into a > single one and new config setup. Some feedback on how to make breaking changes would be good for us. The update from 1.7.1 to 2.0.0 was supposed to be breaking. The port used to have several slave ports because the firewall selection was compiled into the binary. Perhaps a better fix would have been to keep the slave ports that each shipped with a different default configuration file, but I thought that was more trouble than it was worth. The breakage for running sshguard from syslog was intentional. Too many users reported that syslogd would SIGHUP sshguard. As always we appreciate feedback on how to make things better. -- Kevin Zheng kev...@gm... | ke...@be... | PGP: 0xC22E1090 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X