search

berkus / kbus

Automatically exported from code.google.com/p/kbus
Other
1 stars 0 forks source link

There is no way to set the maximum message size #62

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
In earlier versions of KBUS, there was a fixed maximum message size. When this 
was removed, a settable value should have replaced it, but did not. Without 
this, there is nothing to stop a user from creating an incredibly large message 
as a denial of service attack (or just carelessness).

Two values should be supplied: an absolute maximum message size, determined at 
compile time, above which the maximum message size cannot be set, and a default 
maximum message size.

An ioctl should also be introduced to change the current maximum, on a 
particular KBUS device.

A lower limit of greater than the size of a message header (80 bytes on a 
32-bit machine) should be enforced (e.g., 100).

Original issue reported on code.google.com by t...@tibsnjoan.co.uk on 14 Apr 2011 at 2:46

GoogleCodeExporter commented 9 years ago 
The kernel module has been updated to have the appropriate new ioctl.

The Python module has been updated to support it.

The Python tests now test it.

Outstanding is adding support to the C, C++ and Java libraries.

Original comment by t...@tibsnjoan.co.uk on 14 Apr 2011 at 4:54