<li><ahref="Community-&-Related-software.html">Community & Related software</a></li>
<li><ahref="TODO.html">TODO</a></li>
</ul></li>
</ul>
</div>
<h1id="gnupg-signature">GnuPG signature</h1>
<h2id="introduction">Introduction</h2>
<h3id="pgp-and-gpg">PGP and GPG</h3>
<p><ahref="https://gnupg.org/">Gnu Privacy Guard</a> (GnuPG) is an Open Source implementation of the <ahref="https://en.wikipedia.org/wiki/Pretty_Good_Privacy#OpenPGP">Pretty Good [](.html)<br/>Privacy</a> (OpenPGP) specification. Its main purposes are digital authentication,<br/>signature and encryption.</p>
<p>It is often used by the <ahref="https://en.wikipedia.org/wiki/Free_and_open-source_software">FLOSS</a> community to verify:<ahref=".html"></a></p>
<li><ahref="https://en.wikipedia.org/wiki/Revision_control">SCM</a> releases & maintainer identity<ahref=".html"></a></li>
</ul>
<h3id="trust">Trust</h3>
<p>To quote Phil Pennock (the author of the <ahref="https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Home">SKS</a> key server - <ahref="http://sks.spodhuis.org/"class="uri">http://sks.spodhuis.org/</a>):<ahref=".html"></a></p>
<blockquote>
<p>You MUST understand that presence of data in the keyserver (pools) in no way connotes trust. Anyone can generate a key, with any name or email address, and upload it. All security and trust comes from evaluating security at the “object level”, via PGP Web-Of-Trust signatures. This keyserver makes it possible to retrieve keys, looking them up via various indices, but the collection of keys in this public pool is KNOWN to contain malicious and fraudulent keys. It is the common expectation of server operators that users understand this and use software which, like all known common OpenPGP implementations, evaluates trust accordingly. This expectation is so common that it is not normally explicitly stated.</p>
</blockquote>
<p>Trust can be gained by having your key signed by other people (and signing their key back, too :) ), for instance during <ahref="https://en.wikipedia.org/wiki/Key_signing_party">key signing parties</a>, see:<ahref=".html"></a></p>
<ul>
<li><ahref="http://www.cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html">The Keysigning party HOWTO</a><ahref=".html"></a></li>
<li><ahref="https://en.wikipedia.org/wiki/Web_of_trust">Web of trust</a><ahref=".html"></a></li>
</ul>
<h2id="generate-a-gpg-key">Generate a GPG key</h2>
<p>See <ahref="http://stackoverflow.com/a/16725717">Generating a GPG key for Git tagging</a>.<ahref=".html"></a></p>
<h3id="gpg---provide-identity-information">gpg - provide identity information</h3>
<spanclass="st">"Marvin the Paranoid Android <marvin@h2g2.net>"</span>
<spanclass="kw">Change</span> (N)<spanclass="kw">ame</span>, (E)<spanclass="kw">mail</span>, or (O)<spanclass="kw">kay</span>/<spanclass="kw">(Q)uit?</span> o
<spanclass="kw">We</span> need to generate a lot of random bytes. It is a good idea to perform
<spanclass="kw">some</span> other action (type on the keyboard, move the mouse, utilize the
<spanclass="kw">disks</span>) <spanclass="kw">during</span> the prime generation<spanclass="kw">;</span><spanclass="kw">this</span> gives the random number
<spanclass="kw">generator</span> a better chance to gain enough entropy.</code></pre>
<spanclass="kw">gpg</span>: sending key A9D53A3E to hkp server pgp.mit.edu</code></pre>
<h2id="create-and-push-a-gpg-signed-tag">Create and push a GPG-signed tag</h2>
<p>See <ahref="http://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project#Tagging-Your-Releases">Git - Maintaining a project - Tagging your [](.html)<br/>releases</a>.</p>
<h3id="prerequisites">Prerequisites</h3>
<p>This guide assumes that you have:</p>
<ul>
<li>a GPG key matching your GitHub authentication credentials
<ul>
<li>i.e., the email address identified by the GPG key is the same as the one in your <code>~/.gitconfig</code></li>
</ul></li>
<li>a GitHub fork of Shaarli</li>
<li>a local clone of your Shaarli fork, with the following remotes:
<ul>
<li><code>origin</code> pointing to your GitHub fork</li>
<li><code>upstream</code> pointing to the main Shaarli repository</li>
</ul></li>
<li>maintainer permissions on the main Shaarli repository (to push the signed tag)</li>
<h3id="verify-a-signed-tag">Verify a signed tag</h3>
<p><ahref="https://github.com/shaarli/Shaarli/releases/tag/v0.5.0"><code>v0.5.0</code></a> is the first GPG-signed tag pushed on the Community Shaarli.<ahref=".html"></a></p>
<spanclass="kw">gpg</span>: Signature made Thu 30 Jul 2015 11:46:34 CEST using RSA key ID 4100DF6F
<spanclass="kw">gpg</span>: Good signature from <spanclass="st">"VirtualTam <virtualtam@flibidi.net>"</span> [ultimate][](.html)</code></pre>
