Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Korbinian Bachl
Bad idea - some ISPs and proxys would be locked out... cachapta would be
solution of choice here.

Regards

Korbinian

 

 -Ursprüngliche Nachricht-
 Von: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] Im Auftrag 
 von Johannes Fahrenkrug
 Gesendet: Montag, 6. November 2006 14:01
 An: wicket-user@lists.sourceforge.net
 Betreff: [Wicket-user] Prevent Brute Force and the like
 
 Hi!
 
 I'd like to prevent brute force attacks on the login page of 
 my wicket application. What would be the best approach? This 
 is what I'm thinking about doing: Record when the last 
 request for the loginpage from a certain IP came in and only 
 handle the request when at least a second or two have passed.
 This would have to be done application wide because when an 
 attacker uses a tool like cURL a new session is created with 
 each request.
 
 So what would you guys suggest?
 
 - Johannes
 
 --
 ---
 Using Tomcat but need to do more? Need to support web 
 services, security?
 Get stuff done quickly with pre-integrated technology to make 
 your job easier Download IBM WebSphere Application Server 
 v.1.0.1 based on Apache Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057;
dat=121642
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user
 


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Johannes Fahrenkrug
Korbinian,

I'm sorry if I wasn't clear: I didn't plan on blocking anymore 
permanently, just add one second delays if some IP was flooding me to 
render brute force attacks useless and impractical.

Could you please explain cachapta / provide a link to an article?

Regards,

Johannes

Korbinian Bachl wrote:

Bad idea - some ISPs and proxys would be locked out... cachapta would be
solution of choice here.

Regards

Korbinian

 

  

-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] Im Auftrag 
von Johannes Fahrenkrug
Gesendet: Montag, 6. November 2006 14:01
An: wicket-user@lists.sourceforge.net
Betreff: [Wicket-user] Prevent Brute Force and the like

Hi!

I'd like to prevent brute force attacks on the login page of 
my wicket application. What would be the best approach? This 
is what I'm thinking about doing: Record when the last 
request for the loginpage from a certain IP came in and only 
handle the request when at least a second or two have passed.
This would have to be done application wide because when an 
attacker uses a tool like cURL a new session is created with 
each request.

So what would you guys suggest?

- Johannes

--
---
Using Tomcat but need to do more? Need to support web 
services, security?
Get stuff done quickly with pre-integrated technology to make 
your job easier Download IBM WebSphere Application Server 
v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057;


dat=121642
  

___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user





-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

  



-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Erik van Oosten
Another option is to lower the throughput (number of login requests 
handled per minute) for that IP address.
In this case you should probably use Wicket 2 to optimize session usage.

 Erik.


Korbinian Bachl schreef:
 Bad idea - some ISPs and proxys would be locked out... cachapta would be
 solution of choice here.

 Regards

 Korbinian


   
 -Ursprüngliche Nachricht-
 Von: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] Im Auftrag 
 von Johannes Fahrenkrug
 Gesendet: Montag, 6. November 2006 14:01
 An: wicket-user@lists.sourceforge.net
 Betreff: [Wicket-user] Prevent Brute Force and the like

 Hi!

 I'd like to prevent brute force attacks on the login page of 
 my wicket application. What would be the best approach? This 
 is what I'm thinking about doing: Record when the last 
 request for the loginpage from a certain IP came in and only 
 handle the request when at least a second or two have passed.
 This would have to be done application wide because when an 
 attacker uses a tool like cURL a new session is created with 
 each request.

 So what would you guys suggest?

 - Johannes

 
-- 
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Rüdiger Schulz
Hello Johannes,

that's a good topic you've got here...

I agree to Korbinian that locking out IPs is a bad idea. One could
extend that to the combination of username/IP, but that could be worked
around with a more sofisticated script.

What do you think about logging false logins on a per-user basis, and
delay the response after the first false attempt by a couple of seconds
until another valid login for that user happened? I think the Linux
shell login works like that.

Or, one could lock an account completely after say three false attempts,
and send an email to the user with a link to unlock it again.


.rue


