use 0600 as default proxy socket endpoint file mode#62
Merged
wollomatic merged 1 commit intoSep 30, 2025
Merged
Conversation
wollomatic
approved these changes
Sep 30, 2025
Owner
|
Thank You @amanda-wee for fixing this! |
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
2 participants
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 README documents that the default value for the proxy socket endpoint file mode parameter/environment variable is
0600, but the code actually has it as0400. I could not get the unix socket to work with my Beszel agents with the default (no error message, yet no data retrieved), but when I checked the newly added wiki example, I saw that it explicitly set this parameter to0600. Copying this allowed my setup to work, so I'm proposing that the actual default value be changed to0600to match the README.