title: Setting up TrustKit
body: <p>I am working on an application that quickly needs to include <code>https</code> for network communication. Our concern over this came about when we noticed we are sending all of our user credentials over the <code>URL</code>. This isn't good because then our usernames and passwords are out there in the open. After a lot of research it seems that pinning the public key of the server's SSL certificate is the way to go. I have decided to use <code>TrustKit</code> to pin the public key of the certificate so we do not have to pin the entire certificate in the application. That way we do not have to keep replacing the certificate overtime it expires, thus not having to build a new IPA or submit to Apple. In order to get this up and running, I need a few questions answered.</p>
  
  <p>So I understand there are three main things I need to get started with <code>TrustKit</code>.</p>
  
  <p><strong>1.</strong> I need to know the <strong>domains</strong> that we are going to be using and include them in our info.plist.</p>
  
  <ul>
  <li><strong>QUESTION</strong>: Does the server at this domain need to do any preparation in order to get <code>TrustKit</code> what it needs to handle everything?</li>
  </ul>
  
  <p><strong>2.</strong> I need 2 public key <strong>hashes</strong> that also need to be included in the info.plist.</p>
  
  <ul>
  <li><strong>QUESTION</strong>: How do I extract the public key hashes from the certificate? From where do I get these hashes?</li>
  </ul>
  
  <p><strong>3.</strong> I need to know what public key <strong>algorithm</strong> to use.</p>
  
  <ul>
  <li><strong>QUESTION</strong>: What is this? And how do I find out which one to use?</li>
  </ul>
  
  <hr>
  
  <p>Once all of this is in place, is there anything else I need to do appwise to be able to make sure <code>TrustKit</code> does it's job longterm?</p>