Rename function to not clash with pfsense one
Use the newer snort port version 2.9.4.1
Correct the package name. To many 1
Move to latest available rulesets
Fix binary names for snort deps
Set correct VRT Rules tarball for Snort 2.9.4.1
Merge pull request #411 from bmeeks8/master

Fix VRT rules tarball filename so 2.9.4.1 rules download instead of 2.9.4.0
Fix preproc auto-rule disable to skip disabled rules.
Merge pull request #412 from bmeeks8/master

Fix logic bug in preproc auto-rule-disable so it skips already disabled rules
Disconnect snort-dev from the package lists since it gives problems on rebuilding snort and snort-dev due to different binary requirements
advanced bind options, extended username/password characters+escaping, change deprecated options to current equivalents, changed nbproc default to 1, for better (default settings) compatibility with other options.
Merge pull request #414 from PiBa-NL/haproxy-devel-2.1

advanced bind options, extended username/password characters+escaping, c...
Correctly generate the hex value needed for md5sigkey value. Use correct permissions for configuration file when generating
Actually the md5sigkey is directly given in hex revert partially previous commit
No need anymore for the setkey command
Do not make mandatory the local addr but use the listenip if local address is not set to easy configuration same as was previously done with setkey
Correctly write config file and also properly avoid php errors with some extra safety belts
Correct permission otherwise openbgpd does not start
pfBlocker allow list ranges that are not exact subnets

Fixes #2892
I made a "nasty" list as follows:
192.168.100.0-192.168.101.255
192.168.103.8-192.168.103.23
192.168.104.1-192.168.104.254
192.168.105.22-192.168.106.66
192.168.107.3-192.168.107.33
And this code turns it into:
192.168.100.0/23
192.168.103.8/29
192.168.103.16/29
192.168.104.1/32
192.168.104.2/31
192.168.104.4/30
192.168.104.8/29
192.168.104.16/28
192.168.104.32/27
192.168.104.64/26
192.168.104.128/26
192.168.104.192/27
192.168.104.224/28
192.168.104.240/29
192.168.104.248/30
192.168.104.252/31
192.168.104.254/32
192.168.105.22/31
192.168.105.24/29
192.168.105.32/27
192.168.105.64/26
192.168.105.128/25
192.168.106.0/26
192.168.106.64/31
192.168.106.66/32
192.168.107.3/32
192.168.107.4/30
192.168.107.8/29
192.168.107.16/28
192.168.107.32/31
Which is the correct group of CIDRs to represent the given ranges.
Merge pull request #415 from phil-davis/master

pfBlocker allow list ranges that are not exact subnets