Merge branch 'master' of vcs.fsf.org:enc
[enc-live.git] / index.html
index c02f92bf04f64152d867e4a1e19625e66b53f2a1..e03cdf6eb25974bfed3510521257a64af6404689 100644 (file)
@@ -23,9 +23,9 @@
                                        <li><a href="mac.html">Mac OS</a></li>
                                        <li><a href="windows.html">Windows</a></li>
                                </ul>
-                               <ul class="lang">
+                               <!--<ul class="lang">
                                        <li class="help"><a href="http://libreplanet.org/wiki/GPG_guide">Translate this guide!</a></li>
-                               </ul>
+                               </ul> -->
                        </div>
                </nav>
 
 
                        <div>
                                <h1>Email Self-Defense</h1>
-                               <div class="intro">
-                                       <p>The goal of this guide is to make it easy to set up email encryption on your computer. Once you've finished the guide, you'll be able to send and receive emails that are coded to make sure that a surveillance agent or thief can't intercept your email and read it. </p>
-                                       <p>This isn't something you'd do with every email, or even every day. Rather, it's a tool to have handy when you need to send something sensitive.</p>
-                                       <p>You'll also be able to sign emails to show reliably that they are from you. Though the need for signing may be less obvious, you'll actually do it more often.</p>
-                                       <p>All you need is a computer with GNU/Linux or Windows and an Internet connection. You can use your existing email account for this without affecting it.</p> 
-                               </div>
+
                                <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
                                <div id="fsf-intro">
                                        <h3><a href="http://u.fsf.org/ys"><img alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png"></a></h3>
-                                       <p>Email Self-Defense is a project of the Free Software Foundation. The FSF works to secure freedom for computer users by promoting the development and use of free (as in freedom) software and documentation.</p><p>For our next step, we want to set up events to teach Email Self-Defense all over the world. Can you pitch in to help?</p>
+                                       <p>Email Self-Defense is a project of the Free Software Foundation. The FSF works to secure freedom for computer users by promoting the development and use of free (as in freedom) software and documentation.</p><p>We have big plans to get it in the hands of people under bulk surveillance all over the world, and make more tools like it. Can you make a donation to help us achieve that goal?</p>
 
                                        <!--<p><a href="https://u.fsf.org/yr"><img alt="Join now" src="http://static.fsf.org/nosvn/enc-dev0/img/join.en.png"></a></p>-->
                                        <p><a href="https://u.fsf.org/7w"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/donate.en.png"></a></p>
                                        </div><!-- End .newsletter -->
                                </div><!-- End #fsf-intro -->
 
+                               <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
+                               <div class="intro">
+                                       <p id="infographic">
+                                               <a class="img-link" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/infographic-button.png" alt="Email Self-Defense, Infographic" /></a>
+                                               <a class="text-link" href="infographic.html">View &amp; share our infographic &rarr;</a>
+                                       </p>
+                                       <p>The goal of this guide is to make it easy to set up email encryption on your computer. Once you've finished, you'll be able to send and receive emails that are coded to make sure that a surveillance agent or thief can't intercept your email and read it. </p>
+                                       <!--<p>You'll also be able to sign emails to show reliably that they are from you. Though the need for signing may be less obvious, you'll actually do it more often.</p>-->
+                                       <p>All you need is a computer with an Internet connection, an email account and about half an hour. You can use your existing email account for this without affecting it.</p>
+                                       <p>This guide relies on software which is freely licensed; it's completely transparent and anyone can copy it or make their own version. This makes it safer from surveillance than proprietary software (like Windows). Learn more about free software at <a href="https://u.fsf.org/ys">fsf.org</a>.</p>
+
+                               </div>
+                               
                        </div>
                </header><!-- End #header -->
 
                                </div><!-- End #step1-a .step -->
 
                                <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
-                               <div id="step-1c" class="step">
+                               <div id="step-1b" class="step">
                                        <div class="sidebar">
