]> git.immae.eu Git - github/shaarli/Shaarli.git/blame - doc/GnuPG-signature.html
Doc: sync from Wiki, generate HTML
[github/shaarli/Shaarli.git] / doc / GnuPG-signature.html
CommitLineData
992af0b9
V
1<!DOCTYPE html>
2<html>
3<head>
4 <meta charset="utf-8">
5 <meta name="generator" content="pandoc">
6 <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
7 <title>Shaarli - GnuPG signature</title>
8 <style type="text/css">code{white-space: pre;}</style>
9 <!--[if lt IE 9]>
10 <script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
11 <![endif]-->
12 <style type="text/css">
13table.sourceCode, tr.sourceCode, td.lineNumbers, td.sourceCode {
14 margin: 0; padding: 0; vertical-align: baseline; border: none; }
15table.sourceCode { width: 100%; line-height: 100%; }
16td.lineNumbers { text-align: right; padding-right: 4px; padding-left: 4px; color: #aaaaaa; border-right: 1px solid #aaaaaa; }
17td.sourceCode { padding-left: 5px; }
18code > span.kw { color: #007020; font-weight: bold; }
19code > span.dt { color: #902000; }
20code > span.dv { color: #40a070; }
21code > span.bn { color: #40a070; }
22code > span.fl { color: #40a070; }
23code > span.ch { color: #4070a0; }
24code > span.st { color: #4070a0; }
25code > span.co { color: #60a0b0; font-style: italic; }
26code > span.ot { color: #007020; }
27code > span.al { color: #ff0000; font-weight: bold; }
28code > span.fu { color: #06287e; }
29code > span.er { color: #ff0000; font-weight: bold; }
30 </style>
31 <link rel="stylesheet" href="github-markdown.css">
32</head>
33<body>
34<div id="local-sidebar">
35<ul>
36<li><a href="Home.html">Home</a></li>
37<li>Installation
38<ul>
f8b936e7 39<li><a href="Download.html">Download</a></li>
992af0b9
V
40<li><a href="Server-requirements.html">Server requirements</a></li>
41<li><a href="Server-configuration.html">Server configuration</a></li>
42<li><a href="Shaarli-configuration.html">Shaarli configuration</a></li>
43</ul></li>
44<li><a href="Usage.html">Usage</a>
45<ul>
46<li><a href="Sharing-button.html">Sharing button</a> (bookmarklet)</li>
47<li><a href="Firefox-share.html">Firefox share</a></li>
48<li><a href="RSS-feeds.html">RSS feeds</a></li>
49</ul></li>
50<li>How To
51<ul>
52<li><a href="Backup,-restore,-import-and-export.html">Backup, restore, import and export</a></li>
53<li><a href="Copy-an-existing-installation-over-SSH-and-serve-it-locally.html">Copy an existing installation over SSH and serve it locally</a></li>
54<li><a href="Download-CSS-styles-from-an-OPML-list.html">Download CSS styles from an OPML list</a></li>
6335a0fc 55<li><a href="Datastore-hacks.html">Datastore hacks</a></li>
992af0b9
V
56</ul></li>
57<li><a href="Troubleshooting.html">Troubleshooting</a></li>
58<li><a href="Development.html">Development</a>
59<ul>
60<li><a href="GnuPG-signature.html">GnuPG signature</a></li>
61<li><a href="Coding-guidelines.html">Coding guidelines</a></li>
62<li><a href="Directory-structure.html">Directory structure</a></li>
63<li><a href="3rd-party-libraries.html">3rd party libraries</a></li>
64<li><a href="Plugin-System.html">Plugin System</a></li>
65<li><a href="Security.html">Security</a></li>
66<li><a href="Static-analysis.html">Static analysis</a></li>
67<li><a href="Theming.html">Theming</a></li>
68<li><a href="Unit-tests.html">Unit tests</a></li>
69</ul></li>
70<li>About
71<ul>
72<li><a href="FAQ.html">FAQ</a></li>
73<li><a href="Community-&amp;-Related-software.html">Community &amp; Related software</a></li>
74<li><a href="TODO.html">TODO</a></li>
75</ul></li>
76</ul>
77</div>
78<h1 id="gnupg-signature">GnuPG signature</h1>
79<h2 id="introduction">Introduction</h2>
80<h3 id="pgp-and-gpg">PGP and GPG</h3>
81<p><a href="https://gnupg.org/">Gnu Privacy Guard</a> (GnuPG) is an Open Source implementation of the <a href="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>
82<p>It is often used by the <a href="https://en.wikipedia.org/wiki/Free_and_open-source_software">FLOSS</a> community to verify:<a href=".html"></a></p>
83<ul>
84<li>Linux package signatures: Debian <a href="https://wiki.debian.org/SecureApt">SecureApt</a>, ArchLinux <a href="https://www.archlinux.org/master-keys/">Master [](.html)<br />Keys</a></li>
85<li><a href="https://en.wikipedia.org/wiki/Revision_control">SCM</a> releases &amp; maintainer identity<a href=".html"></a></li>
86</ul>
87<h3 id="trust">Trust</h3>
88<p>To quote Phil Pennock (the author of the <a href="https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Home">SKS</a> key server - <a href="http://sks.spodhuis.org/" class="uri">http://sks.spodhuis.org/</a>):<a href=".html"></a></p>
89<blockquote>
90<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>
91</blockquote>
92<p>Trust can be gained by having your key signed by other people (and signing their key back, too :) ), for instance during <a href="https://en.wikipedia.org/wiki/Key_signing_party">key signing parties</a>, see:<a href=".html"></a></p>
93<ul>
94<li><a href="http://www.cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html">The Keysigning party HOWTO</a><a href=".html"></a></li>
95<li><a href="https://en.wikipedia.org/wiki/Web_of_trust">Web of trust</a><a href=".html"></a></li>
96</ul>
97<h2 id="generate-a-gpg-key">Generate a GPG key</h2>
98<p>See <a href="http://stackoverflow.com/a/16725717">Generating a GPG key for Git tagging</a>.<a href=".html"></a></p>
99<h3 id="gpg---provide-identity-information">gpg - provide identity information</h3>
100<pre class="sourceCode bash"><code class="sourceCode bash">$ <span class="kw">gpg</span> --gen-key
101
102<span class="kw">gpg</span> (GnuPG) <span class="kw">2.1.6;</span> <span class="kw">Copyright</span> (C) <span class="kw">2015</span> Free Software Foundation, Inc.
103<span class="kw">This</span> is free software: you are free to change and redistribute it.
104<span class="kw">There</span> is NO WARRANTY, to the extent permitted by law.
105
106<span class="kw">Note</span>: Use <span class="st">&quot;gpg2 --full-gen-key&quot;</span> for a full featured key generation dialog.
107
108<span class="kw">GnuPG</span> needs to construct a user ID to identify your key.
109
110<span class="kw">Real</span> name: Marvin the Paranoid Android
111<span class="kw">Email</span> address: marvin@h2g2.net
112<span class="kw">You</span> selected this USER-ID:
113 <span class="st">&quot;Marvin the Paranoid Android &lt;marvin@h2g2.net&gt;&quot;</span>
114
115<span class="kw">Change</span> (N)<span class="kw">ame</span>, (E)<span class="kw">mail</span>, or (O)<span class="kw">kay</span>/<span class="kw">(Q)uit?</span> o
116<span class="kw">We</span> need to generate a lot of random bytes. It is a good idea to perform
117<span class="kw">some</span> other action (type on the keyboard, move the mouse, utilize the
118<span class="kw">disks</span>) <span class="kw">during</span> the prime generation<span class="kw">;</span> <span class="kw">this</span> gives the random number
119<span class="kw">generator</span> a better chance to gain enough entropy.</code></pre>
120<h3 id="gpg---entropy-interlude">gpg - entropy interlude</h3>
121<p>At this point, you will:</p>
122<ul>
123<li>be prompted for a secure password to protect your key (the input method will depend on your Desktop Environment and configuration)</li>
124<li>be asked to use your machine's input devices (mouse, keyboard, etc.) to generate random entropy; this step <em>may take some time</em></li>
125</ul>
126<h3 id="gpg---key-creation-confirmation">gpg - key creation confirmation</h3>
127<pre class="sourceCode bash"><code class="sourceCode bash"><span class="kw">gpg</span>: key A9D53A3E marked as ultimately trusted
128<span class="kw">public</span> and secret key created and signed.
129
130<span class="kw">gpg</span>: checking the trustdb
131<span class="kw">gpg</span>: 3 marginal(s) <span class="kw">needed</span>, 1 complete(s) <span class="kw">needed</span>, PGP trust model
132<span class="kw">gpg</span>: depth: 0 valid: 2 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 2u
133<span class="kw">pub</span> rsa2048/A9D53A3E 2015-07-31
134 <span class="kw">Key</span> fingerprint = AF2A 5381 E54B 2FD2 14C4 A9A3 0E35 ACA4 A9D5 3A3E
135<span class="kw">uid</span> [ultimate] Marvin the Paranoid Android <span class="kw">&lt;</span>marvin@h2g2.net<span class="kw">&gt;</span>[](.html)
136<span class="kw">sub</span> rsa2048/8C0EACF1 2015-07-31</code></pre>
137<h3 id="gpg---submit-your-public-key-to-a-pgp-server-optional">gpg - submit your public key to a PGP server (Optional)</h3>
138<pre class="sourceCode bash"><code class="sourceCode bash">$ <span class="kw">gpg</span> --keyserver pgp.mit.edu --send-keys A9D53A3E
139<span class="kw">gpg</span>: sending key A9D53A3E to hkp server pgp.mit.edu</code></pre>
140<h2 id="create-and-push-a-gpg-signed-tag">Create and push a GPG-signed tag</h2>
141<p>See <a href="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>
142<h3 id="prerequisites">Prerequisites</h3>
143<p>This guide assumes that you have:</p>
144<ul>
145<li>a GPG key matching your GitHub authentication credentials
146<ul>
147<li>i.e., the email address identified by the GPG key is the same as the one in your <code>~/.gitconfig</code></li>
148</ul></li>
149<li>a GitHub fork of Shaarli</li>
150<li>a local clone of your Shaarli fork, with the following remotes:
151<ul>
152<li><code>origin</code> pointing to your GitHub fork</li>
153<li><code>upstream</code> pointing to the main Shaarli repository</li>
154</ul></li>
155<li>maintainer permissions on the main Shaarli repository (to push the signed tag)</li>
156</ul>
157<h3 id="bump-shaarlis-version">Bump Shaarli's version</h3>
158<pre class="sourceCode bash"><code class="sourceCode bash">$ <span class="kw">cd</span> /path/to/shaarli
159
160<span class="co"># create a new branch</span>
161$ <span class="kw">git</span> fetch upstream
162$ <span class="kw">git</span> checkout upstream/master -b v0.5.0
163
164<span class="co"># bump the version number</span>
165$ <span class="kw">vim</span> index.php shaarli_version.php
166
167<span class="co"># commit the changes</span>
168$ <span class="kw">git</span> add index.php shaarli_version.php
169$ <span class="kw">git</span> commit -s -m <span class="st">&quot;Bump version to v0.5.0&quot;</span>
170
171<span class="co"># push the commit on your GitHub fork</span>
172$ <span class="kw">git</span> push origin v0.5.0</code></pre>
173<h3 id="create-and-merge-a-pull-request">Create and merge a Pull Request</h3>
174<p>This one is pretty straightforward ;-)</p>
175<h3 id="create-and-push-a-signed-tag">Create and push a signed tag</h3>
176<pre class="sourceCode bash"><code class="sourceCode bash"><span class="co"># update your local copy</span>
177$ <span class="kw">git</span> checkout master
178$ <span class="kw">git</span> fetch upstream
179$ <span class="kw">git</span> pull upstream master
180
181<span class="co"># create a signed tag</span>
182$ <span class="kw">git</span> tag -s -m <span class="st">&quot;Release v0.5.0&quot;</span> v0.5.0
183
184<span class="co"># push it to &quot;upstream&quot;</span>
185$ <span class="kw">git</span> push --tags upstream</code></pre>
186<h3 id="verify-a-signed-tag">Verify a signed tag</h3>
187<p><a href="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.<a href=".html"></a></p>
188<p>Let's have a look at its signature!</p>
189<pre class="sourceCode bash"><code class="sourceCode bash">$ <span class="kw">cd</span> /path/to/shaarli
190$ <span class="kw">git</span> fetch upstream
191
192<span class="co"># get the SHA1 reference of the tag</span>
193$ <span class="kw">git</span> show-ref tags/v0.5.0
194<span class="kw">f7762cf803f03f5caf4b8078359a63783d0090c1</span> refs/tags/v0.5.0
195
196<span class="co"># verify the tag signature information</span>
197$ <span class="kw">git</span> verify-tag f7762cf803f03f5caf4b8078359a63783d0090c1
198<span class="kw">gpg</span>: Signature made Thu 30 Jul 2015 11:46:34 CEST using RSA key ID 4100DF6F
199<span class="kw">gpg</span>: Good signature from <span class="st">&quot;VirtualTam &lt;virtualtam@flibidi.net&gt;&quot;</span> [ultimate][](.html)</code></pre>
200</body>
201</html>