Use the latest released version of LabLink, or the current default branch if you are validating unreleased changes.
If this repository is hosted on GitHub, please use private vulnerability reporting / GitHub Security Advisories for sensitive reports when that feature is enabled.
If private reporting is not available:
- Do not open a public issue for a security vulnerability.
- Contact the repository maintainers through a private channel provided by the hosting organization.
- Include the affected version, reproduction details, impact, and any relevant logs or configuration notes.
For public or shared environments, the recommended LabLink configuration is:
scripts\bootstrap-operator.ps1scripts\bootstrap-windows-node.ps1LABLINK_TRANSPORT=mtlsLABLINK_AGENT_TOKEN_FILE- generated client/server certificates from
lablink-ca.exe
Avoid:
LABLINK_TRANSPORT=insecureoutside migration scenarios- committing token files, private keys, or issued certificates to source control
- reusing the same PKI material across unrelated environments
The recommended public path uses token files plus local filesystem ACLs instead of placing shared tokens directly in .mcp.json.
save_credential opens a separate local masked terminal. Passwords never pass
through MCP and are encrypted at rest with user-scoped DPAPI on Windows or
AES-GCM in the credential-store implementation on non-Windows hosts.
credentials.json contains metadata only. Automatic prompt launching is
currently supported on Windows.
On shared operator machines, you may still prefer:
- interactive
PSCredentialprompts - the bootstrap scripts
- or an external secret-management workflow
This document covers vulnerabilities in the LabLink codebase and the recommended bootstrap/deployment flow that ships with it.