-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Use of StopSpammer #82
Comments
#147 is related. So, was there any progress with this task? |
This issue was automatically marked as stale |
@skenow do you still have a plan anything to do with this? |
To be honest, I haven't come up with a plan of attack. I'll have a look at it. |
@skenow I think finding a similar library that is regularly updated would be an excellent first step and then replacing internal StopSpammer code with this library. One of our main problems is that we do not have enough time to keep up with security stuff.. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or assign sombody or this will be closed in 5 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or assign sombody or this will be closed in 5 days. |
Stopspammer is used in the core during the creation of users. In some cases, for example during a local installation, Stopspammer gives false positives, effectively blocking users where it is not needed.
I think this is a good candidate to use the events in the core : create an event 'beforeusercreate' and link stopspammer to that.
This is an import from Assembla Ticket 431
The text was updated successfully, but these errors were encountered: