Timeline for Exploiting WordPress Core Functionality for Development
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 19, 2017 at 16:56 | comment | added | Tyler Johnson | @VishalKumarSahu Run your site through Cloudflare and use their firewall. I've found that really helps cut down on bots sniffing around. And I agree with David, security through obscurity, especially with WP, isn't really worth it. | |
| Jan 19, 2017 at 16:15 | comment | added | Vishal Kumar Sahu | That is like fighting the attack. I am also trying to find ways to misguide bots. :/ | |
| Jan 19, 2017 at 15:58 | comment | added | David | I think you should consider WordPress as secure or inspect the code to find possible vulnerabilities and report them to get them fixed (which typically doesn't take very long). Anything that goes into the direction of «security by obscurity» (hiding WP) is not worth the effort and I'm in doubt that it is even possible. You can improve security be enforce strong passwords and using a provider that is able to block brute force attacks. But the most important thing is to keep every software up to date. | |
| Jan 19, 2017 at 15:32 | history | asked | Vishal Kumar Sahu | CC BY-SA 3.0 |