Closed rkttu closed 4 years ago
Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq Notify danmosemsft if you want to be subscribed.
Likely a mono issue?
I'm having an issue with ExportParameters(true) as well. It takes an extremely long time to return, and when it finally does return the private parameters aren't there. Only Exponent and Modulus are populated.
Blazor WebAssembly in .NET 5 does not support cryptography libraries. It will throw System.PlatformNotSupportedException: System.Security.Cryptography is not supported on Browser.
@davidfowl @mdh1418 Thanks for your comment. I understand that local cryptography in Blazor is a corner and rare use case. Also, it requires lots of computing resources. But I didn't find any notice or best practices about cryptographic API that does not support Blazor. This situation makes some confusion. If possible, even in the current version, this API should also throw the exception to prevent further trouble.
For those of you interested in this topic, there is one piece of information I found. I found an alternative implementation. It will be an alternative implementation of built-in local cryptography.
https://github.com/ebekker/FMRL/tree/master/BlazorX.WebCrypto
Describe the bug
I tested a code which relies on RSACryptoServiceProvider.ExportParameters function in Blazor WebAssembly, but it hangs after the function called.
To Reproduce
I tested the below code in the SDK 3.1.300 (3.1.4 release).
Further technical details
dotnet --info