Re:300,000 WordPress hacking attempts and 5 observations
by iamjason89 on Friday November 28, 2014 @02:34AM
(#8670019)
Was just about to recommend this. Supporting Wordpress everyday, I find this is the best way to combat the problem. Another option would be to add an additional password for the directory. For you apache guys,
[ Parent
| on HN ]
Re:300,000 WordPress hacking attempts and 5 observations
by porker on Friday November 28, 2014 @03:27AM
(#8670117)
Good tip. The other two changes I recommend are:
1. Disable PHP execution in the uploads directory (hmm, wonder if it'd work if I disabled it in the entire wp-content folder?).
2. Run PHP as a different user to the file owner.
Both of these are to minimise damage when an extension is exploited by a hacker (if it hasn't happened to you yet, it will do) and to reduce the damage done to the server/site.
Re:300,000 WordPress hacking attempts and 5 observations
by deanclatworthy on Friday November 28, 2014 @02:54AM
(#8670041)
This is the approach I used to take also, before moving my site to Jekyll. You could also use fail2ban to prevent hammering of that URL.