Comodo default blocked?

@Sybre Waaijer

The iTSec plugin HackRepair.com blacklist setting uses template files for inserting the necessary .htaccess lines.

These template files (3) are located in the better-wp-security/core/modules/ban-users/lists folder.

You can change the entries in these template files anyway you want.
So if you are using Nginx webserver edit the hackrepair-nginx.inc file.

After making your changes don’t forget to make a backup copy of the .inc file and save it in a secure location OUTSIDE the better-wp-security folder.
When updating the plugin all changes will be lost …

If you decide to change a template file don’t forget to disable the Banned Users HackRepair.com blacklist setting, save all changes and then reenable the HackRepair.com blacklist setting and save all changes, in order to propagate the template file changes to your nginx.conf file …
Then restart Nginx.

If the above info answers your question please mark this topic as ‘resolved’.

dwinden

Hi dwinden,

It actually doesn’t, as I’m using Apache ??
Nevertheless, I’ve already resolved this prior to posting this topic.

It also was merely a suggestion, so I should mark this as a “not a support question” ??

Happy holidays!

@Sybre Waaijer

Ok, sorry to waste your time.
Don’t know why I thought you were on Nginx …
Anyway webserver used doesn’t really matter.

Would it be possible to share your solution to the community ?

Do note the Hackrepair.com list is supposed to be a starting point …
There simply isn’t a one size fits all solution …
That said the list is originally from Hackrepair.com … so you might have a better chance when you request the Hackrepair.com list author to change his list and then the change might trickle down this plugin in a future update …

Happy holidays!

dwinden

Hi Dwinden,

I simply blocked access from PHP on the .htaccess file for security reasons a long time ago.

From there you can simply remove the lines needed to be removed from .htaccess ?? In this case it was the line with comodo.

I hope this helps!

But why is comodo blocked? I’ve just had a nightmare trying to get a SSL verified. I kept blaming the SSL verification software, saying it was broken. The SSL issuer told me to remove any htaccess lines to get it to work, i.e. disable the site security. I did that and got it to work, and eventually we established comodo are specifically blocked. In the meantime my site security was disabled.

I would like to know why comodo is blocked and we have to specifically allow them. Now I have commented out the comodo block in htaccess, have I lowered security, because I assume they blocked for some good reason? Although not sure why as they are a SSL issuer.

Thanks

• This reply was modified 8 years ago by amityweb.