Johannes Fahrenkrug schrieb:
 Hi!
 
 I'd like to prevent brute force attacks on the login page of my wicket 
 application. What would be the best approach? This is what I'm thinking 
 about doing: Record when the last request for the loginpage from a 
 certain IP came in and only handle the request when at least a second or 
 two have passed.
 This would have to be done application wide because when an attacker 
 uses a tool like cURL a new session is created with each request.
 
 So what would you guys suggest?
 
 - Johannes
 
 -
 Using Tomcat but need to do more? Need to support web services, security?
 Get stuff done quickly with pre-integrated technology to make your job easier
 Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user
 
 


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Johan Compagner
isn't this more the responsibility for the hardware/software that runs wicket?So Apache or WebLogic itself? That does the throttling?I wouldn't try to solve this in a webapplication. johan
On 11/6/06, Johannes Fahrenkrug [EMAIL PROTECTED] wrote:
Hi!I'd like to prevent brute force attacks on the login page of my wicketapplication. What would be the best approach? This is what I'm thinkingabout doing: Record when the last request for the loginpage from a
certain IP came in and only handle the request when at least a second ortwo have passed.This would have to be done application wide because when an attackeruses a tool like cURL a new session is created with each request.
So what would you guys suggest?- Johannes-Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimohttp://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___Wicket-user mailing listWicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Pierre-Yves Saumont
  Could you please explain cachapta / provide a link to an article?

I suppose he means captcha. You should find this one on google ;-)

Pierre-Yves

Johannes Fahrenkrug a écrit :
 Korbinian,
 
 I'm sorry if I wasn't clear: I didn't plan on blocking anymore 
 permanently, just add one second delays if some IP was flooding me to 
 render brute force attacks useless and impractical.
 
 Could you please explain cachapta / provide a link to an article?
 
 Regards,
 
 Johannes
 
 Korbinian Bachl wrote:
 
 Bad idea - some ISPs and proxys would be locked out... cachapta would be
 solution of choice here.

 Regards

 Korbinian



  

 -Ursprüngliche Nachricht-
 Von: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] Im Auftrag 
 von Johannes Fahrenkrug
 Gesendet: Montag, 6. November 2006 14:01
 An: wicket-user@lists.sourceforge.net
 Betreff: [Wicket-user] Prevent Brute Force and the like

 Hi!

 I'd like to prevent brute force attacks on the login page of 
 my wicket application. What would be the best approach? This 
 is what I'm thinking about doing: Record when the last 
 request for the loginpage from a certain IP came in and only 
 handle the request when at least a second or two have passed.
 This would have to be done application wide because when an 
 attacker uses a tool like cURL a new session is created with 
 each request.

 So what would you guys suggest?

 - Johannes

 --
 ---
 Using Tomcat but need to do more? Need to support web 
 services, security?
 Get stuff done quickly with pre-integrated technology to make 
 your job easier Download IBM WebSphere Application Server 
 v.1.0.1 based on Apache Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057;


 dat=121642
  

 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user




 -
 Using Tomcat but need to do more? Need to support web services, security?
 Get stuff done quickly with pre-integrated technology to make your job easier
 Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user

  

 
 
 -
 Using Tomcat but need to do more? Need to support web services, security?
 Get stuff done quickly with pre-integrated technology to make your job easier
 Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user
 
 
 


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Johannes Fahrenkrug
I guess that depends... I think you have to let the webapplication 
handle it if you want to prevent brute force dictionary attacks on the 
login page only. Especially if you want to do this on a per username 
basis or even use captchas (thanks Pierre-Yves).
I don't think the hardware or the server software could handle this or 
am I wrong?

- Johannes

Johan Compagner wrote:

 isn't this more the responsibility for the hardware/software that runs 
 wicket?
 So Apache or WebLogic itself? That does the throttling?
 I wouldn't try to solve this in a webapplication.

 johan


 On 11/6/06, *Johannes Fahrenkrug* [EMAIL PROTECTED] 
 mailto:[EMAIL PROTECTED] wrote:

 Hi!

 I'd like to prevent brute force attacks on the login page of my wicket
 application. What would be the best approach? This is what I'm
 thinking
 about doing: Record when the last request for the loginpage from a
 certain IP came in and only handle the request when at least a
 second or
 two have passed.
 This would have to be done application wide because when an attacker
 uses a tool like cURL a new session is created with each request.

 So what would you guys suggest?

 - Johannes

 -
 Using Tomcat but need to do more? Need to support web services,
 security?
 Get stuff done quickly with pre-integrated technology to make your
 job easier
 Download IBM WebSphere Application Server v.1.0.1 based on Apache
 Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 mailto:Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user




