OpenCode/MeshBot
2
0
Fork 0
Code Issues Pull Requests Actions Activity

Remove insecure NODE_TLS_REJECT_UNAUTHORIZED=0 TLS workaround (follow-up to #56) #57

Merged
kamilkrzywda merged 1 commits from feat/meshmonitor-connection into main 2026-10-13 03:13:22 +02:00
Conversation 0 Commits 1 Files Changed 3
+1 -7
1 Commits
Author SHA1 Message Date
kamilkrzywdaandOpenCode 25f99f04ad Remove insecure NODE_TLS_REJECT_UNAUTHORIZED=0 TLS workaround
CI / build + unit (pull_request) Successful in 46s
Details 
The MeshMonitor gateway uses a valid Let's Encrypt certificate, so
standard TLS certificate verification already works — no workaround
needed. The flag was a security downgrade: it disabled cert verification
for ALL outbound connections in the container (including the LLM and
opencode services), not just the gateway.

- docker-compose.yml: drop NODE_TLS_REJECT_UNAUTHORIZED env line + comment
- src/main.ts: drop process.env.NODE_TLS_REJECT_UNAUTHORIZED + comments
- CHANGELOG.md: correct the v0.22.0 Docker bullet wording

Part of the already-open MeshMonitor connection work (PR #56): no version
bump, no new changelog section.

Co-Authored-By: OpenCode <noreply@opencode.ai>
 2026-10-13 01:07:36 +00:00