On 2020-12-29 07:47:11 +0100, Sven Joachim wrote: > There is already code in the libpam0g postinst script to restart them, > but it is only triggered on upgrades from versions older than 1.3.1-2, > which is apparently not enough.
Yes, in the case of cron, the daemon is linked against /lib/x86_64-linux-gnu/libpam.so.0 (thus the file before the PAM upgrade) and tries to open pam_unix.so later via dlopen (thus the file after the PAM upgrade). I suppose that libpam.so.0 and pam_unix.so must come from the same PAM version, so a restart of the cron service is necessary. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
