Timeline for Prevent brute force attacks on web publishing logins
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 21, 2015 at 17:58 | vote | accept | ispiro | ||
| Jul 20, 2015 at 17:28 | vote | accept | ispiro | ||
| Jul 20, 2015 at 17:28 | |||||
| Jul 16, 2015 at 18:44 | comment | added | Jeroen | @ispiro: That's correct! | |
| Jul 16, 2015 at 18:44 | comment | added | ispiro | @Jeroen-ITNerdbox Thanks. (I assume you meant to post that as a comment to my question.) | |
| Jul 16, 2015 at 18:42 | comment | added | Jeroen | Shared hosting is by default a risk in my opinion, not to mention the control panels. If you want full control and be able to secure your server as much as possible, I suggest to look into either a dedicated server or a VPS. This way you can control all your concerns regarding brute force attacks. | |
| Jul 16, 2015 at 18:40 | comment | added | Rory McCune | that was why I opened with the bit about it depending on the level of access. If you have no control over the server or firewall configuration and the service provider doesn't provide any features that could be used for this, it's hard to see what you could do (i.e. you have no access, you can't change the service) apart from have good passwords. | |
| Jul 16, 2015 at 18:33 | comment | added | ispiro | Thanks. But perhaps I wasn't clear enough in my question. I'm asking about using a shared web-hosting service and therefore have limited control over their server's setup. | |
| Jul 16, 2015 at 18:28 | history | answered | Rory McCune | CC BY-SA 3.0 |