Your message dated Mon, 26 Oct 2026 10:19:49 +0000
with message-id <[email protected]>
and subject line Bug#1147179: fixed in sudo 1.9.17p2-9exp1
has caused the Debian Bug report #1147179,
regarding sudo.nss: Add sudoers: files entry to nsswitch.conf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1147179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147179
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sudo
Version: 1.9.17p2-7
Severity: wishlist
Hi Marc,
in the course of getting sssd back into Debian testing, I came across
this last RC bug to fix:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1129522
The bug report is valid and reproducible in a test setup.
In a previous bug fix, it was decided that libsss-sudo owns the
sudoers: entry in nsswitch.conf. When we install the package, it adds
sudoers: sss and sudo immediately stops seeing /etc/sudoers.
There are two meaningful approaches how to address this: add the
sudoers: entry to base-files (and make it an official field in
nsswitch.conf) or (and I think this hadn't come up, so far) sudo
itself owns that nsswitch.conf key/entry.
In fact, sudo works well with /etc/sudoers without an entry in
nsswitch.conf. However, it does not hurt if `sudoers: files` exists in
nsswitch.conf, either. And what package could better own this entry in
nsswitch.conf than sudo itself???
So here is my idea:
* you add a debian/sudo.nss file into the sudo src:pkg with the
following content:
```
sudoers database-add
sudoers first files
```
* And for all other consumers, such as sssd, we add:
debian/control:
Pre-Depends: sudo (>= <version-that-adds-the-above-file>)
debian/lib<foo>-sudo.nss
```
sudoers database-require
sudoers after=files <foo>
```
What do you think? If I have to fix #1129522 only from within
libsss-sudo, it gets really hacky and I'd like to avoid that.
Thanks!
Mike
--
mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: [email protected], http://sunweavers.net
pgpFeY6ksgDAU.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Source: sudo
Source-Version: 1.9.17p2-9exp1
Done: Marc Haber <[email protected]>
We believe that the bug you reported is fixed in the latest version of
sudo, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Marc Haber <[email protected]> (supplier of updated sudo package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 26 Oct 2026 10:21:06 +0100
Source: sudo
Architecture: source
Version: 1.9.17p2-9exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Sudo Maintainers <[email protected]>
Changed-By: Marc Haber <[email protected]>
Closes: 1147179
Changes:
sudo (1.9.17p2-9exp1) experimental; urgency=medium
.
[ Mike Gabriel ]
* d/control: B-D on Dh-nss (>= 1.8~)
* d/sudo.nss: Authoritatively manage sudoers: entry in nsswitch.conf.
(Closes: #1147179)
Checksums-Sha1:
f00ab139b8f138ff24fc484e5b789bfb34bd8f7a 1980 sudo_1.9.17p2-9exp1.dsc
000dc2243686c68597710d2c6310a16110ba4b27 53516
sudo_1.9.17p2-9exp1.debian.tar.xz
116eaa9811d2582f5266901f04b055fe7061e51f 4923
sudo_1.9.17p2-9exp1_source.buildinfo
Checksums-Sha256:
bb1b40b5b602ad5784f40a20a07951cdbd3aebaee9b66c0be87942483c532948 1980
sudo_1.9.17p2-9exp1.dsc
6d0f94dc7aa3040153092454e70542a2d4c73f7a1f96d01a04ae76499b7be21e 53516
sudo_1.9.17p2-9exp1.debian.tar.xz
a0bfd994cb05ce23ed15fa24f14af56364d37ac95fb980cb0a210eff651dc5ed 4923
sudo_1.9.17p2-9exp1_source.buildinfo
Files:
ca4aa23dfa9a8eb29f1b3b162d16817a 1980 admin optional sudo_1.9.17p2-9exp1.dsc
bead2af5e07ab67f376dcce96a1e6597 53516 admin optional
sudo_1.9.17p2-9exp1.debian.tar.xz
18fee97c4dc0b6b60733e7a3dfea9005 4923 admin optional
sudo_1.9.17p2-9exp1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iJYEARYKAD4WIQRoUtdjQYCq5giMg+rVTTAMN2ORyQUCat8jryAcbWgrZGViaWFu
LXBhY2thZ2VzQHp1Z3NjaGx1cy5kZQAKCRDVTTAMN2ORyS8kAP9eoVU6aND93Ppk
qPMbTMxWfi2phNi8NgAAJI77QcJxIgEA8OHYih2pZ2PrX8Jaf18JxZxyNE1Joo1J
efBswc26tQ4=
=NKCa
-----END PGP SIGNATURE-----
pgp83aiWgkCHt.pgp
Description: PGP signature
--- End Message ---