This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients gregory.p.smith, ned.deily, ronaldoussoren
Date 2022-03-26.00:48:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1648255710.38.0.570771334735.issue47124@roundup.psfhosted.org>
In-reply-to
Content
https://developer.apple.com/documentation/cryptokit/ in macOS 10.15+

This is a common place for platform specific hardware acceleration to be exposed to the user (especially on SoCs which often have non-standard hardware - Like Apples... which is presumably why they create this).

What they offer is limited, but when present and running on a recent enough macOS, using their and SHA2 and HMAC(SHA2) implementations as well as Insecure.SHA1 is probably better than OpenSSL's.  **Verify this.** It'd also allow those to be fast in a non-openssl build (as if anyone does those).

I know little about mac building and packaging and how to have something target an older OS and use a 10.15+ API. So if this winds up only being used from aarch64 macOS builds (10.15+ by definition IIRC?) that could also work.

I leave this issue for a macOS Apple API friendly person to take on.

This issue is cousin to the Linux one: https://bugs.python.org/issue47102
History
Date User Action Args
2022-03-26 00:48:30gregory.p.smithsetrecipients: + gregory.p.smith, ronaldoussoren, ned.deily
2022-03-26 00:48:30gregory.p.smithsetmessageid: <1648255710.38.0.570771334735.issue47124@roundup.psfhosted.org>
2022-03-26 00:48:30gregory.p.smithlinkissue47124 messages
2022-03-26 00:48:30gregory.p.smithcreate