[asterisk-bugs] [Asterisk 0017509]: Bruteforce hack

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17509 
====================================================================== 
Reported By:                mn3250
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17509
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.32 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 not fixable
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-06-15 21:07 CDT
Last Modified:              2010-06-16 08:37 CDT
====================================================================== 
Summary:                    Bruteforce hack
Description: 
Lately there are some registration attempts from different IPs to register
to my servers. Both on SIP and IAX.
Is it possible to think of disabling an IP source not to be able to
register for a few minutes after some unsuccessful registration attempts?
Since wrong user/pass cannot be handled in firewall, can there be a new
feature in Asterisk to do it?
====================================================================== 

---------------------------------------------------------------------- 
 (0123474) pabelanger (manager) - 2010-06-16 08:37
 https://issues.asterisk.org/view.php?id=17509#c123474 
---------------------------------------------------------------------- 
This is a support request (see below), not a bug.
---
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it would
make more sense to raise your question in the support tracker,
http://www.asterisk.org/support 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-16 08:37 pabelanger     Note Added: 0123474                          
2010-06-16 08:37 pabelanger     Status                   new => closed       
2010-06-16 08:37 pabelanger     Resolution               open => not fixable 
======================================================================