CIDRAM Files

Version/Release 1.4.0

• [2017.12.24; Sub-minor code change; Maikuolan]: Signature file extended run rule closures can now return exit codes to trigger greylist or whitelist mechanisms. Improved default signature bypasses so that CIDRAM can play more nicely with Bingbot (occasional false positives with requests originating from Azure ranges). Slightly improved logs filtering and search mechanism.

• [2017.12.26; Sub-minor code change; Maikuolan]: Root check safeguard added to the "DNS-Reverse" closure.

• [2017.12.27; Minor code change; Maikuolan]: Optional fallback added to "DNS-Reverse" closure for "gethostbyaddr" (can be toggled via a newly added configuration directive).

• [2017.12.30; NEW FEATURE; Maikuolan]: Added flag support to the front-end logs page (it should now be possible to filter log entries on the basis of country flags, if any were indicated by the signatures triggered for them).

• [2018.01.11; Sub-minor code change; Maikuolan]: Not technically a bug, but DNS lookups shouldn't be performed on localhost addresses due to the risk of false positives. Code modified accordingly.

• [2018.01.14; NEW FEATURE; Maikuolan]: Added a "Sections List" page to the front-end (lists all the sections in the signature files and counts the total number of sections and signatures throughout all the signature files).

• [2018.01.16; Bug-fix; Maikuolan]: Direct closure sometimes produced errors when running CIDRAM via Cron (e.g., via Cronable) due to SCRIPT_FILENAME sometimes not being defined in that context; Fixed via isset check.

• [2018.01.18; Sub-minor code change; Maikuolan]: Performed some minor refactoring. Added checks for origin tags to the CLI signature file validator and fixer. Sections list now checks whether sections have been ignored.

• [2018.01.20; Sub-minor code change; Maikuolan]: Slightly improved CLI-mode help information.

Caleb M (Maikuolan), Jan 20, 2018.