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 badges1 Answer
Reset to default 0I 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
版权声明:本文标题:installation - Renaming install.php for security? 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1736300364a1930789.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论