Jelena

Hi,

Thanks for reaching out.

Yes, there is. You can find this within Login Protection module => Brute Force => Login Cooldown Interval. This option limits login attempts to every X seconds.

Please see here:
https://icontrolwp.freshdesk.com/support/solutions/articles/3000000882-what-is-login-cooldown-and-how-does-it-work-

Hope that helps.

Regards,
Jelena

Hi Daniel,

There’s no problem at all. 🙂

The only thing I can confirm is that those files are not part of the current WordPress 4.9 core installation files.

Before you make the final decision (removing / or excluding from the future scans) I recommend you to talk to your web host first. If they confirm that the detected files are not important for your site(s), you can remove them. If they tell you that some of the files are important, you can add them into file exclusion list.

Regards,
Jelena

Hi,

With the Shield Security plugin, we haven’t provided “I’m a human” string customization functionality.

But, you’ll be able to manually edit it directly with Shield Pro that due for release in a week or so and will cost only $1/month.

You can signup to hear about it here: https://onedollarplugin.com/

Many thanks for your time, and if you have any additional questions or concerns regarding this matter, please feel free to contact us anytime. We’ll be delighted to help. 🙂

Regards,
Jelena

• This reply was modified 8 years, 5 months ago by Jelena.

Hi,

As Paul said, you need to give us more details on this. It’s still unclear what issue you have there.

I assume that you’ve excluded the “webp” file from the scan but the scanner keeps detecting it as “unrecognised” and you don’t know what to do? Is the problem related to the file exclusion process or? Please clarify so we could help you out.

I’m also suggesting you to read this help article:
https://icontrolwp.freshdesk.com/support/solutions/articles/3000069910-hack-protection-module-unrecognised-file-scanner-summary

Regards,
Jelena

• This reply was modified 8 years, 6 months ago by Jelena.

It only blocks the URL for non-logged-in visitors. If you are logged in, the URL will work as normal.

Please read this blog article:
https://www.icontrolwp.com/blog/block-username-fishing-using-author-ids-scans-wordpress-security-basics-series-pt-6/

Regards,
Jelena

Hi Marty,

Thanks for reaching out.

If you have comments disabled on your site but you keep the Comments SPAM feature enabled, the feature will not have any effect whatsoever. The spam filtering only gets activated when a comment is posted, or the comments form is loaded. You will not get spam comments if comments are disabled.

There’s no downside to enabling the option anyway. If you ever enabled comments just for 1 post only, you’ll be protected.

I hope this answers your question.

Regards,
Jelena

Hi,

Many thanks for contacting us and for the detailed problem explanation.

Shield plugin is founded on using standard WordPress API/hooks/filters. If you are using a custom login form that doesn’t use these standards, then it’s possible that the form doesn’t fire the necessary WordPress hook that allows us to insert the checkbox.

In this case, you have 2 options:

1 – Turn off the GASP option within the Login Protection module since your custom login form doesn’t support it; or
2 – Don’t use a custom login plugin/theme or use one that supports standard WordPress login hooks.

The other possibility is that the browser may not be setup to support Javascript.

The options are:

1 – Enable Javascript on the browser; or
2 – Disable the GASP option.

Hope this helps.

Regards,
Jelena

Hi,

Many thanks for contacting us and pointing out the problem.

Login Protection and Comments SPAM modules should work independently.

We’ve been able to replicate the settings and we can confirm that Google reCAPTCHA option doesn’t work properly. We’ll look at it in more depth and fix the problem.

Thanks one more time and if you have any other questions, please feel free to contact us anytime.

Regards,
Jelena

• This reply was modified 8 years, 7 months ago by Jelena.