-                                               <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></p>
+                                               <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></p>
+                                               <ul class="images">
+                                                       <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-02-search.png" alt="Step 1.B: Search Add-ons" /></li><li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-03-install.png" alt="Step 1.B: Install Add-ons" /></li>
+                                               </ul>
+
                                        </div><!-- /.sidebar -->
                                        <div class="main">
                                                <h3><em>Step 1.b</em> Install the Enigmail plugin for your email program</h3>
                                                        <dl>
                                                                <dt>I can't find the menu.</dt>
                                                                        <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars.</dd>
+
                                                                <dt class="feedback">Don't see a solution to your problem?</dt>
                                                                        <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
                                                        </dl>
                                                </div><!-- /.troubleshooting -->
                                        </div><!-- End .main -->
-                               </div><!-- End #step-1c .step -->
+                               </div><!-- End #step-1b .step -->
                        </div>
                </section><!-- End #section1 -->
 
                                <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
                                <div id="step-2a" class="step">
                                        <div class="sidebar">
-                                               <p><img src="//static.fsf.org/nosvn/enc-dev0/img/placeholders/placeholder.png" alt="Placeholder" /></p>
+                                               <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>
                                        </div><!-- /.sidebar -->
                                        <div class="main">
                                                <h3><em>Step 2.a</em> Make a keypair</h3>
-                                               <p>In your email program's menu, select OpenPGP -> Setup Wizard. You don't need to read the text in the window that pops up unless you'd like to, but it's good to read the text on the later screens of the wizard.</p>
+                                               <p>In your email program's menu, select OpenPGP &rarr; Setup Wizard. You don't need to read the text in the window that pops up unless you'd like to, but it's good to read the text on the later screens of the wizard.</p>
                                                <p>On the second screen, titled "Signing," select "No, I want to create per-recipient rules for emails that need to be signed."</p>
                                                <p>Use the default options until you reach the screen titled "Create Key".</p>
                                                <p>On the screen titled "Create Key," pick a strong password! Your password should be at least 8 characters and include at least one lower case and upper case letter and at least one punctuation mark. Don't forget it, or all this work will be wasted!</p>
                                        <p>The program will take a little while to finish the next step, the "Key Creation" screen. While you wait, do something else with your computer, like watching a movie or browsing the Web. The more you use the computer at this point, the faster the key creation will go.</p>
