I’m very pleased to announce the release of IP Location Block 0.2.2.0. In this release, 2 new features are implemented to enhance its the protection ability against the malicious accesses. The estimated amount of true positive against preventing malicous accesses in the real world would be about 80% now.
IP Location Block 0.2.2.1 isn’t so attractive for you because there’s no new feature except several bug fixes, but it includes a very important alteration related to the IP address geolocation API for local databases of Maxmind and IP2Location. In this changelog, I’ll mention about it.
Speed performance of this plugin is one of my primary concern. In this version, I’ve enhanced the validation performance up to 25% at maximum than the previous one. So I’d like to summarize the changes in this release with other improvements.
In WordPress 4.4 and later, system.multicall XML-RPC callback is disabled since Sucuri had discovered brute force amplification attacks using this callback which can attempt thousands of authentification only by a single HTTP request. Thanks to the core team, we don’t need to worry about this type of attacks. But we still need to take care […]
Because I’m not a native english speaker, it is difficult to express something in English. After some discussions (many thanks to John), I realized again that simple and straightforward is always the best .
I’ve almost done with devoloping the next release 0.2.2.5 of IP Location Block. Before releasing this version in public, I’d ask you to test and see if the beta1 works for you. You can download it from here.
Since I already had mentioned about changes of 0.2.2.5 beta1 compared to 0.2.2.4.1 in the previous article, I don’t have much about the release version except for the compatibility of downloading IP address database zip files for Microsoft IIS from IP2Location.
I’ve developed my plugin IP Location Block as a security purpose plugin which protect the back-end of WordPress since version 2.0.0 on 2015. But since then, I’ve received many requests and suggestion that it would be better to have blocking ability on the front-end. At the time when I released version 2.0.0, I though that […]