meulengracht / libgracht Goto Github PK

Currently there is no protection against serializing too much data and deserializing a message that is too large. Max Message Size is defined in both client and server - and we have no "negotiation" phase which would inform each other of their respective max sizes. A solution needs to be defined for this and implemented.

Since this library is communications-focused, security should be in order. We need to identify the security vulnerabilities, places where we do not protect/defend against input from bad players.

Currently the windows build is failing due to missing C99 features and because WSA does not match the interface that posix has for sockets. So we need to implement and correctly facilitate the differences in sockets in the code.

• Remove usage of VLAs
• Implement *_msg equivents.
• Handle MSG_WAITALL and MSG_DONTWAIT

Proper error handling is missing from the parser, currently both the line number and line offset is wrong. And it only prints out that an unexpected token was encountered, not a more precise reason the parsing failed.

Before we release libgracht 1.0 we need to cleanup and document the APIs, and fill the README.

• Cleanup header files and add parameter names
• Add API documentation for all calls
• README: Information about required dependencies (thread lib)
• README: Examples
• README: More about link seperation?
• README: Fill out api descriptions
• README: Multi-calling (message contexts) and multi-waiting.

In case of invalid messages.

Currently only linux implements the flag MSG_DONTWAIT. I have yet to identify which measures I have to take to make sure this is not an issue with the windows build.

This is a todo for my personal project, I need to update Vali to use the Gracht V2 and update the link as I have to refactor my ipc implementation to allow for raw buffer transfer.