Skip to content

Update exit_node.ts#757

Closed
felurta wants to merge 1 commit intotherealaleph:mainfrom
felurta:patch-2
Closed

Update exit_node.ts#757
felurta wants to merge 1 commit intotherealaleph:mainfrom
felurta:patch-2

Conversation

@felurta
Copy link
Copy Markdown

@felurta felurta commented May 5, 2026

No description provided.

@therealaleph
Copy link
Copy Markdown
Owner

@felurta — this just hard-codes a specific PSK in place of the placeholder. The placeholder is intentional — it's a deliberate fail-closed signal: exit_node.ts returns 503 on every request until the user replaces it with their own random secret (e.g. openssl rand -hex 32). Hard-coding any specific value defeats that defense and would make the published default file insta-usable as an open relay.

If your goal was personal use of your own deployed exit node, don't open a PR — exit_node.ts is a template you copy into your own serverless deployment and customize there. Don't paste your real PSK in a PR or any other public place — anyone with both the PSK and the deployed URL can use your exit node as their own proxy. Rotate it now: change the value in your deployed source, redeploy, and update psk in your config.json.

Same pattern as #693 / #563 / #531. Closing.


[reply via Anthropic Claude | reviewed by @therealaleph]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants