Re: [Zope] Re: Handling login failures

2006-01-13 Thread David Hassalevris

Håkan Johansson wrote:



On Jan 13, 2006, at 00:32, Dennis Allison wrote:





A more usual solution to this issue is to insert a delay after the third
and subsequent failures.  You, of course, need a policy for removing the
delay (successful login or N minutes following the last attempt).




Yes, I have been thinking the same thing. It would be much less work 
for the admin of the system.

Thanks for the tip though :)

_


Of course if you enforced longer passwords you can  achieve a similar 
result.  You dont slow time down between authentication events (like 
Dennis suggests) but you add the amount of time needed to guess a 
password.  So (slow Auth reponsies + tries) can approximate (fast Auth 
responses + alot more tries)



David



___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope] Re: Handling login failures

2006-01-12 Thread Håkan Johansson


On Jan 13, 2006, at 00:32, Dennis Allison wrote:





A more usual solution to this issue is to insert a delay after the 
third
and subsequent failures.  You, of course, need a policy for removing 
the

delay (successful login or N minutes following the last attempt).




Yes, I have been thinking the same thing. It would be much less work 
for the admin of the system.

Thanks for the tip though :)

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )


[Zope] Re: Handling login failures

2006-01-12 Thread Håkan Johansson


On Jan 13, 2006, at 00:24, Florent Guillaume wrote:




Håkan Johansson wrote:
I want to be able to block a user from logging in if he fails to give 
the right login/password three times in a row.


You're aware that this allows anyone to trivially DoS your users, 
right?
If you take the precaution of matching with the IP, it still will harm 
people logging in through corporate or ISP proxies. Which, admittedly, 
may not be a problem in an intranet setting.


Florent


This is not really a problem for us since we have a firewall that must 
be logged into first. Only customers to the system can actually access 
it.
If I had a say in it, I would not implement a system like this at all, 
but our customer wants it.


Thanks for the warning though. I hadn't thought about the DoS aspect.

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope] Re: Handling login failures

2006-01-12 Thread Dennis Allison

A more usual solution to this issue is to insert a delay after the third
and subsequent failures.  You, of course, need a policy for removing the 
delay (successful login or N minutes following the last attempt).


On Fri, 13 Jan 2006, Florent Guillaume wrote:

> Håkan Johansson wrote:
> > I want to be able to block a user from logging in if he fails to give 
> > the right login/password three times in a row. 
> 
> You're aware that this allows anyone to trivially DoS your users, right?
> If you take the precaution of matching with the IP, it still will harm 
> people logging in through corporate or ISP proxies. Which, admittedly, 
> may not be a problem in an intranet setting.
> 
> Florent
> 
> > The problem is that I  don't know how to do this.
> > 
> > First, I need to know if an attempt failed. This, I have no idea how to do.
> > 
> > Second, I need to block the user without deleting him. One problem here 
> > is that the user can write different login names for the different login 
> > attempts. We have been thinking about blocking the offender's IP for 30 
> > minutes or so and leave it at that. It seems to me that 
> > SiteAccess.AccessRule could be used for that, but I haven't looked much 
> > into it yet. The documentation is extremely light.
> > 
> > 
> > I have a very clean Zope 2.8.4 installation on a SuSE linux machine.
> > Logins are handled in the standard Zope way, nothing special added.
> > The Zope is running as a stand alone server, i.e. no Apache at all.
> > 
> > 
> > Another thing: How do I get Zope to log failed authentication attempts? 
> > Neither event.log or Z2.log shows anything. As Z2.log is the access log, 
> > I would have guessed that such things should be logged there. If not, 
> > where and how?
> 
> 
> 
> 

-- 

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )


[Zope] Re: Handling login failures

2006-01-12 Thread Florent Guillaume

Håkan Johansson wrote:
I want to be able to block a user from logging in if he fails to give 
the right login/password three times in a row. 


You're aware that this allows anyone to trivially DoS your users, right?
If you take the precaution of matching with the IP, it still will harm 
people logging in through corporate or ISP proxies. Which, admittedly, 
may not be a problem in an intranet setting.


Florent


The problem is that I  don't know how to do this.

First, I need to know if an attempt failed. This, I have no idea how to do.

Second, I need to block the user without deleting him. One problem here 
is that the user can write different login names for the different login 
attempts. We have been thinking about blocking the offender's IP for 30 
minutes or so and leave it at that. It seems to me that 
SiteAccess.AccessRule could be used for that, but I haven't looked much 
into it yet. The documentation is extremely light.



I have a very clean Zope 2.8.4 installation on a SuSE linux machine.
Logins are handled in the standard Zope way, nothing special added.
The Zope is running as a stand alone server, i.e. no Apache at all.


Another thing: How do I get Zope to log failed authentication attempts? 
Neither event.log or Z2.log shows anything. As Z2.log is the access log, 
I would have guessed that such things should be logged there. If not, 
where and how?




--
Florent Guillaume, Nuxeo (Paris, France)   Director of R&D
+33 1 40 33 71 59   http://nuxeo.com   [EMAIL PROTECTED]
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )