thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.5
Status: Open
Resolution: None
Priority: 9
Private: No
Submitted By: billiejoex (billiejoex)
Assigned to: Josiah Carlson (josiahcarlson)
Summary: asyncore DoS
DoS vulnerability
Initial Comment:
DoS asyncore vulnerability
asyncore, independently if used with select() or poll(), suffers a DoS-type
vulnerability when a high number of simultaneous connections to handle
simultaneously is reached.
The number of maximum connections is system-dependent as well
thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.5
Status: Open
Resolution: None
Priority: 9
Private: No
Submitted By: billiejoex (billiejoex)
Assigned to: Nobody/Anonymous (nobody)
Summary: asyncore DoS
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.
?
That's
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 connections. That's
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)
File
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 and I
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 win2k
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 asyncore
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
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 behalf
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 after
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 and I discovered that asyncore (or better, select()) can manage
only a limited number of file descriptors (aka simultaneous
13 matches
Mail list logo
