<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#ffffff" text="#000000">
<h2 class="with-tabs"><big>Keysigning party</big></h2>
<big> </big><big> </big><big>Like previous years, there will be a
keysigning party at FOSDEM.</big>
<div id="node-86" class="clearfix node">
<div class="content"><big></big>
<p><big>Both CAcert and GPG/PGP signing will be done.</big></p>
<big></big>
<h2><big>GPG/PGP keysigning</big></h2>
<big></big>
<p><big>A PGP Keysigning Party is a meeting where people exchange "PGP
key
fingerprints" in a secure way.<br>
These meetings are quite often fun too.<br>
Exchanging key fingerprints enables one to strengthen the "web of
trust". A
stronger web of trust makes more secure communication using the
internet
possible. For instance, the content of your emails cannot be read by
others.
Even if your key has already been signed by others, it's useful to
attend such
a party: the more people have signed your key, the more trustworthy
your key
can be to others.</big></p>
<big></big>
<p><big>Instructions on how to join the PGP Keysigning Party
are published at <a href="http://ksp.mdcc.cx/">ksp.mdcc.cx</a>.</big></p>
<big></big>
<p><big><b>Stuff to do right now</b><br>
First, submit your PGP public key to the HKP keyserver at ksp.mdcc.cx.
Run<br>
<code> gpg --keyserver hkp://ksp.mdcc.cx --keyserver-options
export-minimal --send-keys <i>yourkeyid</i></code>
<br>
Where <i>yourkeyid</i> is an ID like e.g. 0B86B067: When output of <code>"gpg
--fingerprint
'<i>Your Name</i>'</code>" looks like:<br>
<code> pub 2048D/0B86B067 2006-02-27<br>
uid Joost van Baal [...]<br>
sub 2048g/F0B86553 2006-02-27</code>
<br>
you need "<code>0B86B067</code>": on the line with "<code>pub</code>".</big></p>
<big></big>
<p><big>Instructions on how to join the PGP Keysigning Party
are published at <a href="http://ksp.mdcc.cx/">ksp.mdcc.cx</a>.</big></p>
<big></big>
<h2><big>CACert</big></h2>
<big><b>TODO for visitors</b>
<br>
</big>
<ul>
<li><big> If you can (you'll have less work later on), first go to
the <a href="http://www.cacert.org">CAcert</a> website to register.
</big></li>
<li><big> Once logged in on the site, you'll find a <i>"CAcert Web
of Trust"</i> menu. Click on that title to open the menu and download
the personal <i>"A4 - WoT Form"</i>.
I recommend you to print approx 20-40 sheets of this document. as it
will enable you to be signed by other people too. You need more as just
one Assurance in order to have your name on the certificate or even
become an Assurer yourself and help to establish the web of trust. You
should also do this if you are already assurer, so that cross
signatures are possible.
</big></li>
<li><big> <b>Take 2 official proofs of identity.</b> (eg: ID-card,
drivers-license, passport,...).
</big></li>
</ul>
<!--a name="gpg"><a name="pgp"><h1>GPG/PGP Keysigning</h1></a></a>
<p><strong>Submission is now closed.</strong> If you submitted your key previously, you should be in the list. You must now:</p>
<ul>
<li><a href="http://grep.be/data/fosdem-2008-keysigning.txt">Download the list of keys</a>.</li>
<li>Verify that your key fingerprint is correct. It should be; but if it isn't, see below.</li>
<li>Print the list of keys.</li>
<li>Calculate the checksums, as detailed in the list, and fill them in on the designated spots.</li>
<li>Don't forget to bring the list and some proof of ID to the key signing party next week.</li>
</ul>
<p>If you do not have your own list of keys with your own checksums, then <strong>you will <em>not</em> be able to participate in the keysigning party!</strong></p>
<p><strong>What to do if your key is listed incorrectly, or you were too late to submit your key?</strong></p>
<p>First, <a href="mailto:w@uter.be">contact Wouter</a>. If there are many problems with the list, there <em>may</em> be an update. Don't count on it though. The list was prepared carefully.</p>
<p>Next, you may bring paper slips with key fingerprints. Be sure to bring enough of them. There isn't much time, so it must all run smoothly. For that reason, copying the fingerprint with a pen and a piece of paper <strong>will not be allowed</strong>. If you run out of fingerprint slips, tough.</p>
<p>At the keysigning party, we will then go through the following procedure:</p>
<ul>
<li>We will read out both checksums, so that everyone can verify that their file is the exact same as everyone else's.</li>
<li>Next, we will line up and compare identity information against key identity information, as in a usual key signing party.</li>
</ul>
<p>We'll be using this procedure because it is much faster than the one in which each and every key is checked manually; however, because of the trust link to the list of keys that is required in this scenario, we cannot print out a list of keys for participants, as was the case in previous years. You <strong>must</strong> bring one yourself, and calculate the checksums.</p>
--><big>The proceedings for the signing are simple. <br>
We make 1 line, Assurers will sit (floor/seat), visitors willing to
be assured will pass and show their identity papers. Papers will be
signed.
<br>
<br>
<b>More information</b>
<br>
<a href="http://wiki.cacert.org/wiki/FAQ/AssuranceIntroduction">Introduction
to the CAcert Assurance Program</a>
<br>
<a href="http://www.cacert.org">http://www.cacert.org</a> <br>
<a href="http://wiki.cacert.org">http://wiki.cacert.org</a> </big>
<p
style="border: 2px dotted red; padding: 1em; background-color: rgb(255, 255, 238); font-size: 150%; text-align: center;"><!--See <a href="http://fosdem.org/2009/schedule/events">here</a> for the schedule of the keysigning session--><big>
The keysigning will take place on Sunday. More details later.
</big></p>
<big> </big></div>
</div>
<pre class="moz-signature" cols="73">--
Christophe Vandeplas
<a class="moz-txt-link-abbreviated" href="mailto:cvandeplas@fosdem.org">cvandeplas@fosdem.org</a>
<a class="moz-txt-link-freetext" href="http://www.fosdem.org">http://www.fosdem.org</a>
</pre>
</body>
</html>