<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Luke Faraone &#187; security</title>
	<atom:link href="http://luke.faraone.cc/blog/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://luke.faraone.cc/blog</link>
	<description></description>
	<lastBuildDate>Fri, 25 Jun 2010 14:13:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Low-tech anti-surveillance tool for the OLPC XO-1</title>
		<link>http://luke.faraone.cc/blog/2010/02/low-tech-anti-surveillance-tool-for-the-olpc-xo-1/</link>
		<comments>http://luke.faraone.cc/blog/2010/02/low-tech-anti-surveillance-tool-for-the-olpc-xo-1/#comments</comments>
		<pubDate>Fri, 26 Feb 2010 04:26:24 +0000</pubDate>
		<dc:creator>luke</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[lowtech]]></category>
		<category><![CDATA[olpc]]></category>
		<category><![CDATA[paranoia]]></category>
		<category><![CDATA[sarcasm]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[sugar]]></category>
		<category><![CDATA[surveillance]]></category>

		<guid isPermaLink="false">http://luke.faraone.cc/blog/2010/02/low-tech-anti-surveillance-tool-for-the-olpc-xo-1/</guid>
		<description><![CDATA[After reading several articles about the alleged spying that was enabled by a Pennsylvania school district via its one-to-one MacBook, and seeing discussion on a variety of mailing lists, I&#8217;ve decided to implement my own zero-cost, no-hassle solution to the problem for the OLPC XO-1&#8216;s camera. This should be able to be adopted in deployments [...]]]></description>
			<content:encoded><![CDATA[<div style="float: right; margin-left: 10px; margin-bottom: 10px;">
<p><a title="photo sharing" href="http://www.flickr.com/photos/lfaraone/4386519014/"><img style="border: solid 2px #000000;" src="http://farm5.static.flickr.com/4052/4386519014_55ed834441_m.jpg" alt="" /></a></p>
</div>
<p>After reading <a href="http://www.washingtonpost.com/wp-dyn/content/article/2010/02/25/AR2010022502339.html">several</a> <a href="http://www.washingtonpost.com/wp-dyn/content/article/2010/02/19/AR2010021902004.html">articles</a> about the alleged spying that was enabled by a Pennsylvania school district via its one-to-one <a href="http://www.apple.com/macbook/">MacBook</a>, and seeing discussion on a variety of mailing lists, I&#8217;ve decided to implement my own zero-cost, no-hassle solution to the problem for the <a href="http://en.wikipedia.org/wiki/OLPC_XO-1">OLPC XO-1</a>&#8216;s camera.</p>
<p>This should be able to be adopted in <a href="http://wiki.laptop.org/go/Deployments">deployments</a> everywhere, by anyone with a piece of paper, or anything else they can slide through the plastic faceplate.</p>
<p>Just say no to fancy addons and factory-added &#8220;shutters&#8221; or &#8220;covers&#8221;, make your own!</p>
]]></content:encoded>
			<wfw:commentRss>http://luke.faraone.cc/blog/2010/02/low-tech-anti-surveillance-tool-for-the-olpc-xo-1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Personal Security: the Secret Question and Answer</title>
		<link>http://luke.faraone.cc/blog/2009/05/personal-security/</link>
		<comments>http://luke.faraone.cc/blog/2009/05/personal-security/#comments</comments>
		<pubDate>Fri, 15 May 2009 02:09:40 +0000</pubDate>
		<dc:creator>luke</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[exploit]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[social engineering]]></category>
		<category><![CDATA[sqa]]></category>

		<guid isPermaLink="false">http://luke.faraone.cc/?p=80</guid>
		<description><![CDATA[In this session, we&#8217;ll explore some parts of infosec which should be taught in primary school. We&#8217;re all too smart to use the same password on multiple sites, right? While most people, I included, cannot say &#8220;yes&#8221; to the first question (at least not for everything), that alone is not enough. This is because no [...]]]></description>
			<content:encoded><![CDATA[<p>In this session, we&#8217;ll explore some parts of infosec which should be taught in primary school.</p>
<p>We&#8217;re all too smart to use the same password on multiple sites, right?</p>
<p>While most people, I included, cannot say &#8220;yes&#8221; to the first question (at least not for everything), that alone is not enough. This is because no matter how secure your password is, be it 20 letters long with various dingbats and 中文 characters, there is a weak link in this system. Or rather, two:</p>
<p>Your <strong>email</strong> is an obvious vulnerability: if someone was able to gain access to that, it would be trivial to reset your password for Facebook, YouTube, Meebo, etc.</p>
<p>What if you have a strong email password, you ask? In that case, we get on to the heart of the matter (which is also the most relevant to all those social networking users out there): <strong>secret questions</strong>.</p>
<p>Secret Q&amp;As (SQAs) were initially a good idea: provide an alternative in case one has lost access to one&#8217;s email, or never set one in the first place. (as with Gmail or Yahoo) It presents an interesting problem, however: while the average netizine is unlikely to know the mother&#8217;s maiden name of <em><span>dogggzlover98382374@hotmai</span>l.com</em>, if even your name can be figured from your email address (or the attacker knows you personally), it is trivial to use sites such as Facebook and MySpace to find the answers to SQAs. A rather public example of this vulnerability can be seen when Sarah Palin&#8217;s email account <a title="http://gawker.com/5051193/sarah-palins-personal-emails" href="http://www.facebook.com/note_redirect.php?note_id=101379871952&amp;h=bfdd3b4b52c9ab4b5d79642173657b6f&amp;url=http%3A%2F%2Fgawker.com%2F5051193%2Fsarah-palins-personal-emails" target="_blank">was broken into</a> last summer: all of the information needed could be found out using public records.</p>
<p>An example of a possible attack against Facebook in particular:</p>
<ul>
<li>Gain access to someone&#8217;s profile by either friend-requesting outright them or by masquerading as someone they know (and don&#8217;t already despise)</li>
<li>Look for an email address on the profile or in wall posts.</li>
<li>Visit their email provider and reset their email password via the information in their profile.</li>
<li>Now reset their Facebook password. This will send an email to their address, which you already have access to.</li>
</ul>
<p>This works against any site that uses a email-loop, even if it is well designed to avoid common SQAs. Social networking sites, however, are particularly vulnerable because of the wealth of personal information one shares freely on them.</p>
<p>This is because, as they are part of your personal history and not transactional, SQAs are almost always the same between sites. So, if you&#8217;re truly concerned about your information security: use something random for your SQAs and store them in a safe place.</p>
]]></content:encoded>
			<wfw:commentRss>http://luke.faraone.cc/blog/2009/05/personal-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
