You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Swift packages that use CryptoKit's SecureEnclave module (if it is available) cannot compile against Crypto, since Crypto does not define this module. All SecureEnclave operations have to be conditionally compiled in this case.
Since SecureEnclave has runtime detection (SecureEnclave.isAvailable), a stub of the SecureEnclave API that returns false for isAvailable (and throws for all operations) on non-macOS platforms would remove the need for conditional compilation.
One annoyance is that some functions in this API also take LAContext and SecAccessControl parameters. These can be left out, or the structures would have to be stubbed out too.
Importance:
Better compatibility with CryptoKit.
The text was updated successfully, but these errors were encountered:
New API Proposal: SecureEnclave
Motivation:
Swift packages that use CryptoKit's SecureEnclave module (if it is available) cannot compile against Crypto, since Crypto does not define this module. All SecureEnclave operations have to be conditionally compiled in this case.
Since SecureEnclave has runtime detection (
SecureEnclave.isAvailable
), a stub of the SecureEnclave API that returnsfalse
for isAvailable (and throws for all operations) on non-macOS platforms would remove the need for conditional compilation.One annoyance is that some functions in this API also take
LAContext
andSecAccessControl
parameters. These can be left out, or the structures would have to be stubbed out too.Importance:
Better compatibility with CryptoKit.
The text was updated successfully, but these errors were encountered: