1 vote

Integration functions for advanced settings protection

1) Change Database Table Prefix
2) Hide Backend login with custom name
3) Change or update Salts key on wp config settings
4) Hide all reference string version or generator of plugin inside code

Passionlab shared this idea

1 thought on “Integration functions for advanced settings protection”

  1. Great suggestions – a few notes:
    1) It is already possible to change the database table prefix via one of the autofixers.

    3) There is already a check for the age of the salt keys, and there is an autofixer that help with taking a backup and updating the keys.
    4) I am not sure what the idea is here? Removing version number and generator of WordPress in the source code on frontend? If that is the reference, there is already an “autofix” for this for hiding WP version info.

    2) We are working on adding a way to hide backend/login – Check out this request

Leave a Reply

Your email address will not be published. Required fields are marked *

1 thought on “Integration functions for advanced settings protection”

  1. Great suggestions – a few notes:
    1) It is already possible to change the database table prefix via one of the autofixers.

    3) There is already a check for the age of the salt keys, and there is an autofixer that help with taking a backup and updating the keys.
    4) I am not sure what the idea is here? Removing version number and generator of WordPress in the source code on frontend? If that is the reference, there is already an “autofix” for this for hiding WP version info.

    2) We are working on adding a way to hide backend/login – Check out this request

Comments are closed.

20% OFF

Subscribe to our newsletter

* We do not spam or share your email

Discount on any Security Ninja plan

and get

Hi and welcome back :-)