admin管理员组

文章数量:1122832

A few years ago I was reading some blogs on how to harden your WP site, and one of the things suggested was to rename your install.php file so that someone couldn't re-install a new WP site over top of the current one.

It appears that when you update WP now the install.php file is put back. I've been trying to google whether this step is still necessary, but haven't found anything useful.

Any hard evidence this is still a good thing to implement? Or can I safely take this off my checklist of things to do.

Thanks.

A few years ago I was reading some blogs on how to harden your WP site, and one of the things suggested was to rename your install.php file so that someone couldn't re-install a new WP site over top of the current one.

It appears that when you update WP now the install.php file is put back. I've been trying to google whether this step is still necessary, but haven't found anything useful.

Any hard evidence this is still a good thing to implement? Or can I safely take this off my checklist of things to do.

Thanks.

Share Improve this question asked Nov 29, 2016 at 20:32 KVDDKVDD 1522 silver badges11 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 0

I agree that this is a good step to take in hardening the site. I would not recommend interfering directly with the files from WordPress for the exact reason your describe: updates will overwrite it.

Two options I would recommend:

  • Use a hardening plug-in to help you do this
  • Add a rule to .htaccess to prevent people from accessing the file

In the wp-admin folder add this to .htaccess:

<Files install.php> Order Allow,Deny Deny from all </Files>

本文标签: installationRenaming installphp for security