Skip to content

Security: yedvvard/solidworks-remote-bridge

Security

SECURITY.md

Security model

Network boundary

  • The only LAN-facing protocol is the user's existing SSH service.
  • The interactive Broker refuses non-loopback bind addresses.
  • The Broker listens on 127.0.0.1:8765 and requires a per-user random secret.
  • The remote proxy reads the secret on Windows and sends it only over loopback.

Execution boundary

  • The bridge exposes the upstream MCP whitelist; it does not add arbitrary Python or VBA execution.
  • SolidWorks COM calls run only in the logged-in Windows user's interactive session.
  • The upstream MCP lock and the Broker connection lifecycle serialize CAD writes.

Files that must never be committed

  • state/broker.secret
  • .env files
  • Broker/MCP logs containing local paths
  • user CAD files, previews, exports, or diagnostics
  • SSH private keys or copied SSH configuration

The root .gitignore excludes the normal forms of these files. Before pushing, also inspect git status and git diff --cached.

Reporting

For security-sensitive problems, use the private repository's GitHub security advisory feature rather than a public issue.

There aren't any published security advisories