search

ravthan / all-eyes

Automatically exported from code.google.com/p/all-eyes
0 stars 0 forks source link

monitor/aeMgr message coming across two TCP packets #43

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Right now the message processing routines assume the entire message i.e. from 
monitor(s) and aeManager come in a single packet with the headeer "[:" and the 
ending with the trailer ":]".  But it can come across two TCP packets.  Message 
processing routines may have to do more sophisticated buffering.  It is not 
doing it for this prototype.

More over a rogue monitor can stage such attack also.  Make sure this is 
handled properly,
ravi.

Original issue reported on code.google.com by ravt...@gmail.com on 28 Oct 2012 at 2:53

GoogleCodeExporter commented 8 years ago 
For prototype, the maximum message size will be 1024, which should fix in one 
tcp packet.  In 1.0, update code to handle larger message.

Original comment by heyyoul...@gmail.com on 30 Oct 2012 at 2:09

GoogleCodeExporter commented 8 years ago 
Our protocol design includes the message beginning marker and ending marker. 
The markers are used for such situation that a message is divided into multiple 
TCP packets. The receiver process design should include the notion that a 
message can be received by reading multiple TCP packets and then combined them 
into the expected message. The timeout routine should be used to govern the 
waiting time for receiving all packets for a message, etc.

Original comment by toddd...@gmail.com on 30 Oct 2012 at 2:17

GoogleCodeExporter commented 8 years ago

Original comment by ravt...@gmail.com on 14 Nov 2012 at 3:21