Use dedicated halpid group for socket access control#98
Merged
Conversation
Replace the overly broad `adm` group with a dedicated `halpid` system group (GID 960) for socket permission control. The postinst now creates the group and adds the default user (UID 1000) to it for CLI access. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
admgroup with a dedicatedhalpidsystem group (GID 960) for socket permission controlgroup_addin docker-composeCompanion PR: halos-org/halos-marine-containers#132 (adds
group_add: ["960"]to Signal K container)Closes hatlabs/signalk-halpi#2
Test plan
getent group halpidshows GID 960root:halpid 0660at/run/halpid/halpid.sockhalpiCLI tool still works (default user in halpid group)🤖 Generated with Claude Code