fix: clear TS_AUTHKEY env after config resolution#199
Merged
Conversation
The tsnet library independently reads TS_AUTHKEY from the process environment via getAuthKey(), even when tsbridge has determined that existing state should be used. This can cause control servers (particularly Headscale) to register a new node on each restart instead of reusing the existing one. Clear TS_AUTHKEY and TS_AUTH_KEY from the environment after resolving them into the config struct. Cache the resolved Tailscale config in the Docker provider so subsequent Load() calls don't fail from the cleared env vars.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The tsnet library independently reads TS_AUTHKEY from the process environment via getAuthKey(), even when tsbridge has determined that existing state should be used. This can cause control servers (particularly Headscale) to register a new node on each restart instead of reusing the existing one.
Clear TS_AUTHKEY and TS_AUTH_KEY from the environment after resolving them into the config struct. Cache the resolved Tailscale config in the Docker provider so subsequent Load() calls don't fail from the cleared env vars.