> The fix does not address the root trigger (FIPS provider loading failure in sc_openssl3_init); that is a separate issue handled elsewhere.
What's the user story that you're proposing to fix in this SRU then please, if FIPS provider loading is still expected to fail anyway even after this patch is applied to the archive? Or have I misunderstood? It sounds like you need to fix at least two different things, only one of which you're proposing to fix here. That's fine, but then we should be verifying both things together, to ensure that we are fixing what is actually needed. See https://documentation.ubuntu.com/project/SRU/howto/common-issues/#test- plan "Test Plan only covers the fix, and not general use of the package" and "The Test Plan verifies a technical change but not the user story". What I'm expecting is the *entire* user story to be validated, not just something that doesn't crash in a specific non-default configuration. What's the purpose of this specific non-default configuration, and how are you validating that it works all the way to the end? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2147395 Title: [SRU] opensc-pkcs11 (0.25.0~rc1-1ubuntu0.2) SIGSEGV in sc_release_context during PKCS#11 C_Initialize via p11-kit/NSS (Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/2147395/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
