Debian Patches
Status for shadow/1:4.17.2-5
Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
debian/Set-group-and-mode-for-g-shadow-files.patch | Set group and mode for [g]shadow files Set group 'shadow' and mode 0400. |
Shadow package maintainers <pkg-shadow-devel@lists.alioth.debian.org> | no | 2024-06-22 | ||
debian/Keep-using-Debian-adduser-defaults.patch | Keep using Debian's adduser defaults Upstream's bbf4b79bc49fd1826eb41f6629669ef0b647267b commit in 4.9 merged those values from upstream's default configuration file which is not shipped in Debian. This patch keeps the program's compiled in defaults in sync with the configuration files shipped in Debian (debian/default/useradd). |
Balint Reczey <balint@balintreczey.hu> | not-needed | debian upstream | 2024-06-22 | |
debian/Document-the-shadowconfig-utility.patch | Document the shadowconfig utility Status wrt upstream: The shadowconfig utility is Debian-specific. The man page is Debian-specific, but it used to be distributed by upstream. |
Shadow package maintainers <pkg-shadow-devel@lists.alioth.debian.org> | no | 2024-06-22 | ||
debian/Recommend-using-adduser-and-deluser.patch | Recommend using adduser and deluser Status wrt upstream: Debian specific patch. |
Shadow package maintainers <pkg-shadow-devel@lists.alioth.debian.org> | no | 2024-06-22 | ||
debian/tests-disable-su.patch | upstream testsuite: disable su tests Debian uses su from util-linux, pointless/impossible to test shadow's su here. |
Serge Hallyn <serge@hallyn.com> | no | 2024-06-27 | ||
debian/Adapt-login.defs-for-Debian.patch | Adapt login.defs for Debian Remove settings only applicable to shadow's su, which we do not use. Remove settings only applicable without PAM support enabled. Remove obscure commented-out settings. Remove explanation about write(1), which Debian does not ship anymore. |
Shadow package maintainers <pkg-shadow-devel@lists.alioth.debian.org> | no | 2024-07-07 | ||
debian/Define-LOGIN_NAME_MAX-on-HURD.patch | Define LOGIN_NAME_MAX on HURD | Chris Hofstaedtler <zeha@debian.org> | no | 2024-08-06 | ||
debian/Stop-building-programs-we-do-not-install.patch | Stop building programs we do not install | Chris Hofstaedtler <zeha@debian.org> | no | 2024-08-06 | ||
upstream/a015e919834c90b99947829c6c823f7fe93a8097-E_BAD_NAME.patch | [PATCH] src/useradd.c: E_BAD_NAME: Use a different error code for bad login names Wrappers like adduser(8) want to do their own stuff if the login name is bad. For that, they need to be able to differentiate such an error. |
Alejandro Colomar <alx@kernel.org> | no | debian | 2024-12-05 | |
upstream/man-useradd.8.xml-Document-new-exit-code-19-E_BAD_NAME.patch | man/useradd.8.xml: Document new exit code 19 (E_BAD_NAME) | Marc Haber <mh+debian-packages@zugschlus.de> | no | 2024-12-05 | ||
upstream/Revert-lib-src-Use-local-time-for-human-readable-dates.patch | Revert "lib/, src/: Use local time for human-readable dates" This reverts commit 3f5b4b56268269fefed55aa106f382037297d663. The dates are stored as UTC, and are stored as a number of days since Epoch. We don't have enough precision to translate it into local time. Using local time has caused endless issues in users. This patch is not enough for fixing this issue completely, since printing a date without time-zone information means that the date is a local date, but what we're printing is a UTC date. A future patch should add time-zone information to the date. For now, let's revert this change that has caused so many issues. |
Alejandro Colomar <alx@kernel.org> | no | 2025-02-14 | ||
Revert-lib-strtoday.c-strtoday-Fix-calculation.patch | Revert "lib/strtoday.c: strtoday(): Fix calculation" This reverts commit 1175932c0c86ee46ee298fd9cfa01653a2ba3a27. |
Chris Hofstaedtler <zeha@debian.org> | no | debian | 2025-02-16 | |
Warn-when-badname-and-variants-are-given.patch | Warn when --badname (and variants) are given Upstream PR 1158 will remove them, probably in the forky timeframe. |
Chris Hofstaedtler <zeha@debian.org> | no | 2025-02-17 | ||
upstream/src-chfn.c-Partially-revert-lib-src-Use-strsep-3-instead-.patch | src/chfn.c: Partially revert "lib/, src/: Use strsep(3) instead of its pattern" This partially reverts commit 16cb664865541162c504a6f5ef5ca4b38b5e0c9a. I'll try to reintroduce this change more carefully. For now, let's revert to a known-good state. The problem was due to accidentally ignoring the effects of the 'break' on the 'cp' variable. |
Alejandro Colomar <alx@kernel.org> | no | 2025-02-17 | ||
upstream/src-chfn.c-Use-stpsep-instead-of-its-pattern.patch | src/chfn.c: Use stpsep() instead of its pattern | Alejandro Colomar <alx@kernel.org> | no | 2025-02-17 | ||
upstream/src-chfn.c-Add-local-variable-to-refer-to-the-separated-f.patch | src/chfn.c: Add local variable to refer to the separated field | Alejandro Colomar <alx@kernel.org> | no | 2025-02-17 | ||
upstream/src-chfn.c-copy_field-Rename-local-variable.patch | src/chfn.c: copy_field(): Rename local variable This makes it more obvious what that pointer is. |
Alejandro Colomar <alx@kernel.org> | no | 2025-02-17 |
All known versions for source package 'shadow'
- 1:4.17.2-5 (sid)
- 1:4.16.0-7 (trixie)
- 1:4.13+dfsg1-1 (bookworm)
- 1:4.8.1-1 (bullseye)