You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a followup to a PR I made regarding this issue, and I'd like to hear some comment.
In Gentoo's OpenRC (very close to upstream), pam_start(3) is called after chroot(2), so the process is unable to find the files required for PAM, as you can see on this strace output with unmodified start-stop-daemon: http://of.sijanec.eu/krneki/strace.txt
With a modified start-stop-daemon, chroot is correctly executed after pam_start and services utilizing --chroot option work.
On current release, --chroot is broken unless PAM files are mounted in the chroot, which might even be a security issue.
vapier
changed the title
pam_start should not be called from inside chroot in start-stop-daemon
start-stop-daemon: pam_start should not be called from inside chroot
Jan 15, 2023
This is a followup to a PR I made regarding this issue, and I'd like to hear some comment.
In Gentoo's OpenRC (very close to upstream), pam_start(3) is called after chroot(2), so the process is unable to find the files required for PAM, as you can see on this strace output with unmodified start-stop-daemon: http://of.sijanec.eu/krneki/strace.txt
With a modified start-stop-daemon, chroot is correctly executed after pam_start and services utilizing --chroot option work.
On current release,
--chroot
is broken unless PAM files are mounted in the chroot, which might even be a security issue.Related PR is #517, #517
The text was updated successfully, but these errors were encountered: