[Phpgroupware-tracker] [bug #5311] Too many bad logins does not block account

[nobody]

=================== BUG #5311: FULL BUG SNAPSHOT ===================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5311&group_id=509

Submitted by: pooh_                   Project: phpGroupWare                 
Submitted on: Mon 09/15/2003 at 12:47
Category:  API - Admin                Bug Group:  0.9.16RC1                 
Severity:  5 - Major                  Priority:  Normal                     
Resolution:  None                     Assigned to:  None                    
Status:  Open                         Component Version:  None              
Platform Version:  Linux - RedHat     Reproducibility:  Every Time          

Summary:  Too many bad logins does not block account

Original Submission:  Admin -> Site configuration;



You can set Max # of bad logins before IP gets blocked and

you can set max # of bad logins before Account gets blocked.



- If both set to zero the default back to 3. Why?

- Which setting has priority? cause the lowest# of attemps always wins right?

- If block account is set to lowest # of attemps, this results in ip blocking 
and the account is not deactivated!



An admin panel to directly unblock the IP and account would be preferable, 
cause now you have to delete the phpgw_access_log manually.

That's no fun when you're not at the console (and don't have  other means of 
accessing the db directly)





No Followups Have Been Posted


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5311&group_id=509

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/