Curiousness, not casual dismissal, is what's mentioned in the HN guidelines.
But since you ask, they do mention some of the reasons: - Apple’s Secure Enclave processor - Able to test the implementations against each other
But since you ask, they do mention some of the reasons: - Apple’s Secure Enclave processor - Able to test the implementations against each other
That's only referred to as something that is explicitly not supported.
> - Able to test the implementations against each other
Surely they could have done that anyway, since SC implements the CK API. Or they could have disabled the CK backend for all release builds.
—— original (incorrect) comment
It does not say Secure Enclave is not supported, it says this:
“ a subset of the API is built around using Apple’s Secure Enclave processor to securely store and compute on keying material. Apple’s Secure Enclave processor is not available on non-Apple hardware: as a result, Swift Crypto does not provide these APIs.”
So if secure enclave is available it specifically _is_ used to implement some functionality, but this is implements in other ways on other platforms. However the APIs for secure enclave itself are not exposed in either implementation.
It says nothing about whether any other SC APIs use the enclave behind the scenes (but I doubt it, there's not much point in bothering with the enclave if the CPU has access to the key material).