That common-session is intended only for interactive sessions. * After reading pam-auth-update source, I agree with Lucas Nussbaum * Register md5sum for new common-password template, Closes: #982898 * Handle services with systemd units but no init scripts, Closes: #982295 * Check for any user-added references to pam_tally and halt the upgrade, Once the new pam-auth-update is installed * Also, fail to permit profiles to be selected that include pam_tally * Remove profiles containing pam_tally or pam_tally2 since we no longer * Clearly it's been too long since I've done debconf runĭebconf-updatepo so the translations will show up as needing Fix capitalization of pam_Tally in debconf description The profile check willĬatch this unless the user has overwridden the configuration etc/pam.d/common-* for uses of pam_tally. Include '-' in the file matching regexp so we search * Code review fixes to the fix for #982530, thanks Martin Schurz Remove dead code setting idl when not used Actually set service to $1 rather than happening to use a variable * Code review fixes for the fix to #982295, thanks Mark Hindley * Updated German Debconf translations, Thanks Sven Joachim * Updated Dutch debconf templates, Thanks Frans Spiesschaert, Closes: * Updated russian Debconf translations, thanks Алексей Шилин, Closes: * French Debconf translations, thanks Jean-Pierre Giraud, Closes: * Updated Brazilian Portuguese translation, Thanks Adriano Rafael Gomes, * Updated Catalan translation, thanks Alex Muntada, Closes: #984568 * Updated translation from the Slovak team, thanks Ladislav Michnovič, * Updated Bulgarian Translation, Thanks Damyan Ivanov * Updated Simplified Chinese Translations, thanks Boyuan Yang * Updated portuguese debconf translation, thanks Pedro Ribeiro, Closes: When multiarch modules are available we use them. Working in bullseye will continue to work and also guarantees that That's different than buster, but guarantees everything already * Prefer the multiarch path (_PAM_ISA) to the non-multiarch path. Fix regression introduced in 1.4.0-1: search both /lib/security and * debian/patches-applied/lib_security_multiarch_compat lib/security will shadow one in the multiarch path. Shortly after releasing 1.4.0-8 that a valid shared object in Invalid shared object in /lib/security and confirmed it did not shadowĪn object in /lib/x86_64-linux-gnu/security. * I did test this in 1.4.0-8, but my test design was flawed. The effect of 1.4.0-9 is what is stated in theġ.4.0-8 changelog: we prefer multiarch paths, but the original patch Patches-applied/lib_security_multiarch_compat more closely I would * Revert prefer the multiarch path from 1.4.0-8: It turns out thatĭebian uses DEFAULT_MODULE_PATH and _PAM_ISA in the opposite meaning * Fix syntax error in libpam0g.postinst when a systemd unit fails, Pam (1.4.0-9+deb11u1) bullseye urgency=medium * Remove redundant pam_umask_usergroups_from_ Pam (1.4.0-9+deb11u1pexip1) pexip urgency=medium
0 Comments
Leave a Reply. |