-                                               <p>When the OpenPGP Confirm screen pops up, select Generate Certificate and choose to save it in a safe place on your computer (we recommend making a folder called "Revocation Certificate" in your home folder and keeping it there. You'll learn more about the revocation certificate in Section 5. The setup wizard will ask you to move it onto an external device, but that isn't necessary at this moment.</p>
+                                               <p>When the OpenPGP Confirm screen pops up, select Generate Certificate and choose to save it in a safe place on your computer (we recommend making a folder called "Revocation Certificate" in your home folder and keeping it there. You'll learn more about the revocation certificate in <a href="#section5">Section 5</a>. The setup wizard will ask you to move it onto an external device, but that isn't necessary at this moment.</p>
                                                <p class="highlight">After creating your key, the Enigmail set-up wizard automatically uploaded it to a keyserver, an online computer that makes everyone's keys available through the Internet.</p>
 
                                                <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
                                                        <dl>
                                                                <dt>I can't find the OpenPGP menu.</dt>
                                                                        <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars. OpenPGP may be inside a section called Tools.</dd>
+    <dt>The wizard says that it cannot find GnuPG.</dt>
+
+                                         <dd>Open whatever program you usually use for installing  software, and search for GnuPG, then install it. Then restart the  Engimail setup wizard by going to OpenPGP -> Setup Wizard.</dd>
                                                                <dt class="feedback">Don't see a solution to your problem?</dt>
                                                                        <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
                                                        </dl>
 <p>Put at least one word (whatever you want) in the subject and body of the email, then hit send.</p>
 
 <p>It may take two or three minutes for Adele to respond. In the meantime, you might want to skip ahead and check out the Use it well section of this guide. Once she's responded, head to the next step. From here one, you'll be doing just the same thing as when corresponding with a real person.</p>
-
-                               <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
-                                               <div class="troubleshooting">
-                                                       <h4>Troubleshooting</h4>
-                                                       <dl>
-                                                               <dt>PLACEHOLDER</dt>
-                                                                       <dd>PLACEHOLDER</dd>
-                                                               <dt class="feedback">Don't see a solution to your problem?</dt>
-                                                                       <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
-                                                       </dl>
-                                               </div><!-- /.troubleshooting -->
                                        </div><!-- End .main -->
                                </div><!-- End #step-3b .step -->
 
                                        </div><!-- End .main -->
                                </div><!-- End #step-3c .step -->
 
-                               <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
+<!-- STEP 3D IS COMMENTED OUT UNTIL WE FIND A WAY TO VALIDATE SIGNATURES
+                               <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ --
                                <div id="step-3d" class="step">
                                        <div class="main">
                                                <h3><em>Step 3.d</em> Send a test signed email to a friend</h3>
                                                <p>Write a new email in your email program, addressed to a friend. If you want, tell them about this guide!</p>
                                                <p>Before sending the email, click the icon of the pencil in the bottom right of the composition window (it should turn yellow). This tells Enigmail to sign the email with you private key.</p>
                                                <p>After you click send, Enigmail will ask you for your password. It will do this any time it needs to use your public key.</p>
-                                       </div><!-- End .main -->
+                                       </div><!-- End .main --
                                </div><!-- End #step-3d .step -->
                        </div>
-               </section><!-- End #section3 -->
+               </section><!-- End #section3 --
+
 
 <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust  ~~~~~~~~~ -->
                <section class="row" id="section4">
                                        </div><!-- /.sidebar -->
                                        <div class="main">
                                                <h3><em>Step 4.a</em> Sign a key</h3>
-                                               <p>In your email program's menu, go to OpenPGP -> Key Management.</p>
+                                               <p>In your email program's menu, go to OpenPGP &rarr; Key Management.</p>
                                                <p>Right click on Adele's public key and select Sign Key from the context menu.</p>
                                                <p>In the window that pops up, select "I will not answer" and click OK.</p>
-                                               <p>In your email program's menu, go to OpenPGP -> Key Management -> Keyserver -> Upload Public Keys and hit OK.</p>
+                                               <p>In your email program's menu, go to OpenPGP &rarr; Key Management &rarr; Keyserver &rarr; Upload Public Keys and hit OK.</p>
                                                <p class="highlight">You've just effectively said "I trust that Adele's public key actually belongs to Adele." This doesn't mean much because Adele isn't a real person. Before signing a real person's key, always make sure it actually belongs to them, and answer honestly in the window that pops up and asks "How carefully have you verified that the key you are about to sign actually belongs to the person(s) named above?".</p>
                                                <p class="highlight">It's important to take keysigning seriously because it will affect people beyond just you and the person who's key you are signing. If someone doubts that a key actually belongs to the person that is says it does, they can go on a keyserver and see the number of signatures that it has. The more it has, the more they are likely to trust it.</p>
                                                <p class="highlight">The Web of Trust takes this concept to the next level. It is a network of key signatures that is saved in keyservers on the Internet. It builds chains of trust between individuals that do not know each other by passing through others, a bit like the famous <a href="http://en.wikipedia.org/wiki/Six_degrees_of_separation">"six degrees of separation" game</a>. You don't need to understand it in detail to use email encryption, but it will become a powerful tool if you become an advanced user.</p>
+
+                                               <div id="pgp-pathfinder">
+                                                       <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
+                                                               <p><strong>From:</strong> <input type="text" name="FROM"></p>
+                                                               <p><strong>To:</strong> <input type="text" name="TO"></p>
+                                                               <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
+                                                       </form>
+                                               </div><!-- End #pgp-pathfinder -->
+
                                        </div><!-- End .main -->
                                </div><!-- End #step-4a .step -->
                        </div>
                                        <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
                                <div class="section-intro">
                                                <h2><em>#5</em> Use it well</h2>
+<p>Everyone uses GnuPG a little differently, but it's important to follow some basic practices to keep your email secure. Not following them, you risk the privacy of the people you communicate with, as well as your own, and damage the Web of Trust.</p>
                                </div><!-- End .section-intro -->
 
                                <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
                                <div id="step-5a" class="step">
                                        <div class="main">
-                                               <h3><em>Step 5a</em> When should I encrypt? When should I sign?</h3>
-                                               <p>Everyone uses GnuPG a little differently. Encryption is most important for messages involving finances, personal information, politically sensitive conversations and anything else that you wouldn't want to fall into the wrong hands. Signing is best for when you think there might be concern about your identity, or as a way of demonstrating that you know how to use GnuPG and will be able to decrypt emails. If you're already encrypting, there's no reason not to sign as well, to give the recipient added assurance that the message is from you.</p>
-                                               <p>If you're using your email program (or wherever you have GnuPG set up) often, we recommend that you sign all outgoing messages because it turns you into an ambassador for GnuPG. Anyone can read a signed email, so it doesn't matter if the recipient doesn't yet know how to use email encryption. The more you encrypt the better, but you won't be able to do so unless the recipient has a public key. However, if you've set it up for an email program on your computer, but you primarily use email through your phone, then you'll only want to fire up the email program and use GnuPG for special occasions. If this describes you, we recommend you use </p>
+                                               <h3>When should I encrypt?</h3>
+
+                                               <p>The more you can encrypt your messages, the better. This is because, if you only encrypt emails occasionally, each encrypted message could raise a red flag for surveillance systems. If all or most of your email is encrypted, people doing surveillance won't know where to start.</p>
+
+</p>That's not to say that only encrypting some of your email isn't helpful -- it's a great start and it makes bulk surveillance more difficult. And even people that encrypt as much as they can are still limited to those of their contacts that have public keys.</p>
+                                       
                                        </div><!-- End .main -->
                                </div><!-- End #step-5a .step -->
 
                                <div id="step-5b" class="step">
                                        <div class="main">
-                                               <h3><em>Step 5b</em> Be wary of invalid keys</h3>
-                                               <p>Coming soon</p>
+                                               <h3>Be wary of invalid keys</h3>
+                                               <p>GnuPG makes email safer, but it's still important to watch out for invalid keys, which which might have fallen into the wrong hands. Email encrypted with invalid keys might be readable by surveillance programs.</p>
+                                               <p>In your email program, go back to the second email that Adele sent you. Because it was encrypted with her key, it will have a message from OpenPGP at the top, which most likely says "OpenPGP: Part of this message encrypted."</p>
+<p><b>When using GnuPG, make a habit of glancing at that bar. The program will warn you there if you get an email encrypted with a key that can't be trusted.</b></p>
                                        </div><!-- End .main -->
                                </div><!-- End #step-5b .step -->
 
-                               <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
                                <div id="step-5c" class="step">
                                        <div class="main">
-                                               <h3><em>Step 5c</em> Make it part of your online identity</h3>
-                                               <p>Start writing your key ID anywhere someone would see your email address. Add it to your email signature, social media profile, blog, Website, or business card.</p>
-                                       <!-- ~~~~~~~~~ highlight  ~~~~~~~~~ -->
-                                               <div class="highlight">
-                                                       <h4>Important: act swiftly if you lose your key</h4>
-                                                       <p>If you lose your private key or someone else gets ahold of it (say, by stealing your computer), it's important to revoke it immediately before someone else uses it to steal your identity. This guide doesn't cover how to revoke a key, but it only takes a minute. We recommend you Google it or seek help from a skilled friend. After you're done revoking, send an email to everyone with whom you usually use your key to make sure they know.</p>
-                                               </div><!-- End .highlight -->
+                                               <h3>Copy your revocation certificate to somewhere safe</h3>
+                                               <p>Remember when you created your keys and saved the revocation cerfiticate that GnuPG made? It's time to copy that cerfiticate onto the safest digital storage that you have -- the ideal thing is a flash drive, disk or hard drive stored in a safe place in your home.</p>
+<p>If your private key ever gets lost or stolen, you'll need this certificate file.</p>
+                                       </div><!-- End .main -->
+                               </div><!-- End #step-5c .step -->
+
+                               <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
+                               <div id="step-lost_key" class="step">
+                                       <div class="main">
+                                               <h3><em>Important:</em> act swiftly if someone gets your private key</h3>
+                                               <p>If you lose your private key or someone else gets ahold of it (say, by stealing or cracking your computer), it's important to revoke it immediately before someone else uses it to steal your identity. This guide doesn't cover how to revoke a key, but it only takes a minute. We recommend you Google it or seek help from a skilled friend. After you're done revoking, send an email to everyone with whom you usually use your key to make sure they know.</p>
+                                       </div><!-- End .main -->
+                               </div><!-- End #step-lost_key .step-->
+
+                               <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
+                               <div id="step-5d" class="step">
+                                       <div class="main">
+                                               <h3>Make it part of your online identity</h3>
+                                               <p>Start writing your key ID anywhere someone would see your email address. Add it to your email signature, so that anyone corresponding with you knows that they can donwload your public key and verify that it's the correct one. It's also good to post it on your media profile, blog, Website, or business card. We need to get our culture to the point that we feel like something is missing when we see an email address without a public key ID.</p>
                                        </div><!-- End .main -->
-                               </div><!-- End #step-5c .step-->
+                               </div><!-- End #step-5d .step-->
+
+
                        </div>
                </section><!-- End #section5 -->
 
                                                <h2><em>#6</em> Next steps</h2>
                                </div><!-- End .section-intro -->
 
-                               <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
-                               <div id="step-gnulinux" class="step">
-                                       <div class="sidebar">
-                                               <p><img src="//static.fsf.org/nosvn/enc-dev0/img/placeholders/placeholder.png" alt="Placeholder" /></p>
-                                       </div><!-- /.sidebar -->
-                                       <div class="main">
-                                               <h3>Switch to GNU/Linux</h3>
-                                               <p>Coming soon</p>
-                                       </div><!-- End .main -->
-                               </div><!-- End #step-gnulinux .step -->
-
                                <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
                                <div id="step-keysigning_party" class="step">
                                        <div class="main">
                                <div id="step-programming" class="step">
                                        <div class="main">
                                                <h3>Make these tools even better</h3>
-                                               <p>Like programming? Contribute code to <a href="https://www.gnupg.org/">GnuPG</a> or <a href="https://www.enigmail.net/home/index.php">Enigmail</a>.</p>
+                                               <p>Like programming? Contribute code to <a href="https://www.gnupg.org/">GnuPG</a> or <a href="https://www.enigmail.net/home/index.php">Enigmail</a>. Have an idea for improving this guide? Leave us <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback</a>.</p>
                                        </div><!-- End .main -->
                                </div><!-- End #step-programming .step -->
 
                                                <p>There are a lot more features of GnuPG to discover, including encrypting files on your computer. There are a variety of resources accessible via Google, but we recommend starting with the links on the <a href="https://www.gnupg.org/documentation/">GnuPG Web site</a>.</p>
                                        </div><!-- End .main -->
                                </div><!-- End #step-learn_more .step -->
+
+                               <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
+                               <div id="step-contribute" class="step">
+                                       <div class="main">
+                                               <h3>Contribute to this guide</h3>
+                                               <ul>
+                                                       <li><a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Leave feedback and suggest improvements</a></li>
+                                                       <li>Email us at <a href="mailto:campaigns@fsf.org">campaigns@fsf.org</a> if you'd like to help maintain and improve this guide, or to translate it</a></li>
+                                                       <li><a href="https://u.fsf.org/7w">Donate to the Free Software Foundation</a></li>
+                                               </ul>
+                                       </div><!-- End .main -->
+                               </div><!-- End #step-contribute .step -->
                                        
                        </div>
                </section><!-- End #section6 -->
 
 <!-- ~~~~~~~~~ FAQ  ~~~~~~~~~ -->
+<!-- When un-commenting this section go to main.css and search
+               for /* Guide Sections Background */ then add #faq to the desired color
+               
                <section class="row" id="faq">
                        <div>
-                               <!-- ~~~~~~~~~ section title + graphics  ~~~~~~~~~ -->
                                <div class="sidebar">
                                        <h2>FAQ</h2>
-                               </div><!-- /.sidebar -->
+                               </div>
 
                                <div class="main">
                                        <dl>
                                                <dt>My email program is opening at times I don't want it to open/is now my default program and I don't want it to be.</dt>
                                                        <dd>Answer coming soon.</dd>
                                        </dl>
-                               </div><!-- /.main -->
+                               </div>
                        </div>
-               </section><!-- End #faq -->
+               </section> --><!-- End #faq -->
 
 <!-- ~~~~~~~~~ Footer  ~~~~~~~~~ -->
                <footer class="row" id="footer">
                        <div>
-                               <div id="contribute">
-                                       <h4>Contribute to this guide</h4>
-                                       <ul>
-                                               <li><a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Leave feedback and suggest improvements</a></li>
-                                               <li>Email us at <a href="mailto:campaigns@fsf.org">campaigns@fsf.org</a> if you'd like to help maintain and improve this guide, or to translate it</a></li>
-                                               <li><a href="https://u.fsf.org/7w">Donate to the Free Software Foundation</a></li>
-                               </div><!-- /#contribute -->
                                <div id="copyright">
                                        <h4><a href="https://u.fsf.org/ys"><img alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png"></a></h4>
                                        <p>Copyright &copy; 2014 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. <a href="https://u.fsf.org/yr">Join.</a></p>
                <script src="http://static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
                <script src="http://static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
 
+                <!-- Piwik -->
+                <script type="text/javascript">
+                 /*
+                 @licstart The following is the entire license notice for the
+                    JavaScript code in this page.
+
+                 Copyright 2014 Matthieu Aubry
+
+                  This program is free software: you can redistribute it and/or modify
+                 it under the terms of the GNU General Public License as published by
+                 the Free Software Foundation, either version 3 of the License, or
+                 (at your option) any later version.
+
+                  This program is distributed in the hope that it will be useful,
+                 but WITHOUT ANY WARRANTY; without even the implied warranty of
+                 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+                 GNU General Public License for more details.
+
+                  You should have received a copy of the GNU General Public License
+                 along with this program.  If not, see http://www.gnu.org/licenses/.
+
+                  @licend The above is the entire license notice
+                     for the JavaScript code in this page.
+                 */
+                 var _paq = _paq || [];
+                 _paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
+                 _paq.push(["setCookieDomain", "*.www.fsf.org"]);
+                 _paq.push(["setDomains", ["*.www.fsf.org","*.www.fsf.org"]]);
+                 _paq.push(["trackPageView"]);
+                 _paq.push(["enableLinkTracking"]);
+
+                 (function() {
+                   var u=(("https:" == document.location.protocol) ? "https" : "http") + "://piwik.fsf.org/";
+                   _paq.push(["setTrackerUrl", u+"piwik.php"]);
+                   _paq.push(["setSiteId", "5"]);
+                   var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
+                   g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
+                 })();
+                </script>
+                <!-- End Piwik Code -->
+
        </body>
 </html>
-