-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642



___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
  



-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Alexandre Bairos
I usually use captcha and a cache implementation(e.g. oscache, jboss cache) to save erroneous login attempts until user hits a configured maximum number of attempts. If maximum is achieved the user is blocked for a certain period of time.
On 11/6/06, Pierre-Yves Saumont [EMAIL PROTECTED] wrote:
  Could you please explain cachapta / provide a link to an article?I suppose he means captcha. You should find this one on google ;-)Pierre-YvesJohannes Fahrenkrug a écrit :
 Korbinian, I'm sorry if I wasn't clear: I didn't plan on blocking anymore permanently, just add one second delays if some IP was flooding me to render brute force attacks useless and impractical.
 Could you please explain cachapta / provide a link to an article? Regards, Johannes Korbinian Bachl wrote: Bad idea - some ISPs and proxys would be locked out... cachapta would be
 solution of choice here. Regards Korbinian -Ursprüngliche Nachricht- Von: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
] Im Auftrag von Johannes Fahrenkrug Gesendet: Montag, 6. November 2006 14:01 An: wicket-user@lists.sourceforge.net
 Betreff: [Wicket-user] Prevent Brute Force and the like Hi! I'd like to prevent brute force attacks on the login page of my wicket application. What would be the best approach? This
 is what I'm thinking about doing: Record when the last request for the loginpage from a certain IP came in and only handle the request when at least a second or two have passed.
 This would have to be done application wide because when an attacker uses a tool like cURL a new session is created with each request. So what would you guys suggest?
 - Johannes -- --- Using Tomcat but need to do more? Need to support web
 services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057 dat=121642
 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user -
 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server 
v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/wicket-user - Using Tomcat but need to do more? Need to support web services, security?
 Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo 
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list 
Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user-
Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
Wicket-user mailing listWicket-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wicket-user

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Johannes Fahrenkrug
Hello Rüdiger,

What do you think about logging false logins on a per-user basis, and
delay the response after the first false attempt by a couple of seconds
until another valid login for that user happened? I think the Linux
shell login works like that.
  

That's not a bad idea... that would mean delaying a response for a 
second or two _every time_ a false login happens... That would be a 
rather simple but yet effective solution, too: It would render brute 
force useless and behave quite similar to the Linux shell login you 
mentioned

Or, one could lock an account completely after say three false attempts,
and send an email to the user with a link to unlock it again.
  

That's also an option... but I think that's mostly used for very high 
risk and high security applications like banking and stuff...
I think GMail uses a captcha after a few (or even just one) false 
login... that would be extremely effective against scripts.

- Johannes


.rue


Johannes Fahrenkrug schrieb:
  

Hi!

I'd like to prevent brute force attacks on the login page of my wicket 
application. What would be the best approach? This is what I'm thinking 
about doing: Record when the last request for the loginpage from a 
certain IP came in and only handle the request when at least a second or 
two have passed.
This would have to be done application wide because when an attacker 
uses a tool like cURL a new session is created with each request.

So what would you guys suggest?

- Johannes

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user






-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

  



-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Korbinian Bachl
emm.. yes i meant captcha - look here for a working wicket example as well
as source-code:

http://www.steinhoefel.de/spots.htm 

as this is a base point of security, it should be maintained by the
webapp...

