<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><title>Stephen C Phillips (Posts about Security)</title><link>http://blog.scphillips.com/</link><description></description><atom:link type="application/rss+xml" href="http://blog.scphillips.com/categories/security.xml" rel="self"></atom:link><language>en</language><copyright>Contents © 2018 &lt;a href="mailto:steve@scphillips.com"&gt;Stephen C Phillips&lt;/a&gt; </copyright><lastBuildDate>Mon, 31 Dec 2018 11:41:08 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Intercepting HTTPS Traffic</title><link>http://blog.scphillips.com/posts/2017/04/intercept-https/</link><dc:creator>Stephen C Phillips</dc:creator><description>&lt;div&gt;&lt;p&gt;To &lt;a class="reference external" href="http://blog.scphillips.com/posts/2017/01/the-tado-api-v2/"&gt;document the Tado API&lt;/a&gt;, I needed to intercept the calls the mobile app was making to the server. As with many apps these days, the connection from the app to the server is encrypted using transport layer security (TLS) which makes it hard to read (that's the point!). It is still possible to intercept and read this sort of traffic with a man-in-the-middle attack though: this post discusses how to do it.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://blog.scphillips.com/posts/2017/04/intercept-https/"&gt;Read more…&lt;/a&gt; (18 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>Security</category><guid>http://blog.scphillips.com/posts/2017/04/intercept-https/</guid><pubDate>Wed, 12 Apr 2017 15:00:30 GMT</pubDate></item><item><title>Raspberry Pi System Logging and Loggly</title><link>http://blog.scphillips.com/posts/2015/05/raspberry-pi-system-logging-and-loggly/</link><dc:creator>Stephen C Phillips</dc:creator><description>&lt;div&gt;&lt;p&gt;I've already written about how useful Loggly is to log data from a Raspberry Pi, but like me, you may want to know more about how system logging actually works and what the extra configuration added by the Loggly setup script means.&lt;/p&gt;
&lt;p&gt;This post explains how system logging works and how Loggly fits into it. It describes how the log files are rotated to avoid them filling up the disc and it also goes into a lengthy detour regarding how to encrypt the log traffic between your computer and Loggly, how all the encryption actually works and how you know you can trust it.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://blog.scphillips.com/posts/2015/05/raspberry-pi-system-logging-and-loggly/"&gt;Read more…&lt;/a&gt; (20 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>Loggly</category><category>Raspberry Pi</category><category>Security</category><guid>http://blog.scphillips.com/posts/2015/05/raspberry-pi-system-logging-and-loggly/</guid><pubDate>Sun, 31 May 2015 13:15:19 GMT</pubDate></item></channel></rss>