I think we can close this issue. Even if any core developpers really considered as a security issue, the discussion leaded to some improvements like issue5381, issue5377 and issue5435 which all improve the availability of trytond under some DoS attacks. We will keep the login attempt computation as-is and the reasons can be found at msg24702. Of course for complex database setup, the user will have to take care of how he plans to manage the LoginAttempt table (as many others). But as many other optimisations like indexes the policy in Tryton is to leave as much as possible freedom of choice to the user.
|2016-03-29 13:12:47||ced||set||messageid: <email@example.com>|
|2016-03-29 13:12:47||ced||set||recipients: + bch, yangoon, nicoe, sharkcz, meanmicio, smarro, pokoli, ajacoutot|
|2016-03-29 13:12:46||ced||link||issue5375 messages|
Showing 10 items. Show all history (warning: this could be VERY long)