This bug is a tracker for the FIPS-140 compliance in the Red Hat .NET Core packages. As of now, we've discussed internally with the following summary.
.NET Core calls out to OpenSSL for all but the following crypto algorithms.
Some work with Microsoft is needed here, as there has been discussions to move more implementations within the .NET framework.
Any update on this? The upstream issue  seems to also have gone silent, so let me know if there is anything needed from me to push this forward.
.NET Core 2.2 has gone EOL.
I am re-targeting the bug to the latest version, .NET Core 3.1.