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 |