phpgroupware-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: nobody
Subject: [Phpgroupware-tracker] [bug #5311] Too many bad logins does not block account
Date: Thu, 25 Sep 2003 16:49:15 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030618 Debian/1.3.1-3

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

Changes by: Dave Hall <address@hidden>
Date: Fri 09/26/03 at 06:49 (Australia/Melbourne)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | None                      | skwashd


------------------ Additional Follow-up Comments ----------------------------
Hi pooh_

1 - because it tests if the value is set, 0 = unset

2 and 3 - will look for you



Admin option, sorry that will have to wait for HEAD - new feature.



Hi lcdumais,



That is why it is an config option, for people using phpGW to store important 
information, 3 is the desired value.  Feel free to change the value on your 
install.



=================== BUG #5311: FULL BUG SNAPSHOT ===================


Submitted by: pooh_                   Project: phpGroupWare                 
Submitted on: Mon 09/15/03 at 22:47
Category:  API - Admin                Bug Group:  0.9.16RC1                 
Severity:  5 - Major                  Priority:  Normal                     
Resolution:  None                     Assigned to:  skwashd                 
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)



Follow-up Comments
*******************

-------------------------------------------------------
Date: Fri 09/26/03 at 06:49         By: skwashd
Hi pooh_

1 - because it tests if the value is set, 0 = unset

2 and 3 - will look for you



Admin option, sorry that will have to wait for HEAD - new feature.



Hi lcdumais,



That is why it is an config option, for people using phpGW to store important 
information, 3 is the desired value.  Feel free to change the value on your 
install.

-------------------------------------------------------
Date: Fri 09/26/03 at 05:12         By: lcdumais
I think the default Max # of bad logins before IP gets blocked and 

 max # of bad logins before Account gets blocked should be at least 10 and not 
3.










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/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]