I came by this bug and tried to update the states to better reflect the situation.
We still have the case that for Focal there was a regression due to updates. But also the problem that it is hard to see if we want to revert (no as it was security improvements) or how we could fix (is it actually feature add to become compatible) things. The update to the states show that for new releases e.g. Jammy all the fixes are in and in addition being a new releases it is kind of allowed to do new things differently. But at the same time that means there might be fixes existing by now that make the other components compatible to the new behavior - if those could be backported that would mitigate the issue. But OTOH as we know backporting features usually isn't done in SRUs. That evaluation will need time - Marc was assigned to this before for a revisit, and I have kept this assignment in my update. ** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865900 Title: apache 2.4.29-1ubuntu4.12 authentication with client certificate broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1865900/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
