Files
shadow/CONTRIBUTING.md
T
Jocelyn Le SageandPierre Warnier 8361bf512b gpasswd: added implementation of gpasswd (#282)
* gpasswd: added implementation of gpasswd

* gpasswd: rebase onto main and port to the current APIs

Rebases jlesage's implementation onto a main that moved a long way under
it, and carries it onto the interfaces that landed since the branch was
cut. The tool's behaviour is unchanged and still matches GNU on every
path probed.

What the rebase had to resolve:

  - shadow-rs.spec and debian/ were revived by the merge; both were
    deleted because neither could build.
  - The standalone dispatch() and hand-written --list predate the single
    applets() table, which now drives both. gpasswd joins the table.
  - The five shadow-core parser features it asked for no longer exist.
  - The fourteen [[test]] targets are one; test_gpasswd joins it.
  - README, Makefile and PLATFORM-SUPPORT described the pre-#239
    privilege model, in which every applet ran with euid 0.

What changed beyond the rebase:

  - gpasswd keeps its privilege in the multicall build. It is setuid in
    GNU and the branch marks it setuid for the per-tool install, but
    SETUID_APPLETS still listed four names, so the multicall build would
    have dropped privilege and no group administrator could have used it
    -- silently.
  - Comments in /etc/group survive. It read entries only and wrote them
    back, which erases every comment, blank line and NIS compatibility
    line in the file. The locked-file transaction keeps them, and commits
    group and gshadow together so a bad value cannot leave the pair
    disagreeing.
  - The duplicated EchoGuard and password reader are gone, replaced by
    shadow_core::tty, which blocks interrupts for the read so Ctrl-C at
    the prompt cannot leave the terminal with echo off.
  - The print macros are replaced. They panic when the stream is closed,
    which a setuid-root tool must not do part way through a change.
    These were the only five in the repository and no lint caught them,
    so clippy::print_stdout and print_stderr are now denied
    workspace-wide, with the test crate exempt.

The GNU comparison suite gains gpasswd: the unknown-group, unknown-user
and non-member exit codes, all three of which match.

CONTRIBUTING's licence list also said ISC, BSD-2-Clause, CC0-1.0, Zlib
and MPL-2.0 were acceptable, which stopped being true when deny.toml was
narrowed to the graph. It now says what deny.toml enforces.

---------

Co-authored-by: Pierre Warnier <pierre@warnier.net>
2026-09-06 11:03:53 +02:00

6.7 KiB

Contributing to shadow-rs

Thanks for wanting to contribute to shadow-rs! This document explains everything you need to know.

Before you start, also check:

Warning

shadow-rs is original code and cannot contain any code from GNU shadow-utils or other GPL-licensed implementations. This means that we cannot accept any changes based on the shadow-maint/shadow source code (GPL-2.0+). To make sure that cannot happen, you must not read or link to the GNU source code. This includes paraphrasing or translating their logic, and feeding it into an LLM for translation.

Safe Reference Sources

When implementing a tool, reference ONLY these sources:

Source License Use
POSIX specification Open standard Behavioral spec
Man pages (man7.org) Documentation Command options, file formats
FreeBSD src BSD-2-Clause Implementation patterns
OpenBSD src ISC Implementation patterns
musl libc MIT pwd/grp/shadow C API
sudo-rs Apache-2.0 / MIT PAM, privilege-dropping

Process: Read the POSIX spec and man page for behavioral requirements, then write an original implementation. Never search for or view the C source.

Getting Started

Requirements

  • Docker and Docker Compose (all builds/tests run in containers)
  • Git

Setup

git clone https://github.com/uutils/shadow
cd shadow
docker compose build
./hooks/install.sh  # install pre-commit and pre-push hooks

The hooks are deliberately small. pre-commit checks formatting and runs clippy; pre-push runs make test once, on Debian, and skips entirely for a push that carries no new commits (a tag, a deletion, a branch the remote already has). Everything else — MSRV, cargo-deny, the static musl archive, the three-distro matrix as root, the GNU output comparison and the end-to-end deployment image — runs in CI on the pull request, in parallel and with retries. A hook that tried to match CI took minutes on every push and was routed around with --no-verify, which protects nothing.

There is a second hook system, .pre-commit-config.yaml, run by pre-commit.ci on the pull request. It does not overlap: whitespace, line endings, large files, and the spell checker. The two are kept apart on purpose — file hygiene needs no container, and the Rust checks need one.

Building and Testing

make check is the single definition of what CI gates on — formatting, clippy with and without pam, and the tests in both configurations. Run it in a container; do not build on the host.

docker compose run --rm debian make check           # everything CI gates on
docker compose run --rm debian make test-gnu-compat # compare against GNU

docker compose run --rm debian cargo build          # build
docker compose run --rm debian cargo test --workspace  # test on Debian
docker compose run --rm alpine cargo test --workspace  # test on Alpine (musl)
docker compose run --rm fedora cargo test --workspace  # test on Fedora (SELinux)

All three must pass. The alpine image tests musl with dynamic linking; the release also ships a static musl archive, built without PAM, which make dist-musl reproduces and CI builds on every pull request. What that build gives up is documented in docs/PLATFORM-SUPPORT.md.

Linting

docker compose run --rm debian cargo clippy --workspace --all-targets -- -D warnings
docker compose run --rm debian cargo fmt --all --check

Design Goals

  • Drop-in replacement: same flags, same exit codes, same output format as GNU shadow-utils. Differences with GNU are treated as bugs.
  • uutils compatible: tools use uucore (UResult<()>, #[uucore::main], show_error!) so they can be merged into the uutils ecosystem.
  • Memory safe: no .unwrap(), no panic!, no std::process::exit in library code.
  • Well-tested: unit tests, proptest, integration tests, fuzz targets.

Our Rust Style

Don't panic!

Never use .unwrap() or panic!. Use unreachable! only with a justifying comment. Return errors via UResult<()>.

Don't exit

Utilities must be embeddable. Return UResult<()> from uumain. The uucore::bin!() macro handles process::exit in the generated main().

unsafe

Denied at the workspace level (unsafe_code = "deny"). Only three FFI boundary modules are exempted: shadow_core::pam (PAM C library), shadow_core::crypt (POSIX crypt(3)) and shadow_core::process (setuid, signal masks, getpwuid_r). Every unsafe block must have a // SAFETY: comment.

str, OsStr & Path

Use OsStr and Path for filesystem paths. Only convert to String/str when you know the data is always valid UTF-8 (usernames, for example).

Comments

Comments explain why, not what. If you need to describe what code does, improve the naming instead.

Commits

  • Small, atomic commits — one logical change per commit
  • Tool-prefixed messages: passwd: fix buffer handling
  • Test commits: tests/passwd: add aging test
  • Do not move code in the same commit as a behavior change

Pull Requests

  • One issue per PR, reference it: Fixes #N
  • Title prefixed with tool name, under 70 characters
  • Branch naming: fix/N-short-description or feat/N-short-description
  • CI must pass (clippy, fmt, tests on all 3 distros)
  • Keep PRs small and self-contained

AI-Assisted Development

AI tools (Copilot, Claude, etc.) are allowed and treated like any other development tool.

  • All code must be understood, reviewed, and tested by human contributors
  • Clean-room rule is absolute — never feed GPL source into an LLM
  • Reference only: POSIX specs, man pages, BSD-licensed implementations
  • If a PR is substantially AI-generated, note it (transparency, not a blocker)
  • Quality is the gate — contributions are judged on correctness and test coverage, not authorship method

Licensing

shadow-rs is distributed under the terms of the MIT License.

Acceptable dependency licences are exactly the ones the dependency graph uses today: MIT, Apache-2.0, BSD-3-Clause, Unicode-3.0. The list is deliberately no wider than the graph, so a crate arriving under a new licence is a decision someone records in deny.toml rather than something that passes silently.

No GPL or LGPL dependencies, ever, and no MPL-2.0 either: it is file-level copyleft and this project ships MIT only.