<?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>ChrisAcheson.net &#187; encryption</title>
	<atom:link href="http://chrisacheson.net/blog/tag/encryption/feed/" rel="self" type="application/rss+xml" />
	<link>http://chrisacheson.net/blog</link>
	<description></description>
	<lastBuildDate>Fri, 30 Dec 2011 16:32:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>PGP: Migrating Away from SHA-1</title>
		<link>http://chrisacheson.net/blog/2009/05/09/pgp-migrating-away-from-sha-1/</link>
		<comments>http://chrisacheson.net/blog/2009/05/09/pgp-migrating-away-from-sha-1/#comments</comments>
		<pubDate>Sat, 09 May 2009 18:52:32 +0000</pubDate>
		<dc:creator>Chris Acheson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[pgp]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://chrisacheson.net/blog/?p=69</guid>
		<description><![CDATA[The SHA-1 hash that PGP and GnuPG use by default is now looking even less secure than previously thought. It&#8217;s recommended that users begin using SHA-2, and generate new keys to replace their 1024-bit DSA keys which are dependent on SHA-1: http://www.debian-administration.org/users/dkg/weblog/48 If you understand the instructions in the link above, you should probably follow [...]]]></description>
			<content:encoded><![CDATA[<p>The SHA-1 hash that PGP and GnuPG use by default is now looking even<br />
less secure than previously thought.  It&#8217;s recommended that users begin<br />
using SHA-2, and generate new keys to replace their 1024-bit DSA keys<br />
which are dependent on SHA-1:</p>
<p><a class="moz-txt-link-rfc2396E" href="http://www.debian-administration.org/users/dkg/weblog/48">http://www.debian-administration.org/users/dkg/weblog/48</a></p>
<p>If you understand the instructions in the link above, you should<br />
probably follow them soon.  If you don&#8217;t understand them, don&#8217;t worry<br />
too much, as your keys and signatures are still mostly safe for now,<br />
they&#8217;re just not future-proof.  You&#8217;ll probably want to wait until new<br />
versions of your software are released with updated default settings,<br />
and then generate new keys.</p>
<p>I&#8217;ve generated a <a href="http://chrisacheson.net/contact/">new key</a> for myself, which I&#8217;ve signed with the old key<br />
and will be using from now on.</p>
]]></content:encoded>
			<wfw:commentRss>http://chrisacheson.net/blog/2009/05/09/pgp-migrating-away-from-sha-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Firefox Portable + GnuPG + FireGPG = CryptoFox</title>
		<link>http://chrisacheson.net/blog/2009/05/05/firefox-portable-gnupg-firegpg-cryptofox/</link>
		<comments>http://chrisacheson.net/blog/2009/05/05/firefox-portable-gnupg-firegpg-cryptofox/#comments</comments>
		<pubDate>Tue, 05 May 2009 21:59:12 +0000</pubDate>
		<dc:creator>Chris Acheson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[pgp]]></category>

		<guid isPermaLink="false">http://chrisacheson.net/blog/?p=65</guid>
		<description><![CDATA[I&#8217;ve been talking about this for a while, but I finally got around to doing it.  I&#8217;ve put together a software package consisting of Firefox Portable, GNU Privacy Guard, and FireGPG.  I&#8217;m calling it &#8220;CryptoFox&#8221;.  You can download it here. The idea behind this is to lower the barrier to entry for using PGP encryption.  [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been talking about this for a while, but I finally got around to doing it.  I&#8217;ve put together a software package consisting of <a href="http://portableapps.com/apps/internet/firefox_portable">Firefox Portable</a>, <a href="http://gnupg.org/">GNU Privacy Guard</a>, and <a href="http://getfiregpg.org/">FireGPG</a>.  I&#8217;m calling it &#8220;CryptoFox&#8221;.  You can download it <strong><a href="http://chrisacheson.net/cryptofox/">here</a></strong>.</p>
<p>The idea behind this is to lower the barrier to entry for using PGP encryption.  If you want to communicate privately with someone, instead of having to guide them through the install process for 3 different components, you can just have them download CryptoFox and run it.  No installation is required.</p>
<p>It&#8217;s also a little tricky to set FireGPG and GnuPG up to function portably.  If you want to run them from a USB stick on any computer, I&#8217;ve already done the hard part for you.</p>
]]></content:encoded>
			<wfw:commentRss>http://chrisacheson.net/blog/2009/05/05/firefox-portable-gnupg-firegpg-cryptofox/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>PGP Keysigning Party at BarCampRochester4</title>
		<link>http://chrisacheson.net/blog/2009/03/26/pgp-keysigning-party-at-barcamprochester4/</link>
		<comments>http://chrisacheson.net/blog/2009/03/26/pgp-keysigning-party-at-barcamprochester4/#comments</comments>
		<pubDate>Thu, 26 Mar 2009 21:17:40 +0000</pubDate>
		<dc:creator>Chris Acheson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[barcamp]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[pgp]]></category>
		<category><![CDATA[rochester]]></category>

		<guid isPermaLink="false">http://chrisacheson.net/blog/?p=21</guid>
		<description><![CDATA[I&#8217;m organizing a PGP keysigning party at this year&#8217;s BarCamp Rochester.  For those of you who are unfamiliar with PGP, it&#8217;s a system for sending encrypted messages.  More information can be found in this guide.  The purpose of a keysigning party is to integrate yourself into and expand PGP&#8217;s web of trust, which prevents participants [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m organizing a PGP <a href="http://en.wikipedia.org/wiki/Key_signing_party">keysigning party</a> at this year&#8217;s <a href="http://barcamproc.org/">BarCamp Rochester</a>.  For those of you who are unfamiliar with PGP, it&#8217;s a system for sending encrypted messages.  More information can be found in <a href="http://radgeek.com/gt/2008/10/29/how_to/">this guide</a>.  The purpose of a keysigning party is to integrate yourself into and expand PGP&#8217;s <a href="http://en.wikipedia.org/wiki/Web_of_trust">web of trust</a>, which prevents participants from being tricked into addressing their messages to a clever eavesdropper rather than to their indended recipient.</p>
<p>BarCamp will take place on April 18th, on the third floor of the <a href="http://barcamproc.org/phase3/images/e/ec/Building70.png">GCCIS building (#70)</a> on <a href="http://www.rit.edu/">RIT</a> campus.  The keysigning party will happen at 2:00 PM.  If you&#8217;re interested in attending, you&#8217;ll need to do a little bit of preparation:</p>
<h4>Before the Party</h4>
<ol>
<li><a href="http://chrisacheson.net/contact/">Send me an email</a> to let me know you&#8217;ll be there.  This isn&#8217;t absolutely necessary, but I&#8217;d like to get a rough estimate of how big the party will be.  You&#8217;re also encouraged (though not strictly required) to <a href="http://barcamproc.org/">sign up for BarCamp</a> and give some kind of presentation.</li>
<li>If you don&#8217;t have one already, create a PGP keypair.</li>
<li>Print out slips of paper with your key&#8217;s fingerprint, along with your name and the email address associated with the key.  You should be able to fit several of these onto a single sheet of paper (18 if you lay them out <a href="http://chrisacheson.net/blog/wp-content/uploads/2009/03/keysigning_party_fingerprints_example.pdf">like so</a>).  As of this writing I don&#8217;t know what the turnout will be like, but I&#8217;m guessing one sheet will be enough.</li>
<li>Bring a pen and the slips of paper with you to the party.  Also bring identification, preferably two forms, at least one of which is a photo ID and one of which is government-issued.  Driver&#8217;s license, passport, etc.  Don&#8217;t bring a computer (or if you do, leave it powered off), you won&#8217;t need it.</li>
</ol>
<h4><span id="more-21"></span>During the Party</h4>
<p>The party will be run in a simple ad-hoc format.  You and each other participant will:</p>
<ol>
<li>Trade key fingerprints.  You give them one of your slips of paper, and they give you one of theirs.</li>
<li>Check identification.  Make sure that the photo on the ID matches the person, and that the name on the ID matches the name on their slip of paper.</li>
<li>If their ID checks out, and you&#8217;re comfortable asserting to the world that this person is who they say they are, write your initials on the slip of paper that they gave you.</li>
</ol>
<p>Once you&#8217;ve traded fingerprints with everyone, the formal part of the party is over.  If there&#8217;s time left, we can have an informal discussion (perhaps about promoting PGP use in Rochester?), or you can just head out.</p>
<h4>After the Party</h4>
<p>Once you get home, you&#8217;ll need to actually sign the keys of the party-goers.  For each slip of paper that you initialled:</p>
<ol>
<li>Acquire the corresponding key from the public key servers.  You can search by name, email address, or fingerprint.</li>
<li>Verify that the name, email address, and fingerprint of the key you&#8217;ve downloaded matches the name, email address, and fingerprint on the slip of paper you were given.</li>
<li>Using your PGP program, sign the key.</li>
<li>Export the signed key and send it in an encrypted email to the address listed on the key.  Don&#8217;t upload it back to the public key servers.  This ensures that the email address really does belong to the person who possesses the key.</li>
</ol>
<p>When you receive signatures from others, import them into your keyring and update your key on the public key servers.</p>
<p>That&#8217;s pretty much it.  If you have any questions, either <a href="http://chrisacheson.net/contact/">email me</a> or leave a comment here.</p>
]]></content:encoded>
			<wfw:commentRss>http://chrisacheson.net/blog/2009/03/26/pgp-keysigning-party-at-barcamprochester4/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

