I have two fixes related to this bug. here's the first fix.... Description: Fix uninitialized value warnings when parsing PAM profiles The parse_pam_profile function declares $fieldname without initializing it, then attempts to use it in continuation line processing (else block) without checking if it's defined. This causes Perl warnings when PAM profile files start with comments or blank lines before the first field definition. . Symptoms: Use of uninitialized value $fieldname in hash element at /usr/sbin/pam-auth-update line 733 Use of uninitialized value $fieldname in hash element at /usr/sbin/pam-auth-update line 734 Use of uninitialized value $fieldname in hash element at /usr/sbin/pam-auth-update line 737 . Trigger: Any PAM profile starting with: - Comment lines (e.g., # /usr/share/pam-configs/module) - Blank lines - Any content before first "Field: Value" definition . Impact: Cosmetic - warnings printed to stderr but functionality unaffected . Solution: Add defensive check to skip continuation lines until first field is defined.
** Patch added: "Fix uninitialized value warnings when parsing PAM profiles" https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2075508/+attachment/5987348/+files/01-fix-uninitialized-fieldname.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075508 Title: pam-auth-update should allow for comments in pam-configs profiles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2075508/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
