<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Communications on Hexploitable</title>
    <link>https://hexplo.it/tags/communications/</link>
    <description>Recent content in Communications on Hexploitable</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 10 Aug 2016 13:54:40 +0000</lastBuildDate>
    <atom:link href="https://hexplo.it/tags/communications/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Brace yourselves: ATS is coming</title>
      <link>https://hexplo.it/post/ats-enforcement/</link>
      <pubDate>Wed, 10 Aug 2016 13:54:40 +0000</pubDate>
      <guid>https://hexplo.it/post/ats-enforcement/</guid>
      <description>&lt;h2 id=&#34;application-transport-security&#34;&gt;Application Transport Security&lt;/h2&gt;&#xA;&lt;p&gt;Since HTTP is a plaintext protocol and therefore creates inherent security and privacy concerns when used by applications - Apple has decided that it is finally time to start treating the secure alternative, HTTPS, as the de facto web protocol for iOS mobile apps. At WWDC this year, Apple rightly pointed out that simply &amp;ldquo;enabling&amp;rdquo; HTTPS does not necessarily mean that you are secure. There are many ways in which HTTPS can be improperly configured resulting in the use of insecure connections.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
