Mark Maunder

Thanks for the feedback guys. Just want you to know that I’ve taken note of this and we’ll run Falcon through pagespeed a few times and see if we can improve things.

Regards,

Mark.

OK let me know if it helps.

Regards,

Mark.

I’d check your mail rules – perhaps you’re forwarding? I can’t provide hands-on support for free customers (let me know if you’re paid).

Regards,

Mark.

@allm:

Sorry about the delay on this. It’s been a crazy week. (for all of us in the infosec space!!)

I really need to know what changes are made to the .htaccess file. Are there only additions? And what are they? Or does it try to make changes as well? And what changes? Under what circumstances are these changes made?

No we don’t edit your existing entries. The first change is that we prepend our code to your existing code and our code is enclosed in a block starting and ending with comments containing ‘WFCACHECODE’ without quotes.

The second change is that we prepend a block of code that handles IP blocks, range blocks and user agent blocks. This block is enclosed in comments starting and ending with ‘WFIPBLOCKS’.

And in another thread I said that out of security reasons I’ve made my .htaccess unwritable for all. Apparently I need to lessen that security to give the new WordFence access. But that will give that access to other plugins as well. That is why I need to know the answer to this (as I like to have my .htaccess fully blocked):
Can I still block IP’s the “old” way? Without Wordfence changing my htaccess?

Interesting point. So to modify your htaccess to be compatible with falcon we obviously need write access. But once you’ve enabled falcon I’m parsing your comment to understand that you’d really like to make it read-only again and have the IP blocking updates not write to your .htaccess but do it the traditional way – or at least you’d like the option to do that, correct?

PS: Marking this unresolved until you’re happy with my responses.

Hi,

I think you’re already in our ticketing system and Kerry is busy replying to you as I write this but:

In the newest version we changed Wordfence so that if your IP address is whitelisted, you won’t be taken through the cellphone sign-in process. So it’s likely that you’ve whitelisted your IP address.

Regards,

Mark.

@lizardwebs If you do find it give us an update just for info. Might be interesting to know what the cause was.

Hi,

I’m not sure how that’s possible if you only have one email address configured to get the alerts. We only email that email address.

Regards,

Mark.