use a better/ different list

Hi,

This is very late – only saw the post recently. I just released a new version (1.3.1) which searches a full Tor relay list instead of only exits. I’ve noticed lately when testing Tor requests that the exit node being used doesn’t have the “Exit” flag set in the directory which is what the previous list was using. Not sure why (maybe a delay in consensus) but in any case it will now use the full relay list which should be a bit more accurate for these cases.

I’ll think about also adding arbitrary IP lists but I think there are other plugins that already provide this. Using hostnames like that would also require a reverse DNS lookup for each new IP seen which could add some delay to each page load.

So, hopefully, it should be more accurate now… I will update and test =)

I understand… but it would be nice to have that option, why add another plugin or edit .htaccess if it can be done all in the same place. Maybe just put a warning that entering domains may make the web page take longer to load.

The update list function every 1 hour is not working! The 10 minutes works fine, so it is something in the 1 hour that is missing (maybe in file “vigilantor.php”):

$this->_updateFrequencies = array(
‘_10m’ => array(‘interval’ => 600, ‘display’ => __(‘Every 10 minutes’)),
‘_20m’ => array(‘interval’ => 1200, ‘display’ => __(‘Every 20 minutes’)),
‘_30m’ => array(‘interval’ => 1800, ‘display’ => __(‘Every half hour’)),
‘_60m’ => array(‘interval’ => HOUR_IN_SECONDS, ‘display’ => __(‘Every hour’)),
‘_120m’ => array(‘interval’ => HOUR_IN_SECONDS * 2, ‘display’ => __(‘Every 2 hours’)),
‘_360m’ => array(‘interval’ => HOUR_IN_SECONDS * 6, ‘display’ => __(‘Every 6 hours’)),
);

seems like in 60 minutes should be:
‘_60m’ => array(‘interval’ => HOUR_IN_SECONDS * 1, ‘display’ => __(‘Every hour’)),

I’m correct?

• This reply was modified 8 years, 3 months ago by Linmp. Reason: added "vigilantor.php" page indication

HOUR_IN_SECONDS is the same as HOUR_IN_SECONDS * 1 so that should be okay. The timed updates are handled via wp-cron, so if there are no hits to your site for 2 hours, it will only update on the next visit at least 60 minutes after the previous update.

Since you mention this, it might be nice to support updates via real cron (hitting a special URL that will trigger the update).

Also, I started working on the generic IP blocking / hostname blocking last night. I need to do further testing with large block lists and see if IP to hostname resolution is a problem. In some cases this can add an extra half second to the page load depending on the IP and speed/caching of the DNS server in use. Also, a lot of the IP’s used by these VPN providers don’t reverse to common hostnames that are easy to block and some I found don’t have reverse DNS at all (e.g. PrivateInternetAccess – a few I looked at reverse to host.my-tss.com and some return NXDOMAIN).

Here the “Every hour” never works, not in this version, and also in the previous version it also didn’t work, but I tested the 10 and 30 minutes and it works properly… isn’t anything wrong on the code?

At least a real cron in the hosting company I have the web site is problematic because it can only be done once every hour and I need to program individually to every hour, the control panel is a custom made by company it self.

Thanks for the work. Yes, many VPN company’s don’t offer reverse hostname, but some do and can be added more easily in add-hoc style. Adding the IPs mannually is a pain, but can be made in the .htaccess or in your plugin if you add support for that of course.

Thanks for your good work =)