CIDRAM Files

Version/Release 0.7.0

• [2016.12.15; Bug-fix; Maikuolan]: Files containing underscores weren't deleting when uninstalling components; Fixed.

• [2016.12.20; NEW FEATURE; Maikuolan]: Added support for simple CSV signature files (integrated directly into the already existing functionality for processing signature files; CIDRAM should be able to automatically detect whether a signature file uses the normal, default format, or CSV format). Additionally, added support for using single IPs in signature files directly, without the need for them to use complete CIDR notation (IPs that don't include a range will be interpreted seamlessly as 32's for in the case of IPv4 signature files and as 128's for in the case of IPv6 signature files).

• [2016.12.31; NEW FEATURE; Maikuolan]: Added support for optionally including additional modules into CIDRAM to run after checking IPv4/IPv6 signatures.

• [2017.01.02; Minor code change; Maikuolan]: Added the ability to track and to temporarily ban IP addresses blocked by modules.

• [2017.01.05; Bug-fix; Maikuolan]: Fixed a bug related to the dislay of reCAPTCHA instances which could arise in some specific situations when some specific configurations are used in combination with specially marked sections.

• [2017.01.05; Minor code change; Maikuolan]: Added a new directive to control the maximum number of infractions an IP is allowed to incur before it is banned by IP tracking ("infraction_limit"). Improved the readability of the front-end configuration page by including directive names alongside their descriptions and formatting accordingly. Rewrote the "Direct" closure in the loader (nothing was broken, changed functionality, and patching not required; just changed due to that a code quality checking tool I sometimes use was complaining about the way it was written before).

• [2017.01.10; Minor code change; Maikuolan]: Added several new directives: "ban_override", which allows overriding the value for "forbid_on_block" when requests from banned IPs are blocked, and allows skipping processing for the template files when processing blocked requests from banned IPs; "log_banned_ips", which allows specifying whether to include blocked requests from banned IPs in the logfiles; and "track_mode", which allows specifying whether to only track IPs blocked by modules, or to track IPs blocked for any reasons (eg, via the standard signature files as well as via the modules).

• [2017.01.12; NEW FEATURE; Maikuolan]: Added the ability to distinguish between bots masquerading as popular search engines (eg, Googlebot, Bingbot, Yahoo! Slurp) and their real, legitimate counterparts. From herein, these fake search engine bots will be blocked by default upon detection, whereas their legitimate counterparts will have IP tracking disabled by default upon detection, therefore rendering them unbannable. Added the ability to perform timed DNS lookups, both forward and reverse, along with the ability to cache the results of these lookups. Added a new directive: "default_dns".

• [2017.01.15; Bug-fixes; Maikuolan]: Bug found whereby false positives against search engines could occasionally be generated as a result of failed and incorrect DNS lookups (possible since the 2017.01.12 update); Code therefore modified as such to prevent this from occurring; Timeout limit increased and timed out lookups now result in no action being taken. Bug found whereby logging banned IPs which had exceeded the infraction limit could result in no log entry ID being parsed into log entries; Fixed.

• [2017.01.23; Sub-minor code change; Maikuolan]: "default_dns" can now be a comma delimited list, allowing fallback servers to be used for DNS lookups.

• [2017.01.24; Signatures; Maikuolan]: Further split the signature files, to keep signatures for cloud services, signatures for dangerous and spammy ISPs, and other signatures separate from each other, and to further improve modularisation.

• [2017.01.25; Sub-minor code change; Maikuolan]: Improved component ordering mechanism for the updates page.

• [2017.01.26; NEW FEATURE; Maikuolan]: Added a CIDR calculator to the front-end.

• [2017.01.27; Bug-fix; Maikuolan]: When used, "ban_override" would trigger any time any block occurred, instead of only when the infraction limit had been exceeded; Fixed.

• [2017.01.29; Bug-fix; Maikuolan]: Some versions of the DAT files used by the front-end updater for updating various components, signature files, modules, blocklists, etc, would sometimes glitch out and save several dozen duplicates of the same component entries when newly released components were detected as available for download, when those DAT files contained terminating markers at unexpected points in the file, when they contained too many terminating markers, and/or when they contained inappropriate formatting; Fixed.

• [2017.01.30; Documentation; Maikuolan]: Completed translation for the CIDRAM README documentation into Japanese (fuzzy). This totals 13 different language versions of the README documentation now available.

• [2017.01.31; Minor code change; Maikuolan]: Added a new directive to control whether the protections normally provided by CIDRAM are applied to the front-end ("protect_frontend"). Possibly useful in cases where users may be at risk of blocking themselves due to experimenting with new signatures, new modules, etc.

Caleb M / Maikuolan, 1st February 2017.