Your message dated Wed, 04 Nov 2026 17:42:09 +0000
with message-id <[email protected]>
and subject line Bug#906752: fixed in sudo 1.9.17p2-11
has caused the Debian Bug report #906752,
regarding sudo: /etc/pam.d/sudo doesn't create a new keyring session
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.)
--
906752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906752
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sudo
Version: 1.8.19p1-2.1
Severity: normal
X-Debbugs-CC: Luc Maisonobe <[email protected]>
X-Debbugs-CC: Jonas Meurer <[email protected]>
Dear Maintainer,
sudo's pam config doesn't create a new keyring session for the processes
it spawns. This leads to problems with programs that try to add things
to the keyring, because they try to modify the user's keyring, which
even root doesn't have permission to do. An example of this was
mentioned in this previous bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758788#45
> On the first invocation (for cont1_crypt), I got this dialog:
>
> root@marislae:~# cryptdisks_start cont1_crypt
> [[....] Starting crypto disk...[info] cont1_crypt (starting)...
> Caching passphrase for /cont1: ******
> keyctl_set_timeout: Permission denied
> Error setting timeout on key (2524288), removing
> Caching passphrase for /cont1: ******
> keyctl_set_timeout: Permission denied
> Error setting timeout on key (612589418), removing
>
> [Here I pressed <ctrl-C> to stop the attempts]
>
> Caching passphrase for /cont1: Erreur de lecture de la phrase secrète.
>
>
> I was running the commands from root. I initially logged in to the
> computer from SSH to a regular user, than did "sudo -i" to get root
> access if this matters. As I suspected this may be a problem, I allowed
> root direct SSH access and tried again, login directly to root account,
> this time it worked:
>
> root@marislae:~# cryptdisks_start cont1_crypt
> [....] Starting crypto disk...[info] cont1_crypt (starting)...
> Caching passphrase for /cont1: ******
> [ ok _crypt (started)...done.
> root@marislae:~# cryptdisks_start cont2_crypt
> [....] Starting crypto disk...[info] cont2_crypt (starting)...
> Using cached passphrase for /cont2.
> [ ok _crypt (started)...done.
It turns out that this works when logged in as root via SSH because this
line in `/etc/pam.d/sshd` sets up a new session keyring for the root
user:
> # Create a new session keyring.
> session optional pam_keyinit.so force revoke
The same line is also present in `/etc/pam.d/runuser-l`, so I've been
working around this problem by running cryptdisks_start via `sudo
runuser -l`, as in:
> sudo runuser -l root -c 'cryptdisks_start c1 && cryptdisks_start c2 && #
so on'
Given that it's not useful for a process running on the root user to try to
manipulate the user's session keyring, I think it would make sense for
/etc/pam.d/sudo to force the creation of a new one, or at least for `sudo
-i` to force the creation of a new one via a `/etc/pam.d/sudo-i` config
file, similar to `runuser -l`.
Thanks,
Simon
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (102, 'testing'),
(101, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-7-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages sudo depends on:
ii libaudit1 1:2.6.7-2
ii libc6 2.27-5
ii libpam-modules 1.1.8-3.6
ii libpam0g 1.1.8-3.6
ii libselinux1 2.6-3+b3
ii lsb-base 9.20161125
sudo recommends no packages.
sudo suggests no packages.
-- Configuration Files:
/etc/sudoers [Errno 13] Permission denied: '/etc/sudoers'
/etc/sudoers.d/README [Errno 13] Permission denied: '/etc/sudoers.d/README'
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sudo
Source-Version: 1.9.17p2-11
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: Wed, 04 Nov 2026 17:37:02 +0100
Source: sudo
Architecture: source
Version: 1.9.17p2-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Sudo Maintainers <[email protected]>
Changed-By: Marc Haber <[email protected]>
Closes: 906752 939357 1147179
Changes:
sudo (1.9.17p2-11) unstable; urgency=medium
.
* really upload to unstable
.
sudo (1.9.17p2-10) experimental; urgency=medium
.
* upload to unstable
.
sudo (1.9.17p2-9exp2) experimental; urgency=medium
.
* add pam_keyinit to pam.d snippets.
Thanks to Simon Ruggier <[email protected]>, Sebastian Mohr
<[email protected]>, Guilhem Moulin <[email protected]>
(Closes: #906752, #939357)
.
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:
a5f319cb5eeb5139d4a91c000d6d3b766426ce45 1968 sudo_1.9.17p2-11.dsc
c691decc459a617b9939f316238d7137c3f38840 53692 sudo_1.9.17p2-11.debian.tar.xz
d85fb93eaddb10130bdb6175dd134e684f021a8d 5225 sudo_1.9.17p2-11_source.buildinfo
Checksums-Sha256:
147a4b3e8528a90233efc30c2a2758900a8dfa1939b0e29a06ad3eb18ce3e444 1968
sudo_1.9.17p2-11.dsc
c22fa6e7b17511ff57f2d995eeb3f9bdfd3358aba0b457c3d82a692d84e9d70b 53692
sudo_1.9.17p2-11.debian.tar.xz
f2f5e1b865965aea484f541afc82ba43a632d74cbbcb069c4a8143f305dbee9c 5225
sudo_1.9.17p2-11_source.buildinfo
Files:
a703d53bae38ac9b437f90b3e6cf7e98 1968 admin optional sudo_1.9.17p2-11.dsc
06a66db53f05e51e5896728bc60a23a2 53692 admin optional
sudo_1.9.17p2-11.debian.tar.xz
cc2204fda1a7a09ecdf80879b8206122 5225 admin optional
sudo_1.9.17p2-11_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iJYEARYKAD4WIQRoUtdjQYCq5giMg+rVTTAMN2ORyQUCauto7SAcbWgrZGViaWFu
LXBhY2thZ2VzQHp1Z3NjaGx1cy5kZQAKCRDVTTAMN2ORyWGDAQCGwOqHvpEVrCBa
uEjvp4Db6zks8Z+1ilLuCUH6asm3YAD/X3PNmzq9o9YmZo47p3RThzedY7f6otCt
HXXfN5qdaQ8=
=fGrV
-----END PGP SIGNATURE-----
pgpo21k1lYK3e.pgp
Description: PGP signature
--- End Message ---