# Security measures proposal - User login brute force prevention, and more

**URL:** <https://meta.discourse.org/t/security-measures-proposal-user-login-brute-force-prevention-and-more/19023>\
**Category:** Feature\
**Created:** [Août 19, 2014, 12:42 UTC](https://meta.discourse.org/t/security-measures-proposal-user-login-brute-force-prevention-and-more/19023 "2014-08-19T00:42:23Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Lid](https://avatars.discourse-cdn.com/v4/letter/l/2bfe46/32.png) [@Lid](https://meta.discourse.org/u/Lid)\
**Post date:** [Septembre 8, 2014, 9:16 UTC](https://meta.discourse.org/t/security-measures-proposal-user-login-brute-force-prevention-and-more/19023/11 "2014-09-08T21:16:17Z")

</div>

Yes. To prevent denial of service. The system will generate a “back door” a tokenized login link that will be sent by email to the account holder.  
And the user only have to log in if they logout, so it is unlikely to cause major inconvenience.

IP blocking can also be used to cause denial of service for users sharing IP for example users on the same NAT network in an organization or In bigger scale a mobile network provider where many users can share same public ip. VPN provider. Etc.

At a certain level IP blocking is also an effective and common solution.

my proposed mechanism can provide a really high account security. making it extremely unlikely that even an attacker  
with resources (botnet, captcha solvers for hire) to mange to successfully brute force a password.

---

_[View the full topic](https://meta.discourse.org/t/security-measures-proposal-user-login-brute-force-prevention-and-more/19023)._
