There isn't a plan completely laid out for backporting this. It can be done but as you can see here, it's a very minimal change and it barely passes the criteria for backporting. This means it absolutely must be staged so that it's picked up by a subsequent security update rather than being a standalone update (openssl is installed everywhere so changing the package affects everybody, it's high-impact).
With that said, it's also a change that sits in a weird spot: once you've understood the issue, then you probably don't need the warning anymore and search engines should help find it now. Can you explain your need a bit so I can better gauge the need? Did you encounter the issue or are you rather trying to make sure you don't? BTW, with plucky being released soon, you'll start seeing the effect of the change if the container you run is on plucky. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066990 Title: openssl fails with out of memory messages while trying to load the FIPS provider in a non-FIPS container on a FIPS host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2066990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
