Where can I find some simple sample code for public key encryption and decryption on Mac OS X? I’m frustrated that Apple’s “Certificate, Key, and Trust Services Programming Guide” shows how to do this stuff on iOS, but the needed APIs (SecKeyEncrypt, SecKeyDecrypt) are apparently not available on Mac OS X. There’s probably a way to do it in “CryptoSample”, but it doesn’t look clear or simple, and the sample project is too old to open with the current version of Xcode.
Where can I find some simple sample code for public key encryption and decryption
Share
The Security Framework APIs change rather frequently between Mac OS releases. The best approach depends on what version you target:
https://developer.apple.com/library/archive/documentation/Security/Conceptual/SecTransformPG/SecurityTransformsBasics/SecurityTransformsBasics.html
You’ll want to create a transform using
SecEncryptTransformCreateorSecDecryptTransformCreate, set its input usingSecTransformSetAttributeand execute it withSecTransformExecute.CryptoSample‘scdsaEncryptis a concise example.https://developer.apple.com/library/archive/samplecode/CryptoSample/Listings/libCdsaCrypt_libCdsaCrypt_cpp.html
You can get a
CSSM_CSP_HANDLEand aCSSM_KEYfrom a SecKeyRef by usingSecKeyGetCSPHandleandSecKeyGetCSSMKey, respectively.To learn more about CDSA, the full specification is available from the Open Group (free, but requires registration):
https://www2.opengroup.org/ogsys/jsp/publications/PublicationDetails.jsp?publicationid=11287
Good luck!
If the private key was created exportable, you can export it in an unprotected format and use openssl directly. This puts the raw key data directly in the address space of your application, so it defeats one of the primary purposes of the Keychain. Don’t do this.
Finally, you can mess around with private functions. Mac OS 10.6 and 10.7 include, but do not publicly declare,
SecKeyEncryptandSecKeyDecrypt, with the same arguments as on iOS. The quick’n’dirty solution is to simply declare and use them (weakly linked, with the usual caveats). This is probably a bad idea to do in code that you plan to distribute to others.