-
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] X509KeyStorageFlags in X509Certificate constructor are ignored #52434
Comments
Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchforks Issue DetailsThe implementation of PKCS#12 certificate loading ignores the flags passed to the constructor. It always imports the key as ephemeral even if asked to persist it which is easy to fix. The exportable flag is also ignored. It has to be investigated how it should map on iOS. It may control storing keys in the secure enclave. The keychain is per-application storage which greatly reduces the security risk of non-exportable keys actually being exportable.
|
I might be missing something, but is this resolved by #55425? Line 40 in 6874ef2
Line 56 in 6874ef2
I'm not very familiar, what is the exportable flag? |
On iOS we need to do the appropriate equivalent things. EphemeralKeySet works on iOS, but PersistKeySet and Exportable might need specific support. macOS version: Lines 45 to 53 in 57bfe47
|
The implementation of PKCS#12 certificate loading ignores the flags passed to the constructor. It always imports the key as ephemeral even if asked to persist it which is easy to fix.
The exportable flag is also ignored. It has to be investigated how it should map on iOS. It may control storing keys in the secure enclave. The keychain is per-application storage which greatly reduces the security risk of non-exportable keys actually being exportable.
The text was updated successfully, but these errors were encountered: