SRU review 1. Is this bug that saslauthd doesn't work in Noble at all because the permissions are wrong? Or only in certain circumstances, and in which case, which ones?
2. Is it possible that somebody is successfully using saslauthd running as root, and changing the group of the service to sasl would break them? For example, what if they have saslauthd configured to read something else that is only readable by root? What about shadow? 3. Seems like this could do with verifying that saslauthd is working end-to-end in at least one scenario. See: "The Test Plan verifies a technical change but not the user story" as well as "Test Plan only covers the fix, and not general use of the package to make sure that it still works after the update" from https://canonical-sru- docs.readthedocs-hosted.com/en/latest/howto/common-issues/#test-plan 4. Can we add a dep8 test for saslauthd to both do the verification and also prevent regressions in the future? ** Changed in: cyrus-sasl2 (Ubuntu Noble) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078851 Title: saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2078851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
