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 `decrypt_keyctl` fails when the user-keyring(7) isn't attached to the 
calling process
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: cryptsetup-run
Version: 2:2.1.0-5
Severity: normal
File: /lib/cryptsetup/scripts/decrypt_keyctl

Dear Maintainer,

when configuring this encrypted machine running debian stable with keyscript
"decryt_keyctl", the invocation of "cryptdisks_start data{0,1}_crypt" when
logged in via ssh as normal user and "sudo -i" to root fails with the message:

| [....] Starting crypto disk...data0_crypt (starting)...Caching passphrase for 
data0_crypt:  *********************
| keyctl_set_timeout: Permission denied
| Error setting timeout on key (824927206), removing
| Nothing to read on input.
| Caching passphrase for data0_crypt:

After some searching, I found a link to bug #758788, especially message #45 and 
#50 [1], which
described seemingly the same bug:

| > 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:
|
| Interesting, never saw these kind of problems before. I'm testing on a
| Laptop with Ubuntu 14.04 installed and use 'sudo -i' a lot. Indeed I
| used it for testing the commands above as well. For me it worked. But
| let's keep that aside. It's another issue and out of scope for this
| bugreport ;)

But I haven't found another link to that aspect of that bug; the mentioned
bug was closed without looking at that facette further.

Another link I stumbled upon was one of Matthew Gerret describing a workaround
with the kernel keyring and sudo [2].

I adapted a copy of decrypt_keyctl to his suggestions and afterwards I could
decrypt the multiple cryptdisks. Here is the patch:

--- 8< --- 8< --- 8< ---

--- decrypt_keyctl      2019-06-10 14:51:15.000000000 +0200
+++ decrypt_keyctl_debug        2019-09-03 23:33:51.311240116 +0200
@@ -43,8 +43,13 @@
         keyctl unlink "$KID_" @u
         KID_=""
     fi
-    KID_="$(printf "%s" "$KEY_" | keyctl padd user "$ID_" @u)"
+    KID_="$(printf "%s" "$KEY_" | keyctl padd user "$ID_" @s)"
     [ -n "$KID_" ] || die "Error adding passphrase to kernel keyring"
+    if ! ( keyctl setperm "$KID_" 0x3f3f0000 && keyctl link "$KID_" @u && keyctl unlink 
"$KID_" @s ); then
+        keyctl unlink "$KID_" @u
+        keyctl unlink "$KID_" @s
+        die "Error transferring permissions on key ($KID_), removing"
+    fi
     if ! keyctl timeout "$KID_" "$TIMEOUT_"; then
         keyctl unlink "$KID_" @u
         die "Error setting timeout on key ($KID_), removing"

--- 8< --- 8< --- 8< ---

I don't know whether there are further security implications or something like 
that,
nor did I do extensive testing. The error handling was also added in a quick way
without testing it further (I also don't know how to provoke that error). I just
wanted to let you know that and how I fixed a problem not only I had.


Regards

Sebastian

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758788#50
[2]: https://mjg59.dreamwidth.org/37333.html

--- 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-----

Attachment: pgp73pe2naPW_.pgp
Description: PGP signature


--- End Message ---

Reply via email to