Re: asyncore DoS vulnerability

2007-02-03 Thread aspineux
On 2 fév, 16:32, "billie" <[EMAIL PROTECTED]> wrote: > >> Why does this exception isn't handled inside asyncore.py? > > To do what ? To raise a custom asyncore error ? > > asyncore aims to be a framework, right? > I think that when select() limit is reached asyncore should just drop > other connect

Re: asyncore DoS vulnerability

2007-02-03 Thread billie
On 2 Feb, 17:09, "Chris Mellon" <[EMAIL PROTECTED]> wrote: > Thats like asking why you should have to move your fingers to type or > why you should have to eat food in order to not starve. Windows is > placing a limit of 512 descriptors per process. Call Microsoft if you > want to go over that. ?

Re: asyncore DoS vulnerability

2007-02-02 Thread paul
Jean-Paul Calderone schrieb: > It could ask the application. On the other hand, maybe asyncore remains in > a perfectly consistent state even after it raises this exception, and it is > already "asking" by letting this exception propagate up: if the application > is free to start the loop again af

Re: asyncore DoS vulnerability

2007-02-02 Thread Jean-Paul Calderone
On Fri, 2 Feb 2007 10:39:57 -0600, [EMAIL PROTECTED] wrote: > >billie> asyncore aims to be a framework, right? I think that when >billie> select() limit is reached asyncore should just drop other >billie> connections. That's all. > >You're asking asyncore to make a policy decision on b

Re: asyncore DoS vulnerability

2007-02-02 Thread skip
billie> asyncore aims to be a framework, right? I think that when billie> select() limit is reached asyncore should just drop other billie> connections. That's all. You're asking asyncore to make a policy decision on behalf the controlling application. It has no idea what that appli

Re: asyncore DoS vulnerability

2007-02-02 Thread Chris Mellon
On 2 Feb 2007 07:32:14 -0800, billie <[EMAIL PROTECTED]> wrote: > > This is not a CRASH, It looks an exception with a "Traceback", this is > > the normal way python report problems, nothing wrong with that. > > You can handle it with a try: except: > > I think that such a thing should be handled by

Re: asyncore DoS vulnerability

2007-02-02 Thread billie
> This is not a CRASH, It looks an exception with a "Traceback", this is > the normal way python report problems, nothing wrong with that. > You can handle it with a try: except: I think that such a thing should be handled by asyncore itself. > 512 is probably a fixed limit into XP, win2k3 or win

Re: asyncore DoS vulnerability

2007-02-02 Thread aspineux
Did you take a look for "too many file descriptors in select()" on google. On 1 fév, 20:18, "billie" <[EMAIL PROTECTED]> wrote: > Hi all. I've just terminated a server application using asyncore / > asynchat frameworks. > I wrote a test script that performs a lot of connections to the server > app

Re: asyncore DoS vulnerability

2007-02-02 Thread William Heymann
On Thursday 01 February 2007, billie wrote: > Here's the traceback: > > Traceback (most recent call last): > File "C:\Documents and Settings\root\Desktop\test.py", line 31, in ? > asyncore.loop(timeout=1) > File "C:\Python24\lib\asyncore.py", line 192, in loop > poll_fun(timeout, map)