<?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>This Blog Is Not For Reading &#187; privacy</title>
	<atom:link href="http://bob.jonkman.ca/blogs/category/privacy/feed/" rel="self" type="application/rss+xml" />
	<link>http://bob.jonkman.ca/blogs</link>
	<description>A blog, just like any blog, only more so</description>
	<lastBuildDate>Sun, 05 Feb 2012 21:59:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>How to hold a Key Signing Party</title>
		<link>http://bob.jonkman.ca/blogs/2011/10/14/how-to-hold-a-key-signing-party/</link>
		<comments>http://bob.jonkman.ca/blogs/2011/10/14/how-to-hold-a-key-signing-party/#comments</comments>
		<pubDate>Fri, 14 Oct 2011 04:01:19 +0000</pubDate>
		<dc:creator>Bob Jonkman</dc:creator>
				<category><![CDATA[PGP/GPG]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[certificate authority]]></category>
		<category><![CDATA[gpg]]></category>
		<category><![CDATA[key]]></category>
		<category><![CDATA[keysigning]]></category>
		<category><![CDATA[keysigning party]]></category>
		<category><![CDATA[man in the middle]]></category>
		<category><![CDATA[party]]></category>
		<category><![CDATA[pgp]]></category>
		<category><![CDATA[PKI]]></category>
		<category><![CDATA[public key infrastructure]]></category>
		<category><![CDATA[signature]]></category>
		<category><![CDATA[signing]]></category>
		<category><![CDATA[trust]]></category>
		<category><![CDATA[web of trust]]></category>

		<guid isPermaLink="false">http://bob.jonkman.ca/blogs/?p=450</guid>
		<description><![CDATA[While planning a Keysigning Party, the organizer suggested that among the things to bring: Some ID would also be a good idea, for those who do not already know you. No no no. If people don&#8217;t know you, then they shouldn&#8217;t be signing your key. If you don&#8217;t know someone, then you shouldn&#8217;t be signing [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_459" class="wp-caption alignright" style="width: 310px"><a href="http://bob.jonkman.ca/blogs/2011/10/14/how-to-hold-a-key-signing-party/key-by-quasimondo/" rel="attachment wp-att-459"><img src="http://bob.jonkman.ca/blogs/files/2011/09/Key-by-Quasimondo-300x225.jpg" alt="Key in lock" title="Key" width="300" height="225" class="size-medium wp-image-459" /></a><p class="wp-caption-text">Key by Quasimondo</p></div>While planning a Keysigning Party, the organizer suggested that among the things to bring:</p>
<blockquote><p>
Some ID would also be a good idea, for those who do not already know you.
</p></blockquote>
<p>No no no.</p>
<p>If people don&#8217;t know you, then they shouldn&#8217;t be signing your key.  If you don&#8217;t know someone, then you shouldn&#8217;t be signing their key.</p>
<p>Using ID of any sort is assigning trust by proxy to an &#8220;authority&#8221;.  You&#8217;re no longer vouching for a person based on your own knowledge, but relying on the &#8220;authority&#8221; to provide that trust.  If you&#8217;re going to rely on third-party authorities you might as well revert to a hierarchical <abbr title="Public Key Infrastructure">PKI</abbr> and pay lots of money to a certificate authority to assign levels of trust for you.</p>
<p>The point of the keysigning is to associate a key value with a real person, with no opportunity for a Man in the Middle attack <sup><a href="#footnote1" id="ref1" title="Footnote 1">[1]</a></sup>.  It is not to verify name, address and permission to drive in Ontario.</p>
<p>When I sign your key it is not because the government says that you&#8217;re allowed to drive under your name, but I sign your key because I believe that you&#8217;re the same guy who drinks Jagermeister and hacks on Blackberries and hangs out at the Syrup Festival.  It is based on my personal knowledge of you, and my trust in your claim that you own the GPG key with fingerprint D2CCE5EA <sup><a href="#footnote2" id="ref2" title="Footnote 2">[2]</a></sup>.</p>
<p>The Web of Trust extends this, so that since I trust your identity and judgment, I&#8217;m also likely to grant some level of trust to the people you trust.  After a successful keysigning party then I&#8217;m going to trust many more people because they&#8217;re all trusted by people I trust.  And I&#8217;ll be trusted by more people, because they trust the people who have signed my key.</p>
<p>So, how <strong>do</strong> you hold a keysigning party? Here&#8217;s an excerpt from the <a href="http://www.pgp.net/pgpnet/pgp-faq/" title="The comp.security.pgp FAQ">PGP FAQ</a>:</p>
<blockquote cite="http://www.pgp.net/pgpnet/pgp-faq/">
<h3 class="TITLE">The comp.security.pgp FAQ</a></h3>
<h4 class="AUTHOR">Wouter Slegers</h4>
<p class="COPYRIGHT">Copyright &copy; 1996, 1997, 1998, 1999, 2000,<br />
2001 by Arnoud Engelfriet</p>
<p class="COPYRIGHT">Copyright &copy; 2002 by Wouter Slegers</p>
<div class="LEGALNOTICE">
<p>This FAQ is copyright &copy; 2001 by Wouter Slegers.</p>
<p>It may be distributed freely in online electronic form, provided the copyright notice is left intact. Since this FAQ is always available from USENET and <a href="http://www.pgp.net/pgpnet/" title="Top Level page for www.pgp.net at cam.ac.uk.pgp.net [08040909]">the PGP network</a>, there should be no problems getting access to it. However mirrors with outdated versions can confuse the users, so I request you not to mirror this FAQ elsewhere.</p>
<p>[...]
<div class="QANDAENTRY">
<div class="QUESTION">
<p><big><b>Q: What&#8217;s a key signing party?</b></big></p>
</div>
<div class="ANSWER">
<p><b>A:</b> A key signing party is a get-together with various other users of PGP for the purpose of meeting and signing keys. This helps to extend the <i class="GLOSSTERM">web of trust</i> to a great degree, making it easier for you to find one or more trusted paths to someone whose public key you didn&#8217;t have.</p>
<p>Kevin Herron has an <a href="http://www.herrons.com/kb2nsx/keysign.html" title="Keysigning Party Guide | Radio Amateur W4KWH">example of a keysigning party announcement page</a> <a href="#footnote3" title="Footnote 3" id="ref3"><sup>[3]</sup></a>.</p>
</div>
</div>
<div class="QANDAENTRY">
<div class="QUESTION">
<p><big><b>Q: How do I organize a key signing party?</b></big></p>
</div>
<div class="ANSWER">
<p><b>A:</b> Though the idea is simple, actually doing it is a bit complex, because you don&#8217;t want to compromise other people&#8217;s private keys or spread viruses (which is a risk whenever floppies are swapped willy-nilly). Usually, these parties involve meeting everyone at the party, verifying their identity and getting key fingerprints from them, and signing their key at home.</p>
<p>Derek Atkins has recommended this method:</p>
<p>There are many ways to hold a key-signing session. Many viable suggestions have been given. And, just to add more signal to this newsgroup, I will suggest another one which seems to work very well and also solves the N-squared problem of distributing and signing keys. Here is the process:</p>
<ol type="1">
<li>
<p>You announce the keysigning session, and ask everyone who plans to come to send you (or some single person who <span class="emphasis"><i class="EMPHASIS">will</i></span> be there) their public key. The RSVP also allows for a count of the number of people for step 3.</p>
</li>
<li>
<p>You compile the public keys into a single keyring, run <tt class="USERINPUT"><b>pgp -kvc</b></tt> on that keyring, and save the output to a file.</p>
</li>
<li>
<p>Print out N copies of the <tt class="USERINPUT"><b>pgp -kvc</b></tt> file onto hardcopy, and bring this and the keyring on media to the meeting.</p>
</li>
<li>
<p>At the meeting, distribute the printouts, and provide a site to retrieve the keyring (an ftp site works, or you can make floppy copies, or whatever &#8212; it doesn&#8217;t matter).</p>
</li>
<li>
<p>When you are all in the room, each person stands up, and people vouch for this person (e.g., &#8220;Yes, this really is Derek Atkins &#8212; I went to school with him for 6 years, and lived with him for 2&#8243;).</p>
</li>
<li>
<p>Each person securely obtains their own fingerprint, and after being vouched for, they then read out their fingerprint out loud so everyone can verify it on the printout they have.</p>
</li>
<li>
<p>After everyone finishes this protocol, they can go home, obtain the keyring, run <tt class="USERINPUT"><b>pgp -kvc</b></tt> on it themselves, and re-verify the bits, and sign the keys at their own leisure.</p>
</li>
<li>
<p>To save load on the keyservers, you can optionally send all signatures to the original person, who can collate them again into a single keyring and propagate that single keyring to the keyservers and to each individual.</p>
</li>
</ol>
<p>&#13;</p>
</div>
</div>
</blockquote>
<p>I&#8217;m going to have to put my key signature where my mouth is.  Hopefully there will be another key signing party soon, for which I will be more prepared.</p>
<p>&#8211;Bob.</p>
<p><sup><a href="#ref1" id="footnote1" title="Go back to Reference 1">[1]</a></sup> Yes, it is still possible to have a meatspace <abbr title="Man in the Middle">MitM</abbr> attack if you&#8217;re signing keys for people you don&#8217;t know and relying on ID.  If you&#8217;ve never met me before then it is possible that someone mugs me in the parking lot, takes my ID and wears my goofy hat.  If you don&#8217;t know me you would never be able to tell the difference, and you&#8217;d be signing a key for the wrong person.</p>
<p><sup><a href="#ref2" id="footnote2" title="Go back to Reference 2">[2]</a></sup> Although that&#8217;s really <a href="http://pgp.mit.edu:11371/pks/lookup?op=vindex&#038;search=0xB91289B0D2CCE5EA" title="Search results for '0xb91289b0d2cce5ea'">my PGP key</a>, so as not to divulge the identity of innocent and unsuspecting Key Signing Party Organizers.</p>
<p><sup><a href="#ref3" id="footnote3" title="Go back to Reference 3">[3]</a></sup> Sadly, Kevin Herron makes the same mistake of requiring &quot;Positive picture ID&quot;.  Please ignore that part.</p>
<p style="font-size:smaller;"><a href="https://secure.flickr.com/photos/quasimondo/79765603/" title="Key | Flickr - Photo Sharing!">Key</a> by <a href="https://secure.flickr.com/people/quasimondo/" title="Flickr: Quasimondo">Quasimondo</a> is used under a <a href="https://creativecommons.org/licenses/by-nc/2.0/deed.en_CA" title="Creative Commons — Attribution-NonCommercial 2.0 Generic — CC BY-NC 2.0">Creative Commons by-nc</a> license.</p>
]]></content:encoded>
			<wfw:commentRss>http://bob.jonkman.ca/blogs/2011/10/14/how-to-hold-a-key-signing-party/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Plus considered harmful</title>
		<link>http://bob.jonkman.ca/blogs/2011/06/29/google-plus-considered-harmful/</link>
		<comments>http://bob.jonkman.ca/blogs/2011/06/29/google-plus-considered-harmful/#comments</comments>
		<pubDate>Wed, 29 Jun 2011 04:59:18 +0000</pubDate>
		<dc:creator>Bob Jonkman</dc:creator>
				<category><![CDATA[considered harmful]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[Google Plus]]></category>
		<category><![CDATA[Mashable]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[Techcrunch]]></category>

		<guid isPermaLink="false">http://bob.jonkman.ca/blogs/?p=415</guid>
		<description><![CDATA[Google Plus is available. I won&#8217;t be using it. Google has too much of my data already. For gushing, sycophantic reviews see Mashable and Techcrunch. Update 8 July 2011: Someone pointed out that I should probably investigate Google Plus before dissing it, so I’m licking the Google salt block. There will another blog post with [...]]]></description>
			<content:encoded><![CDATA[<p><div id="attachment_417" class="wp-caption alignright" style="width: 288px"><a href="http://bob.jonkman.ca/blogs/?attachment_id=417" title="This Blog Is Not For Reading » Blog Archive » Google Plus Screenshot"><img src="http://bob.jonkman.ca/blogs/files/2011/06/Google-Plus-Screenshot-278x300.png" alt="Google Plus login screen, with errors" title="Google Plus Screenshot" width="278" height="300" class="size-medium wp-image-417" /></a><p class="wp-caption-text">Google Plus Screenshot</p></div><a href="http://plus.google.com/" title="The Google+ project: Real life sharing, rethought for the web.">Google Plus</a> is available.  </p>
<p>I won&#8217;t be using it.  Google has too much of my data already.</p>
<p>For gushing, sycophantic reviews see <a href="http://mashable.com/2011/06/28/google-plus/" title="Google Launches Its Answer to Facebook: Introducing Google+ [PICS]">Mashable</a> and <a href="http://techcrunch.com/2011/06/28/google-plus/" title="Google+ Project: It’s Social, It’s Bold, It’s Fun, And It Looks Good — Now For The Hard Part">Techcrunch</a>.</p>
<hr />
<p style="margin-left: 3em;"><strong>Update 8 July 2011</strong>: <ins datetime="2011-07-08T19:30-0400" style="text-decoration: none;">Someone pointed out that I should probably investigate Google Plus before dissing it, so I’m licking the Google salt block. There will another blog post with the results of this investigation… In the meantime, <a href="https://plus.google.com/113242521569190236474" title="Bob Jonkman - Google+">Circle Me</a>!</ins></p>
<hr />
<p style="margin-left: 3em;"><strong>Update: 13 October 2011</strong>:  <ins datetime="2011-10-13T00:30-0400" style="text-decoration: none;"><a href="http://bob.jonkman.ca/blogs/2011/10/13/the-verdict-on-google-plus-mostly-harmless/" title="This Blog Is Not For Reading » Blog Archive » The Verdict on Google Plus: Mostly Harmless">The Verdict on Google Plus: Mostly Harmless</a></ins></p>
]]></content:encoded>
			<wfw:commentRss>http://bob.jonkman.ca/blogs/2011/06/29/google-plus-considered-harmful/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Deep Packet Inspection considered harmful</title>
		<link>http://bob.jonkman.ca/blogs/2009/11/13/deep-packet-inspection-considered-harmful/</link>
		<comments>http://bob.jonkman.ca/blogs/2009/11/13/deep-packet-inspection-considered-harmful/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 22:29:47 +0000</pubDate>
		<dc:creator>Bob</dc:creator>
				<category><![CDATA[considered harmful]]></category>
		<category><![CDATA[Deep Packet Inspection]]></category>
		<category><![CDATA[privacy]]></category>

		<guid isPermaLink="false">http://bob.jonkman.ca/blogs/?p=95</guid>
		<description><![CDATA[Michael Geist points us to a Sandvine report analyzing global broadband traffic. Far more interesting than the data presented by Sandvine is the fact that Sandvine has any data to present at all. How did they get this stuff? Did they buy it from Bell and Rogers? Does their throttling equipment phone home? I don&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p><div class="wp-caption alignright" style="width: 310px"><a title="Image from Stop Usage Based Billing blog, used by CC0 license" href="http://stopusagebasedbilling.wordpress.com/2009/10/06/b-packets-and-the-internet/"><img alt="Ripe for Deep Packet Inspection" src="http://stopusagebasedbilling.files.wordpress.com/2009/10/data.jpg?w=300&amp;h=168" width="300" height="168" /></a><p class="wp-caption-text">Ripe for Deep Packet Inspection</p></div><a href="http://www.michaelgeist.ca/content/view/4535/125/" title="Michael Geist: Sandvine Report Should Raise Doubt About Traffic Management Practices">Michael Geist points us</a> to a <a href="http://www.sandvine.com/news/global_broadband_trends.asp" title="Sandvine: 2009 Global Broadband Phenomena">Sandvine report analyzing global broadband traffic</a>.</p>
<p></p>
<p>Far more interesting than the data presented by Sandvine is the fact that Sandvine has any data to present at all.  How did they get this stuff?  Did they buy it from Bell and Rogers?  Does their throttling equipment phone home?  I don&#8217;t recall giving them permission to use my data.</p>
<p>They claim they&#8217;re not looking at data content.  Maybe that&#8217;s true, maybe it&#8217;s not.  But they&#8217;ve inspected deeply enough to know that we use more streaming applications than P2P, and more Bittorrent than Gnutella.  As any data analyst knows, traffic analysis of data patterns gives as much information as the data itself. Why are they allowed to gather any of this data at all? None of their business what I use on my computer.
</p>
<p>
I&#8217;m sure Sandvine is making a hefty buck selling this report, or at least using it as evidence to sell more of their DPI equipment.  They&#8217;re profiting from the the data that I didn&#8217;t give them permission to use.  I think the Privacy Commissioner may want to look into this.
</p>
<p>
&#8211;Bob.</p>
]]></content:encoded>
			<wfw:commentRss>http://bob.jonkman.ca/blogs/2009/11/13/deep-packet-inspection-considered-harmful/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

