Would using /var/tmp a solution?
My long-term solution would to avoid copying files to a temporary
directory at all. Instead the files could be included into the initrd
from their original place.
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Low
** Changed in: initramfs-tools (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2053153
Title:
initramfs-tools broken by libpam-tmpdir and /tmp mounted with noexec
Status in initramfs-tools package in Ubuntu:
Triaged
Status in initramfs-tools package in Debian:
Fix Released
Bug description:
I would like to forward the bug that was reported against Debian
"certain update-initramfs actions broken on systems with' from
'cryptsetup-initramfs: cryptkeyctl script fails to discover
decrypt_keyctl even when present" [1] to upstream initramfs-tools,
which I think is here.
To reproduce this bug in Debian:
1) sudo apt install libpam-tmpdir
2) Mount /tmp with noexec.
This breaks the cryptkeyctl hook.
Could you fix initramfs-tools compatibility with libpam-tmpdir and
/tmp mounted with noexec please?
Is there some more appropriate temporary folder for update-initramfs
to use?
By comparison, dracut has no such issue.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062756
(Disclaimer: I am not affiliated with Debian and writing this on my
own imitative.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2053153/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
