packages/admin/sudo, branch master

sudo: add test-version.sh and stop running sudo in tests

2026-08-10T17:17:56Z

PKG_VERSION substitutes p->_p (1.9.17_p2) for a valid apk version, but the binaries print the real 1.9.17p2, so the generic per-executable version probe reports "no executables provided version" and fails. Add a test-version.sh that matches the version string compiled into the binary. Executing sudo under QEMU emulation (e.g. mips_24kc) hangs indefinitely, so neither test-version.sh nor test.sh runs it any more: the version is read from the binary and test.sh only checks the installed files. Signed-off-by: Alexandru Ardelean

sudo: drop 020-no-owner-change.patch for a make override

2026-08-10T17:17:56Z

The patch blanked INSTALL_OWNER in Makefile.in so the staged install does not chown to install_uid/install_gid, which fails when building as an unprivileged user. sudo already supports this: the top-level install rule recurses with "INSTALL_OWNER=$(INSTALL_OWNER)" into every sub-make, and sudo's own "package" target does "make install INSTALL_OWNER=" for exactly this fakeroot case. Pass INSTALL_OWNER= via MAKE_INSTALL_FLAGS instead of carrying a patch. Signed-off-by: Alexandru Ardelean

sudo: create sudo group

2026-08-07T10:34:12Z

Add a 'sudo' system group at package-install time using the USERID mechanism. Rationale: sudoers configurations that grant privileges to the 'sudo' group -- the near-universal Debian/Ubuntu idiom, e.g. %sudo ALL=(ALL:ALL) NOPASSWD: ALL -- fail silently on OpenWrt today because no 'sudo' group exists in /etc/group. sudo(8) logs 'unknown group: sudo' and the rule is skipped. Users also cannot 'usermod -aG sudo ' without the group present, so there is no straightforward way to delegate root without hand-editing /etc/group or writing per-user sudoers snippets. Seeding the group here matches how OpenWrt already handles other service accounts (chrony, dbus, ntpd, ...): the USERID mechanism creates them lazily via add_group_and_user in the postinst script. No privileges are granted by default -- an administrator still has to add users to the group and ship a sudoers rule that references it. No numeric GID is pinned. The group name is what sudoers, addgroup(1), and getgrnam() operate on; the numeric GID is invisible to sudo's authorisation path and matters only for on-disk group ownership metadata (e.g. 'chgrp sudo' persisted to shared storage) -- something this package does not do. Letting add_group_and_user pick a dynamic GID in the 32768+ range keeps sudo out of base-files' reserved low-range group space and avoids any name-vs-number collision debate. Bump PKG_RELEASE. Signed-off-by: Michael Pfeifroth

sudo: bump to version 1.9.17p2

2025-08-12T18:56:54Z

This change bumps sudo to version 1.9.17p2 Signed-off-by: Alexandru Ardelean

sudo: Fix license file

2025-07-18T14:24:46Z

Signed-off-by: Jan Kardell

sudo: adjust with glibc and libcrypt-compat

2025-07-14T08:40:15Z

glibc 2.39 has removed libcrypt completely. solution: link against libxcrypt built with glibc compatibility. Signed-off-by: Konstantin Demin

sudo: bump to version 1.9.17p1

2025-07-11T16:41:31Z

Fixes: CVE-2025-32462 Fixes: CVE-2025-32463 Signed-off-by: Jan Kardell

sudo: bump to version 1.9.16p2

2024-12-25T19:33:31Z

Signed-off-by: Alexandru Ardelean

sudo: modify version to Alpine Linux one

2024-08-17T01:40:31Z

The goal here is compatibility with APK. Signed-off-by: Rosen Penev

admin/sudo: fix PKG_CPE_ID

2024-02-02T21:35:50Z

sudo_project:sudo is a better CPE ID than todd_miller:sudo as this CPE ID has the latest CVEs (whereas todd_miller:sudo only has CVEs up to 2016): https://nvd.nist.gov/products/cpe/search/results?keyword=cpe:2.3:a:sudo_project:sudo Fixes: 8ce9f30c421255c514b1b2e41fc92eafd7976583 (sudo: Update to 1.8.24) Signed-off-by: Fabrice Fontaine