<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>crl on Madison&#39;s Blog</title>
    <link>https://solarana.dev/tags/crl/</link>
    <description>Recent content in crl on Madison&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 05 Jan 2021 12:00:00 -0600</lastBuildDate><atom:link href="https://solarana.dev/tags/crl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Enforcing Certificate Revocation</title>
      <link>https://solarana.dev/2021/01/05/enforcing-certificate-revocation/</link>
      <pubDate>Tue, 05 Jan 2021 12:00:00 -0600</pubDate>
      
      <guid>https://solarana.dev/2021/01/05/enforcing-certificate-revocation/</guid>
      <description>In addition to TLS Pinning, you can also enforce that the certificate in use has not been revoked by checking the CRL or OCSP result for said certificate. To do this for NSURLSession, you need to add an additional SecPolicyRef to the SecTrustRef provided to you during the authentication challenge. The new policy needs to be created via SecPolicyCreateRevocation and can be tweaked depending on how strict you want to be.</description>
    </item>
    
  </channel>
</rss>
