Replacing OpenSSL with native OSX Library

Question

In our existing application, which is tightly coupled with the OpenSSL, we would like to make use of an OSX native crypto library. Related to this I have following questions:

1. I believe OpenSSL does two jobs, one make the Transport layer secure, and the second to take care of sending & receiving data. While reading several blogs and documentation, I have come to the conclusion that I need to go with the CommonCrypto & NSStream, where CommonCrypto is used for Encryption & Decryption, and NSStream will be used to send & receive data. Please correct me if that sounds wrong.

2. Using NSStream seems to be non-blocking framework, while our existing application would benefit from a blocking mechanism. Is there any way around to this?

Answer 1

Thanks for looking at it,

Secure Transport Reference is the key to look into it...