title: Replacing OpenSSL with native OSX Library
body: <p>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:</p>
  
  <ol>
  <li><p>I believe OpenSSL does two jobs, one make the Transport layer secure, and the second to take care of sending &amp; receiving data. While reading several blogs and documentation, I have come to the conclusion that I need to go with the CommonCrypto &amp; NSStream, where CommonCrypto is used for Encryption &amp; Decryption, and NSStream will be used to send &amp; receive data. Please correct me if that sounds wrong.</p></li>
  <li><p>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? </p></li>
  </ol>