-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[iOS/tvOS] Enable RSA operations #51098
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchforks Issue DetailsThere is a set of the native RSA encrypt/decrypt operations which were disabled on iOS/tvOS in #33970 since most of them depend on the types/methods from the security framework, which are mostly available on MacOSX and seem not to have ready-to-use analogs for iOS/tvOS. During the work for annotating any unavailable APIs as unsupported, all managed calls into those RSA operations lead to the analyzer warnings. I've tried to re-enable the native part but it seems to be more time consuming/requiring more experience in the security area so the plan is to add the warning suppressions for now.
|
@filipnavara Taking into account the recent changes you've made in #51620, can we close this issue as resolved? |
Yes. This can be closed now. |
There is a set of the native RSA encrypt/decrypt operations which were disabled on iOS/tvOS in #33970 since most of them depend on the types/methods from the security framework, which are mostly available on MacOSX and seem not to have ready-to-use analogs for iOS/tvOS.
During the work for annotating any unavailable APIs as unsupported, all managed calls into those RSA operations lead to the analyzer warnings. I've tried to re-enable the native part but it seems to be more time consuming/requiring more experience in the security area so the plan is to add the warning suppressions for now.
Part of #47910
@steveisok @akoeplinger
The text was updated successfully, but these errors were encountered: