<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Infosec on @ppmotskula</title>
    <link>https://peeterpaul.motskula.net:443/tags/infosec/</link>
    <description>Recent content in Infosec on @ppmotskula</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>et-ee</language>
    <managingEditor>peeterpaul@motskula.net (Peeter P. Mõtsküla)</managingEditor>
    <webMaster>peeterpaul@motskula.net (Peeter P. Mõtsküla)</webMaster>
    <lastBuildDate>Tue, 31 Jan 2012 00:00:00 +0000</lastBuildDate><atom:link href="https://peeterpaul.motskula.net:443/tags/infosec/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>encfs for the paranoid</title>
      <link>https://peeterpaul.motskula.net:443/2012/01/31/encfs-for-the-paranoid/</link>
      <pubDate>Tue, 31 Jan 2012 00:00:00 +0000</pubDate>
      <author>peeterpaul@motskula.net (Peeter P. Mõtsküla)</author>
      <guid>https://peeterpaul.motskula.net:443/2012/01/31/encfs-for-the-paranoid/</guid>
      
      <description>&lt;p&gt;&lt;strong&gt;&lt;a href=&#34;http://www.arg0.net/encfs&#34;&gt;EncFS&lt;/a&gt;&lt;/strong&gt; is a free (GPL) FUSE-based cryptographic filesystem that transparently encrypts files, using an arbitrary directory as storage for the encrypted files (&lt;a href=&#34;http://en.wikipedia.org/wiki/EncFS&#34;&gt;Wikipedia article&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;One of the good things about encfs is that it allows you to keep your encrypted directory backed up on a removable disk or remote server, without having to decrypt and re-encrypt the data. And if you exclude the configuration file (that contains the key, which, in turn, is encrypted with a passphrase of your choice) from the backup, then you don&amp;rsquo;t have to worry about whether someone else could get a look at your backups &amp;mdash; all they&amp;rsquo;d ever get is random gibberish.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Skype worm? Not!</title>
      <link>https://peeterpaul.motskula.net:443/2007/09/14/skype-worm-not/</link>
      <pubDate>Fri, 14 Sep 2007 00:00:00 +0000</pubDate>
      <author>peeterpaul@motskula.net (Peeter P. Mõtsküla)</author>
      <guid>https://peeterpaul.motskula.net:443/2007/09/14/skype-worm-not/</guid>
      
      <description>&lt;p&gt;This week kicked off with a bang. A worm had been unleashed into the &amp;rsquo;net, targeting the users of Skype for Windows. You can check out &lt;span style=&#34;font-weight: bold&#34;&gt;Villu Arak&lt;/span&gt;&amp;rsquo;s &lt;a href=&#34;http://heartbeat.skype.com/2007/09/the_worm_that_affects_skype_fo.html&#34;&gt;post&lt;/a&gt; in Skype&amp;rsquo;s Heartbeat blog to read more about the worm and how to protect yourself from similar attacks in future.&lt;/p&gt;
&lt;p&gt;&lt;span style=&#34;font-weight: bold&#34;&gt;Phil Wolff&lt;/span&gt; &lt;a href=&#34;http://skypejournal.com/blog/2007/09/how_the_skype_worms_work.html&#34;&gt;posted&lt;/a&gt; a nice, but oversimplified graphic explanation in Skype Journal:&lt;br&gt;
&lt;img src=&#34;http://farm2.static.flickr.com/1399/1361355027_9e2d29b497_o.jpg&#34; alt=&#34;&#34;&gt;&lt;br&gt;
Why is this oversimplified? Because this explanation fails to address probably the most important point given in Villu&amp;rsquo;s post:&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
