openclaw - 💡(How to fix) Fix Add opt-in message-level signing for mcporter stdio transport [1 comments, 1 participants]

Fix Plan

To add opt-in MCPS (MCP Secure) signing to mcporter, follow these steps:

• Install the mcp-secure package: npm install mcp-secure
• Import the signMessage and verifyMessage functions from mcp-secure
• Wrap outgoing messages with signMessage(msg, passportId, privateKey)
• Verify incoming messages with verifyMessage(envelope, publicKey)

Example code:

const { signMessage, verifyMessage } = require('mcp-secure');

// Outgoing message
const msg = { /* JSON-RPC message */ };
const passportId = 'agent-id';
const privateKey = 'private-key';
const signedMsg = signMessage(msg, passportId, privateKey);
// Send signedMsg

// Incoming message
const envelope = { /* incoming message envelope */ };
const publicKey = 'public-key';
const isValid = verifyMessage(envelope, publicKey);
if (isValid) {
  // Message is valid, process it
} else {
  // Message is invalid, reject it
}

Verification

To verify that the fix worked, test the following scenarios:

• Send a signed message from an agent to the MCP server and verify that it is processed correctly
• Send an unsigned message from an agent to the MCP server and verify that it is still processed correctly (since the security layer is opt-in)
• Attempt to replay a signed message and verify that it is rejected by the MCP server

Extra Tips

• Make sure to handle errors and exceptions properly when signing and verifying messages
• Consider implementing a mechanism to rotate private keys and update public keys in case of a security breach
• Refer to the IETF Internet-Draft draft-sharif-mcps-secure-mcp for more information on the MCPS protocol.