Change: Separate Code Execution from Warlock Messaging

Problem Statement

The current Warlock message service in Hazaar MVC includes code execution capabilities. To enhance security and maintain control, code execution should remain local to the node and not be distributed to other nodes. This requires separating the Warlock server features so that another process handles code execution, while the main Warlock server focuses solely on messaging.

Who will benefit?

Developers and system administrators will benefit from improved security and control over code execution, while maintaining robust messaging capabilities across nodes.

Benefits and risks

Benefits

• Ensures that code execution remains local to the node, maintaining security and control.
• Simplifies the main Warlock server process by focusing it solely on messaging.

Risks

• Requires careful separation of code execution logic to maintain the integrity and security of the system.
• Potential challenges in coordinating the communication between the messaging server and the code execution process.

Proposed solution

1. Separate the Warlock server features to create a dedicated process for handling code execution.
2. Ensure the main Warlock server process is focused solely on messaging.
3. Implement mechanisms to distinguish and route messages appropriately, ensuring that code execution messages are not distributed to other nodes.

Examples

N/A

Priority/Severity

• High (This will bring a huge increase in performance/productivity/usability/legislative cover)
• Medium (This will bring a good increase in performance/productivity/usability)
• Low (anything else e.g., trivial, minor improvements)