You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2013/04/12 09:15:15 UTC

[jira] [Created] (DIRSERVER-1825) The delay used in PasswordPolicy should not be implemented as a Thread.sleep(delay)

Emmanuel Lecharny created DIRSERVER-1825:
--------------------------------------------

             Summary: The delay used in PasswordPolicy should not be implemented as a Thread.sleep(delay)
                 Key: DIRSERVER-1825
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1825
             Project: Directory ApacheDS
          Issue Type: Bug
    Affects Versions: 2.0.0-M11
            Reporter: Emmanuel Lecharny
             Fix For: 2.0.0-RC1


When a delay is introduced after a bind failure, we currently do a Thread.sleep() in the server on the session that was trying to bind. This is absolutely wrong, as it may block the whole server after a few attempt from  few users (as we use only a limited number of threads).

We should instead forbid any attempt during the delay (that means even a successful bind should fail), as the idea behind this delay is to forbid an attack where someone submit as many bind as possible, until one is successful.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira