Apple was deprecated by opensl some time ago, it is no longer part of the SDK, and the library itself does not ship with OS X from 10.11.
Link here
You did not mention what you use openssl for. The decision depends on your needs. If you must use openssl (for example, too much of your code depends on it), you need to get openssl yourself, compile with the loaded headers and include the library in the application distribution package. Cocoapods seems like a smart way to manage this if you don't want to do it manually.
Or modify your code to use other libraries that ship with OS X, such as Security Transforms or CommonCrypto .
UPDATE: Apple documentation seems a bit misleading (surprise!). Dynamic libraries for the older version of openssl (0.9.8) are still distributed since 10.11. Just checked a new installation of 10.11, and libcrypto and libssl still exist.
If thatβs enough (for example, you just use openssl to check the receipt in the App Store), you can go away with only the header files from the 10.10 SDK (download it from Apple using xcode 6.4) and compile the application using the headers only. You do not need the actual openssl binaries.
danielv
source share