[
https://issues.apache.org/jira/browse/DIRSERVER-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1825:
-----------------------------------------
Component/s: ppolicy
> 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
> Components: ppolicy
> Affects Versions: 2.0.0-M11
> Reporter: Emmanuel Lecharny
> Priority: Major
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
