Security

See e.g. https://developer.apple.com/documentation/network/creating-a... where the logging output makes it clear BoringSSL is what is used. Or comments such as: https://github.com/apple-oss-distributions/Security/blob/rel... Unsurprisingly, given BoringSSL doesn't have a stable API (yet alone ABI), it isn't exposed as a system library.

> We also need to notarize the .app and the .dmg. Interestingly, you can only notarize .pkg, .dmg, and .app files (in .zips) — command-line tools can only be notarized if they’re embedded in one of the listed containers. I don't think this is true, actually. I've been notarizing command-line builds of unxip by shoving it in a zip and uploading it to notarytool for a while: https://github.com/saagarjha/unxip/blob/main/release.sh. (You will note, amusingly, that I am suffering from the same -parse-as-library bug as the author.) After this is done I just chuck the zip file and upload the binary directly to GitHub. If you download the file from your browser and chmod +x it, you can double click on it and it runs. Obviously you can skip the chmod +x step by sending people the zip (which preserves permissions inside of itself). Also, FWIW, Appl

Apple still regularly releases large portions of macOS. Confused about some poorly documented keychain behavior? Just look at the source, e.g., https://opensource.apple.com/source/Security/Security-59754.... https://github.com/apple-oss-distributions/Security/blob/Sec... Access to such source code is not nothing, and certainly seems more than just a marketing gimmick.