diff options
author | Mark Felder <feld@FreeBSD.org> | 2016-08-29 19:55:47 +0000 |
---|---|---|
committer | Mark Felder <feld@FreeBSD.org> | 2016-08-29 19:55:47 +0000 |
commit | 8e2c40afaaaccff6ac3a6acf4113e9d52b1aec6f (patch) | |
tree | d79d6a496de5d89e7bb3540788e80f77fd1fbbdd /UPDATING | |
parent | 1c6c8e6f8830f08a2b04e1bcea285fe12948e22c (diff) |
Notes
Diffstat (limited to 'UPDATING')
-rw-r--r-- | UPDATING | 23 |
1 files changed, 23 insertions, 0 deletions
@@ -5,6 +5,29 @@ they are unavoidable. You should get into the habit of checking this file for changes each time you update your ports collection, before attempting any port upgrades. +20160829: + AFFECTS: users of security/sshguard + AUTHOR: feld@FreeBSD.org + + Sshguard has been updated to 1.7.0. There have been several changes to + this release. Notably the hosts and ipfilter backends are no longer + supported. If you need these backends to be supported and you missed + the survey sent out by upstream I urge you to contact upstream. + + The hosts backend was previously served by security/sshguard directly. + The additional backends were slave ports with package name suffixes. I + have opted to keep the master/slave port relationship but not choose a + specific backend for security/sshguard. Instead it is now a metaport + which will prompt you for which backend you prefer. If no backend is + configured it will depend on security/sshguard-ipfw, which is the + native FreeBSD firewall. This my be surprising to users who depended + on security/sshguard which only provided hosts/TCP Wrappers blocking, + but there is no replacement at this time. + + If the removed backends return due to user demand they will be added + as slave ports for consistency. I apologize for any inconvenience and + lack of notice on the deprecation of these features. + 20160815: AFFECTS: users of mail/rspamd* AUTHOR: vsevolod@FreeBSD.org |