Regards


 -Ursprüngliche Nachricht-
 Von: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] Im Auftrag 
 von Pierre-Yves Saumont
 Gesendet: Montag, 6. November 2006 15:56
 An: wicket-user@lists.sourceforge.net
 Betreff: Re: [Wicket-user] Prevent Brute Force and the like
 
   Could you please explain cachapta / provide a link to an article?
 
 I suppose he means captcha. You should find this one on google ;-)
 
 Pierre-Yves
 
 Johannes Fahrenkrug a écrit :
  Korbinian,
  
  I'm sorry if I wasn't clear: I didn't plan on blocking anymore 
  permanently, just add one second delays if some IP was 
 flooding me 
  to render brute force attacks useless and impractical.
  
  Could you please explain cachapta / provide a link to an article?
  
  Regards,
  
  Johannes
  
  Korbinian Bachl wrote:
  
  Bad idea - some ISPs and proxys would be locked out... 
 cachapta would 
  be solution of choice here.
 
  Regards
 
  Korbinian
 
 
 
   
 
  -Ursprüngliche Nachricht-
  Von: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] Im Auftrag von 
  Johannes Fahrenkrug
  Gesendet: Montag, 6. November 2006 14:01
  An: wicket-user@lists.sourceforge.net
  Betreff: [Wicket-user] Prevent Brute Force and the like
 
  Hi!
 
  I'd like to prevent brute force attacks on the login page of my 
  wicket application. What would be the best approach? This is what 
  I'm thinking about doing: Record when the last request for the 
  loginpage from a certain IP came in and only handle the 
 request when 
  at least a second or two have passed.
  This would have to be done application wide because when 
 an attacker 
  uses a tool like cURL a new session is created with each request.
 
  So what would you guys suggest?
 
  - Johannes
 
  --
  ---
  Using Tomcat but need to do more? Need to support web services, 
  security?
  Get stuff done quickly with pre-integrated technology to 
 make your 
  job easier Download IBM WebSphere Application Server
  v.1.0.1 based on Apache Geronimo
  http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057;
 
 
  dat=121642
   
 
  ___
  Wicket-user mailing list
  Wicket-user@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wicket-user
 
 
 
 
  
 -
   Using Tomcat but need to do more? Need to support web 
 services, 
  security?
  Get stuff done quickly with pre-integrated technology to make your 
  job easier Download IBM WebSphere Application Server 
 v.1.0.1 based on 
  Apache Geronimo
  
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121
  642 ___
  Wicket-user mailing list
  Wicket-user@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wicket-user
 
   
 
  
  
  
 --
  --- Using Tomcat but need to do more? Need to support web services, 
  security?
  Get stuff done quickly with pre-integrated technology to 
 make your job 
  easier Download IBM WebSphere Application Server v.1.0.1 based on 
  Apache Geronimo
  
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=1216
  42 ___
  Wicket-user mailing list
  Wicket-user@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wicket-user
  
  
  
 
 
 --
 ---
 Using Tomcat but need to do more? Need to support web 
 services, security?
 Get stuff done quickly with pre-integrated technology to make 
 your job easier Download IBM WebSphere Application Server 
 v.1.0.1 based on Apache Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057;
dat=121642
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user
 


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Korbinian Bachl
heck - wrong link from another posting... sorry:
http://www.wicket-library.com/wicket-examples/captcha

(the other one is of a story here:
http://www.heise.de/newsticker/meldung/80580 - in german only)

Regards
 

 -Ursprüngliche Nachricht-
 Von: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] Im Auftrag 
 von Korbinian Bachl
 Gesendet: Montag, 6. November 2006 16:20
 An: [EMAIL PROTECTED]; wicket-user@lists.sourceforge.net
 Betreff: Re: [Wicket-user] Prevent Brute Force and the like
 
 emm.. yes i meant captcha - look here for a working wicket 
 example as well as source-code:
 
 http://www.steinhoefel.de/spots.htm 
 
 as this is a base point of security, it should be maintained 
 by the webapp...
 
 Regards
 
 
  -Ursprüngliche Nachricht-
  Von: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] Im Auftrag von 
  Pierre-Yves Saumont
  Gesendet: Montag, 6. November 2006 15:56
  An: wicket-user@lists.sourceforge.net
  Betreff: Re: [Wicket-user] Prevent Brute Force and the like
  
