-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make DSACryptoServiceProvider set legal key sizes to most restrictive for platform #50192
Conversation
Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchforks Issue DetailsThe legal key sizes for DSA are more restrictive than on other platforms. Update cc @jkoritzinsky @steveisok @AaronRobinsonMSFT @bartonjs
|
{ | ||
key.KeySize = 576; | ||
} | ||
catch (CryptographicException) when (PlatformDetection.IsAndroid) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exception filters are problematic in AOT scenarios. I would move this check inside the catch block.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we AOT our tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we send all assemblies in a suite's publish directory, for example, to the AOT compiler.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh, TIL. Cool 😄.
The legal key sizes for DSA are more restrictive than on other platforms. Update
DSACryptoServiceProvider
to use the most restrictive sizes as the legal key sizes.cc @jkoritzinsky @steveisok @AaronRobinsonMSFT @bartonjs