Skip to content

release: 0.4.0 - #289

Merged
pierre-warnier merged 1 commit into
mainfrom
docs/platform-support-gpasswd
Sep 6, 2026
Merged

release: 0.4.0#289
pierre-warnier merged 1 commit into
mainfrom
docs/platform-support-gpasswd

Conversation

@pierre-warnier

Copy link
Copy Markdown
Collaborator

gpasswd is a fifteenth tool, so a minor bump rather than a patch.

Documentation the new tool invalidated

docs/PLATFORM-SUPPORT.md describes what the static musl build gives up, tool
by tool. gpasswd changes each of the three sections and none of them had been
updated:

  • No PAM. chfn and chsh become root-only there because they authenticate
    through PAM. gpasswd does not — like newgrp it checks the group password
    through crypt(3) — so it keeps working for a group administrator in the musl
    build. It was silently lumped in with "the other eleven tools, which are
    root-only anyway", which is wrong twice over: the count and the claim.
  • No NSS. gpasswd resolves the caller through getpwuid_r, so it joins
    the list of tools that cannot see directory users there. It was in the list
    but the sentence below still said "those five tools".
  • No yescrypt. gpasswd can neither verify nor set a $y$ group password,
    the same gap newgrp has.

The README's multicall paragraph also still named four setuid applets.

Verified

make check              exit 0
GNU comparison          42 passed, 0 unexpected
dist plan               announcing v0.4.0, three archives
musl archive            all 15 applets, gpasswd included

Tagging 0.4.0 after this publishes. The pipeline is the one that worked for
0.3.1, so I expect no repeat of that adventure — I will check the archives
afterwards regardless.

gpasswd is a fifteenth tool, so a minor bump rather than a patch.

Also corrects the three static-musl sections for it. gpasswd is setuid
and authenticates a group administrator against the group password
through crypt(3) rather than PAM, so unlike chfn and chsh it keeps
working in the musl build; it resolves the caller through getpwuid_r, so
it joins the five tools that do not see directory users there; and it can
neither verify nor set a yescrypt group password. The counts around those
paragraphs were left at fourteen tools.

The README's multicall paragraph still named four setuid applets.
@pierre-warnier
pierre-warnier merged commit e33793c into main Sep 6, 2026
18 checks passed
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.

1 participant