Could you please explain cachapta / provide a link to 
 an article?
  
  I suppose he means captcha. You should find this one on google ;-)
  
  Pierre-Yves
  
  Johannes Fahrenkrug a écrit :
   Korbinian,
   
   I'm sorry if I wasn't clear: I didn't plan on blocking anymore 
   permanently, just add one second delays if some IP was
  flooding me
   to render brute force attacks useless and impractical.
   
   Could you please explain cachapta / provide a link to 
 an article?
   
   Regards,
   
   Johannes
   
   Korbinian Bachl wrote:
   
   Bad idea - some ISPs and proxys would be locked out... 
  cachapta would
   be solution of choice here.
  
   Regards
  
   Korbinian
  
  
  

  
   -Ursprüngliche Nachricht-
   Von: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] Im 
 Auftrag von 
   Johannes Fahrenkrug
   Gesendet: Montag, 6. November 2006 14:01
   An: wicket-user@lists.sourceforge.net
   Betreff: [Wicket-user] Prevent Brute Force and the like
  
   Hi!
  
   I'd like to prevent brute force attacks on the login page of my 
   wicket application. What would be the best approach? 
 This is what 
   I'm thinking about doing: Record when the last request for the 
   loginpage from a certain IP came in and only handle the
  request when
   at least a second or two have passed.
   This would have to be done application wide because when
  an attacker
   uses a tool like cURL a new session is created with 
 each request.
  
   So what would you guys suggest?
  
   - Johannes
  
   --
   ---
   Using Tomcat but need to do more? Need to support web services, 
   security?
   Get stuff done quickly with pre-integrated technology to
  make your
   job easier Download IBM WebSphere Application Server
   v.1.0.1 based on Apache Geronimo
   http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057;
  
  
   dat=121642

  
   ___
   Wicket-user mailing list
   Wicket-user@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/wicket-user
  
  
  
  
   
  
 -
    Using Tomcat but need to do more? Need to support web
  services,
   security?
   Get stuff done quickly with pre-integrated technology to 
 make your 
   job easier Download IBM WebSphere Application Server
  v.1.0.1 based on
   Apache Geronimo
   
  
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121
   642 ___
   Wicket-user mailing list
   Wicket-user@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/wicket-user
  

  
   
   
   
  
 --
   --- Using Tomcat but need to do more? Need to support web 
 services, 
   security?
   Get stuff done quickly with pre-integrated technology to
  make your job
   easier Download IBM WebSphere Application Server v.1.0.1 based on 
   Apache Geronimo
   
  
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=1216
   42 ___
   Wicket-user mailing list
   Wicket-user@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/wicket-user
   
   
   
  
  
  --
  ---
  Using Tomcat but need to do more? Need to support web services, 
  security?
  Get stuff done quickly with pre-integrated technology to 
 make your job 
  easier Download IBM WebSphere Application Server
  v.1.0.1 based on Apache Geronimo
  http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057;
 dat=121642
  ___
  Wicket-user mailing list
  Wicket-user@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Erik van Oosten
Disadvantage is that the server will keep the request processing thread 
occupied during the waiting period. A brute force attach that fires 
multiple requests simultaneously will not be stopped by this and will 
bring the server to its knees even more quickly. So Johan was right, you 
should not do this in the web application.

Now if you start using AsyncWeb it would be quite another story of course...

Regards,
 Erik.


Johannes Fahrenkrug schreef:
 That's not a bad idea... that would mean delaying a response for a 
 second or two _every time_ a false login happens... That would be a 
 rather simple but yet effective solution, too: It would render brute 
 force useless and behave quite similar to the Linux shell login you 
 mentioned
   

-- 
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Prevent Brute Force and the like

2006-11-06 Thread Johannes Fahrenkrug
Erik,

Disadvantage is that the server will keep the request processing thread 
occupied during the waiting period. A brute force attach that fires 
multiple requests simultaneously will not be stopped by this and will 
bring the server to its knees even more quickly. So Johan was right, you 
should not do this in the web application.
  

That is true. But how can I let the server software handle this if I 
want specific behavior only with a certain page of the web application?
Or are you suggesting to let the server software handle all the flooding 
for all the pages of the webapplication (i.e. restricting how many 
requests are processed/handles per second) and to let the webapplication 
handle the specific case of false logins, not caring about how many 
REQUESTS came in, just how many false ATTEMPTS came in?

That sounds like it would make a lot of sense

Now if you start using AsyncWeb it would be quite another story of course...
  

Hmmm, that does look very promising!

- Johannes

Regards,
 Erik.


Johannes Fahrenkrug schreef:
  

That's not a bad idea... that would mean delaying a response for a 
second or two _every time_ a false login happens... That would be a 
rather simple but yet effective solution, too: It would render brute 
force useless and behave quite similar to the Linux shell login you 
mentioned
  



  



-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user