aMule Forum
English => en_Bugs => Topic started by: ced on December 03, 2005, 03:52:23 PM
-
Bugs reproduce on amule-cvs(20051202):
The requests are funny, other random data could lead to same results or crash amuled.
Of course, no sense to connect on 4712 with a browser. :D
This request make unavailable communication with port 4712 (amulecmd and amuleweb segfault)
http://192.168.0.1:4712/if(this->request){packet_data=schmilblick;}else{packet_data=NULL;}return; (http://192.168.0.1:4712/if(this->request){packet_data=schmilblick;}else{packet_data=NULL;}return;)
Amuled debug messages:
ZLib operation returned Z_DATA_ERROR
ZLib error message: incorrect header check
zstream state:
next_in=0x993662a
avail_in=506
total_in=2
next_out=0x993e630
avail_out=32768
total_out=0
CECSocket error: Invalid socket (uninitialized)
CECSocket error: Invalid socket (uninitialized)
CECSocket error: Invalid socket (uninitialized)
This request cause amuled to consume a lot of memory and cpu time
http://192.168.0.1:4712/if(this-> (http://192.168.0.1:4712/if(this->)
After 2 minutes depend memory capacity on the system, launch the request one more time
and port 4712 is unavailable, cpu time usage increase.
----------------------------------------------
Amuled debug messages after the first request:
ZLib operation returned Z_DATA_ERROR
ZLib error message: incorrect header check
zstream state:
next_in=0x9764e32
avail_in=440
total_in=2
next_out=0x976d008
avail_out=32768
total_out=0
CECSocket error: Invalid socket (uninitialized)
-----------------------------------------------
Amuled debug messages after the second request:
ZLib operation returned Z_DATA_ERROR
ZLib error message: incorrect header check
zstream state:
next_in=0x40b89de2
avail_in=440
total_in=2
next_out=0x40b91de8
avail_out=32768
total_out=0
CECSocket error: Invalid socket (uninitialized)
CECSocket error: Invalid socket (uninitialized)
CECSocket error: Invalid socket (uninitialized)
-
Yeah well. *some* people must better increase EC port protection against wrong packets.
-
Kry, if some people would connect other than at home ...
-
I was meaning aMule developers, not other people :P
As in "fuck, this has to be fixed"
-
I've misunderstood :P