+++ /dev/null
-#!/bin/bash
-
-#This script glues the pages together.
-
-cat head.html guide.head.html top-bar-gnu.html index.html.pre gnu-step.html rest.html footer.html > index.html
-cat head.html guide.head.html top-bar-mac.html index.html.pre mac-step.html rest.html footer.html > mac.html
-cat head.html guide.head.html top-bar-win.html index.html.pre win-step.html rest.html footer.html > windows.html
-cat head.html infographic.html.pre footer.html > infographic.html
-cat head.html next_steps.html.pre footer.html > next_steps.html
+++ /dev/null
-<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
- <footer class="row" id="footer">
- <div>
- <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 © 2014 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Datenschutzerklärung</a>. <a href="https://u.fsf.org/yr">Beitreten</a></p>
- <p><em>Version 2.0. <!--LANGUAGE translation by NAME, NAME and NAME.--> Deutsche Übersetzung von <a href="http://de.gpcf.eu" >Gabriel Pérez-Cerezo</a></em></p>
-<p>Die Bilder auf dieser Seite unterliegen einer <a href="https://creativecommons.org/licenses/by/4.0/deed.de">Creative-Commons-Namensnennung-4.0-Lizenz (oder eine neuere Version) </a> und der Rest unterliegt einer <a href="https://creativecommons.org/licenses/by-sa/4.0/deed.de">Creative-Commons-Namensnennung-Weitergabe-unter-gleichen-Bedigungen-4.0-Lizenz (oder eine neuere Version)</a>. — <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Warum diese Lizenzen?</a></p>
- <p>Lade dir den Quellcode für <a href="gnupg-guide.zip">diese Anleitung</a> und für <a href="gnupg-infographic.zip">die Infographik</a> herunter. In der Anleitung & Infographik verwendete Schriftarten: <a href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> von Pablo Impallari, <a href="http://www.google.com/fonts/specimen/Signika">Signika</a> by Anna Giedryś <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> von Omnibus-Type, <a href="http://www.thegopherarchive.com/gopher-files-hacks-pxl2000-119351.htm">PXL-2000</a> von Florian Cramer.</p>
- <p>
- <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
- rel="jslicense">
- JavaScript-Lizenzinformationen
- </a>
- </p>
- </div><!-- /#copyright -->
- <p class="credits">
- Design von <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0n/img/jplusplus.png" alt="Journalism++" /></a>
- </p><!-- /.credits -->
- </div>
- </footer><!-- End #footer -->
-
- <script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
- <script src="//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>
+++ /dev/null
-
-<!-- a div for each step -->
-<div id="step-1b" class="step">
- <div class="sidebar">
- <ul class="images">
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>
- <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>Schritt 1.b</em>Installiere das Enigmail-Plugin für dein E-Mail-Programm</h3>
- <p>
- In dem Menü von deinen Programm, klicke auf Add-ons (es könnte auch im Untermenü "Werkzeuge" sein). Vergewissere dich, dass " Erweiterungen" links ausgewählt wurde. Kannst du Enigmail sehen? Wenn ja, dann überspringe diesen Schritt.</p>
- <p>Wenn nicht, suche "Enigmail" mit Hilfe der Suchleiste. Installiere es. Starte dein E-Mail-Programm anschließend neu.</p>
- <!-- ~~~~~~~~~ Probleme? ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Ich kann das Menü nicht finden.</dt>
- <dd>
- In vielen neuen E-Mail-Programmen wird das Hauptmenü durch drei horizontale Balken dargestellt.</dd>
-
- <dt class="feedback">Fidest du keine Lösung für deine Probleme?</dt>
- <dd class="feedback">Frage uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a>.</dd>
- </dl>
- </div><!-- /.troubleshooting -->
- </div><!-- End .main -->
-</div><!-- End #step-1b .step -->
-</section><!-- End #section1 -->
+++ /dev/null
-<body>
-
- <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
-
- <header class="row" id="header">
- <div>
- <h1 style="font-size: 4.5em;" >E-Mail-Selbstverteidigung</h1>
- <!-- Language list for browsers that do not have JS enabled -->
- <ul id="languages" class="os">
- <li><a href="/en">english</a></li>
- <li><a href="/es">español</a></li>
- <li><a href="/fr">français</a></li>
- <li><a class="current" href="/de">deutsch</a></li>
- <li><a href="/pt-br">português do Brasil</a></li>
- <li><a href="/tr">türkçe</a></li>
- <li><a href="/ro">română</a></li>
- <li><a href="/ru">русский</a></li>
- <!--<li><a href="/ml">മലയാളം</a></li>-->
- <!--<li><a href="/ko">한국어</a></li>-->
- <li><a href="/ja">日本語</a></li>
- <li><a href="/el">ελληνικά</a></li>
- <!--<li><a href="/ar">العربية</a></li>-->
- </ul>
+++ /dev/null
-<!DOCTYPE html>
-<html>
- <head>
- <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-
- <title>E-Mail-Selbstverteidigung - Eine Anleitung zur Bekämpfung der Überwachung mit GnuPG</title>
- <meta name="keywords" content="GnuPG, GPG, openpgp, Überwachung, Privatsphäre, Enigmail" />
- <meta name="description" content="E-Mail-Überwachung verstößt gegen grundlegende Rechte und bedroht die Meinungsfreiheit. Diese Anleitung zeigt dir, wie du in 30 Minuten mit GnuPG verschlüsseln kannst.">
-
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css">
- <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
- <style type="text/css" >
- h1 { font-size: 4.5 em !important}
- </style>
- </head>
+++ /dev/null
-<!-- begin index.html.pre -->
-<li class="spacer">
- <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=E-Mail-Verschlüsselung%20für%20alle%20von%20%40fsf%20%23EmailSelbstverteidigung">
- #EmailSelbstverteidigung
- </a>
-</li>
-</ul>
-
-<!-- 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>
- <div style="font-size:125%"><p>E-Mail-Selbstverteidigung ist ein Projekt der Free Software Foundation. Wir setzen uns für die Rechte der Nutzer ein und unterstützen die Entwicklung von freier Software wie GnuPG, das in dieser Anleitung eingsetzt wird.</p><p><strong>
- Wir möchten Programme wie dieses so weit wie möglich verbreiten, um so vielen Leuten wie möglich den ersten Schritt zur Nutzung von freier Software zum Schutz der Privatsphäre zu erleichtern. Könntest du bitte eine Spende machen um uns zu helfen, diese Ziele zu erreichen?
- </strong></p></div>
-
- <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/donate.en.png"></a> <a href="https://u.fsf.org/yr"><img alt="Join now" src="//static.fsf.org/nosvn/enc-dev0/img/join.en.png"></a></p>
-
-</div><!-- End #fsf-intro -->
-
-<!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
-<div class="intro">
- <p>
- <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/infographic-button.png" alt="View & share our infographic →" /></a>
- Massive Überwachung verstößt gegen unsere Grundrechte und bedroht die Meinungsfreiheit. Diese Anleitung bringt dir eine einfache Selbstverteidigungsmethode bei: E-Mail-Verschlüsselung. Wenn du fertig bist, kannst du E-Mails senden und empfangen, die von Überwachungs-Agenten oder verbrechern nicht gelesen werden können.
- </p>
-
- <p>
- Auch wenn du nichts zu verbergen hast, die Verwendung von Verschlüsselung schützt die Privatsphäre deiner Kommunikationspartner und macht Überwachungssystemen das Leben schwer. Solltest du doch etwas zu verbergen haben, dies sind die selben Programme die Edward Snowden verwendet hat, um die bekannten Geheimnisse über die NSA zu teilen.
- </p>
-
- <p>
- Um Überwachung zu bekämpfen, müssen wir auch uns politisch für eine <a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">Verringerung der Anzahl der Daten, die über uns gesammelt werden</a>, aber der erste Schritt ist uns selber vor Überwachung zu schützen und sie so schwer wie möglich zu machen. Lasst uns anfangen!</p>
-
-</div>
-</div>
-
-</header><!-- End #header -->
-
-<!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
-<section class="row" id="section1">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#1</em> Installiere die Programme</h2>
- <p class="notes">
- Diese Anleitung beruht auf freier Software, sie ist transparent und jeder darf sie vervielfältigen oder eine eigene Version produzieren. Das macht es schwieriger für Überwachung als unfreie Software (wie Windows). Lerne mehr über freie Software auf <a href="https://u.fsf.org/ys">fsf.org</a>.</p>
-
- <p>Das einzige was du benötigst ist ein Computer mit einem Internetanschluss, ein E-Mail-Konto und etwa eine halbe Stunde. Du kannst dein existierendes E-Mail-Account hierfür verwenden ohne Nebenwirkungen.</p>
- <p>
- Auf den meisten GNU/Linux-Systemen ist GnuPG bereits installiert, also musst du es nicht herunterladen. Bevor du GnuPG konfigurierst, brauchst du ein E-Mail-Programm. Bei den meisten GNU/Linux distributionen kann man eine Version des Programms Thunderbird installieren. E-Mail-Programme sind eine andere Art auf E-Mails zuzugreifen, die ähnlich wie Webmail funktioniert, aber wesentlich mehr Funktionen besitzt.</p>
- <p>Wenn du bereits eines hast, dann gehe zum <a href="#step-1b">Schritt 1.b</a>.</p>
-
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div class="main">
- <h3><em>Schritt 1.a</em> Konfiguriere dein E-Mail-Account (wenn es nicht schon getan wurde).</h3>
- <p>Öffne dein E-Mail -Programm und folge dem Assistenten.</p>
-
- <!-- ~~~~~~~~~ Probleme? ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Was ist ein Assistent?</dt>
- <dd>
- Ein Assistent besteht aus mehreren Fenstern, die erscheinen und es einfach machen etwas am Computer zu verändern, wie ein Programm zu installieren.</dd>
- <dt>Mein E-Mail-Programm kann keine E-Mails empfangen.</dt>
- <dd>Frage erst andere Leute die dein System benutzen, suche dann im Internet.</dd>
- <dt class="feedback">Fidest du keine Lösung für deine Probleme?</dt>
- <dd class="feedback">Frage uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a>.</dd>
- </dl>
- </div><!-- /.troubleshooting -->
-
- </div><!-- End .main -->
- </div><!-- End #step1-a .step -->
+++ /dev/null
-
- <body>
-
- <header class="row centered" id="header">
- <div>
- <p class="back">← Lies die <a href="index.html">Anleitung</a></p>
- <h3><a href="https://fsf.org/share?u=https://u.fsf.org/zc&t=Wie%20asymmetrische%20Verschlüsselung%20funktioniert.%20Infographik%20von%20%40fsf%20%23EmailSelbstverteidigung">Teile unsere Infographik</a> mit dem Hashtag #EmailSelbstverteidigung</h3>
-
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/de/gnupg-infographic.de.png" alt="Teile unsere Infographik!" /></p>
-
- <p><a href="//static.fsf.org/nosvn/enc-dev0/gnupg-infographic.zip">Hole dir den Quellcode</a> von der Infographik</p>
- <p class="back">← Lies die <a href="index.html">Anleitung</a></p>
- </div>
- </header><!-- End #header -->
-
+++ /dev/null
-#!/bin/bash
-
-## assemble-all-pages -- generate a set of HTML pages with variable parts
-# for emailselfdefense.fsf.org
-
-## Synopsis: assemble-all-pages
-
-## Description
-
-# Each page is built from a template and one or several includes, as usual;
-# in addition, several versions of a page can be built from a single
-# template which contains all the variable parts, by deleting irrelevant
-# text.
-
-# The templates have inclusion markers (similar to SSI directives, except
-# for the lack of "#") to indicate where the constant parts are to be
-# inserted, and deletion markers to identify the borders of each deletion
-# and indicate which page(s) the text between those borders belongs to.
-
-# The script processes all the templates in the working directory and the
-# pages are created in the parent directory.
-
-# Ideally, any modifications should be done to the templates or includes,
-# not to the final pages.
-
-# Templates: confirmation.t.html
-# index.t.html (contains variable parts for mac and windows)
-# infographic.t.html
-# next_steps.t.html
-
-# Includes: footer.html
-# head.html (contains 2 alternate sets of keywords)
-# javascript.html
-# translist.html
-
-## Graphic-user-interface howto
-
-# - Place the script in the same directory as the templates.
-# - Display this directory in the file browser (do not just unfold the parent
-# directory) and double-click on the script.
-
-# And if anything goes wrong, you can do a git reset, right? ;-)
-
-# ===========================================================================
-
-set -e
-set -o pipefail
-
-function close_term () {
- printf '\n%s' '*** Close the terminal window or press Return.'; read OK
- test -z "$OK" && exit $1
-}
-
-# Create temporary files.
-names=$(mktemp -t aap.XXXXXX) || close_term 1
-list=$(mktemp -t aap.XXXXXX) || close_term 1
-before=$(mktemp -t aap.XXXXXX) || close_term 1
-after=$(mktemp -t aap.XXXXXX) || close_term 1
-trap 'rm -f "$names" "$list" "$before" "$after"' EXIT
-
-# List all the templates in the working directory.
-if ls *.t.html > $names 2>/dev/null; then
- sed -i 's,\.t\.html$,,' $names
-else
- echo "*** There is no template in this directory." && close_term 1
-fi
-
-## Add the includes to the templates.
-
-while read name; do
- # Make sure there is a blank line before the first include, otherwise
- # it will not be added properly.
- sed '1i\\n' $name.t.html > ../$name.html
- # List the includes.
- grep '^<!-- include virtual="' ../$name.html |
- sed 's%^.*include virtual="\([^"]\+\).*$%\1%' > $list
- # Add the includes.
- while read include; do
- sed "1,/^<!-- include virtual=\"$include\"/!d" ../$name.html > $before
- sed "1,/^<!-- include virtual=\"$include\"/d" ../$name.html > $after
- if [ -f "$include" ]; then
- cat $before $include $after > ../$name.html
- else
- echo "$include is missing." && close_term 1
- fi
- sed -i "/^<!-- include virtual=\"$include\"/d" ../$name.html
- done < $list
-done < $names
-
-## Create mac.html and windows.html from index.html.
-
-cp ../index.html ../mac.html
-cp ../index.html ../windows.html
-# add them to the list of page names.
-echo 'mac' >> $names
-echo 'windows' >> $names
-
-## Remove the irrelevant parts.
-
-while read name ; do
- # Find out which deletions apply.
- grep '^<!-- START DELETION' ../$name.html |
- grep -v "$name" > $list || true
- sed -i 's%^<!-- START DELETION \([0-9][0-9]\),.*$%\1%' $list
- # Delete.
- while read deletion; do
- sed -i "/^<!-- START DELETION $deletion/, \
- /^<!-- END DELETION $deletion/d" ../$name.html
- done < $list
- # Remove the markers and any extra blank lines at the end of the page.
- sed -i '/^<!-- [A-Z]* DELETION/d' ../$name.html
- sed -i ':a /^\n*$/ {$d; N; ba}' ../$name.html
-done < $names
-
-close_term 0
+++ /dev/null
-<!-- include virtual="head.html" -->
-
- <header class="row centered" id="header">
- <div>
-
-
-
-<p><strong>Bitte überprüfe jetzt deine E-Mails wegen des Bestätigungslinks. Danke, dass du unserer Liste beigetreten bist!</strong></p>
-
-<p>Wenn du den Bestätigungslink nicht empfängst, schicke uns eine E-Mail an info@fsf.org, damit du manuell hinzugefügt wirst.</p>
-
-
-<br /><p><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/section3-try-it-out.png" alt="Try it out." /></p><br />
-
-<p>Folge uns bei Microblogging-Diensten, um tagesaktuelle Updates zu erhalten:</p>
-<p style="font-size:150%">
- <a href="https://status.fsf.org/fsf">
- <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"
- class="share-logo" alt="[GNU Social]" />
- GNU Social
- </a> |
- <a href="http://microca.st/fsf">
- <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"
- class="share-logo" alt="[Pump.io]" />
- Pump.io
- </a> |
- <a href="https://www.twitter.com/fsf">Twitter</a>
-</p>
-<small>
- <p>
- <a href="https://www.fsf.org/twitter">
- Lies, warum GNU Social und Pump.io besser sind als Twitter.
- </a>
- </p>
-</small>
-<hr />
- <p class="back" style="font-size:150%">← Zurück zu <a href="index.html">E-Mail-Selbstverteidigung</a></p>
- </div>
- </header><!-- End #header -->
-
-<!-- include virtual="footer.html" -->
-
-<!-- include virtual="javascript.html" -->
+++ /dev/null
-<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
- <footer class="row" id="footer">
- <div>
- <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 © 2014 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Datenschutzerklärung</a>. <a href="https://u.fsf.org/yr">Beitreten</a></p>
- <p><em>Version 3.0. Deutsche Übersetzung und Review durch <a href="http://fiff.de">FIfF e.V.</a> (<fiff@fiff.de>) & weitere, basierend auf einer Übersetzung von <a href="http://de.gpcf.eu" >Gabriel Pérez-Cerezo</a>. <a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">Quelltext des GnuPG-Roboters Edward von Josh Drake <zamnedix@gnu.org> verfügbar unter der GNU General Public License.</a></em></p>
-<p>Die Bilder auf dieser Seite sind lizenziert unter einer <a href="https://creativecommons.org/licenses/by/4.0/deed.de">Creative Commons Namensnennung 4.0 International Lizenz</a> und der Rest ist lizenziert unter einer <a href="https://creativecommons.org/licenses/by-sa/4.0/deed.de">Commons Namensnennung - Weitergabe unter gleichen Bedingungen 4.0 International Lizenz</a>. — <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Warum diese Lizenzen?</a></p>
- <p>Lade die Quellen für <a href="emailselfdefense_source.zip">diese Anleitung</a> herunter. Schriftarten in Anleitung & Infografik: <a href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> von Pablo Impallari, <a href="http://www.google.com/fonts/specimen/Signika">Signika</a> von Anna Giedryś, <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> von Omnibus-Type, <a href="http://www.thegopherarchive.com/gopher-files-hacks-pxl2000-119351.htm">PXL-2000</a> von Florian Cramer.</p>
- <p>
- <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
- rel="jslicense">
- JavaScript-Lizenzinformationen
- </a>
- </p>
- </div><!-- /#copyright -->
- <p class="credits">
- Design von <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" alt="Journalism++" /></a>
- </p><!-- /.credits -->
- </div>
- </footer><!-- End #footer -->
+++ /dev/null
-<!DOCTYPE html>
-<html>
- <head>
- <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-
- <title>E-Mail-Selbstverteidigung - eine Anleitung zur Bekämpfung der Überwachung durch Verschlüsselung mit GnuPG</title>
-
-<!-- START DELETION 90, KEEP IN index mac windows next_steps -->
- <meta name="keywords" content="GnuPG, GPG, openpgp, Überwachung, Privatsphäre, E-Mail, Enigmail" />
-<!-- END DELETION 90 -->
-<!-- START DELETION 91, KEEP IN infographic confirmation -->
- <meta name="keywords" content="GnuPG, GPG, Privatsphäre, E-Mail, Enigmail" />
-<!-- END DELETION 91 -->
- <meta name="description" content="Massenüberwachung verstößt gegen unsere Grundrechte und bedroht die freie Meinungsäußerung. Diese Anleitung zeigt dir in 30 Minuten, wie du dich mit Hilfe von GnuPG selbst verteidigen kannst." />
-
- <meta name="viewport" content="width=device-width, initial-scale=1" />
- <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />
- <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
-<!-- START DELETION 92, KEEP IN infographic -->
- <style type="text/css" >
- h1 { font-size: 4.5 em !important}
- </style>
-<!-- END DELETION 92 -->
- </head>
- <body>
-
+++ /dev/null
-<!-- include virtual="head.html" -->
-
-<!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
-
- <header class="row" id="header">
- <div>
- <h1>E-Mail-Selbstverteidigung</h1>
-
-<!-- include virtual="translist.html" -->
-
- <ul id="menu" class="os">
-<!-- START DELETION 01, KEEP IN index -->
-<li class="spacer"><a href="index.html" class="current">GNU/Linux</a></li>
-<li><a href="mac.html">Mac OS</a></li>
-<li><a href="windows.html">Windows</a></li>
-<!-- END DELETION 01 -->
-<!-- START DELETION 02, KEEP IN mac -->
-<li class="spacer"><a href="index.html">GNU/Linux</a></li>
-<li><a href="mac.html" class="current">Mac OS</a></li>
-<li><a href="windows.html">Windows</a></li>
-<!-- END DELETION 02 -->
-<!-- START DELETION 03, KEEP IN windows -->
-<li class="spacer"><a href="index.html">GNU/Linux</a></li>
-<li><a href="mac.html">Mac OS</a></li>
-<li><a href="windows.html" class="current">Windows</a></li>
-<!-- END DELETION 03 -->
- <li class="spacer">
- <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=E-Mail-Verschlüsselung für alle via %40fsf">
- Share
- </a>
- </li>
- </ul>
-
- <!-- ~~~~~~~~~ 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>
- <div class="fsf-emphasis">
- <p>
- Wir kämpfen für die Rechte von Computernutzerinnen und -nutzern und fördern die Entwicklung freier (wie in Freiheit) Software. Widerstand gegen die Massenüberwachung ist sehr wichtig für uns.
- </p>
- <p>
- <strong>
- Wir möchten diese Anleitung in weitere Sprachen übersetzen und eine Version zu Verschlüsselung auf mobilen Geräten erstellen. Bitte spende und helf Menschen auf der ganzen Welt den ersten Schritt zu machen, ihre Privatsphäre mit freier Software zu schützen.
- </strong>
- </p>
- </div>
-
- <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Spenden" src="//static.fsf.org/nosvn/enc-dev0/img/de/donate.png" /></a></p>
-
- </div><!-- End #fsf-intro -->
-
- <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
- <div class="intro">
- <p>
- <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/de/infographic-button.png" alt="Sieh dir unsere Infografik an und verbreite sie weiter →" /></a>
- Massenüberwachung verstößt gegen unsere Grundrechte und bedroht die freie Meinungsäußerung. Diese Anleitung bringt dir eine einfache Selbstverteidigungsmethode bei: E-Mail-Verschlüsselung. Wenn du fertig bist, kannst du E-Mails senden und empfangen, die von Überwachern oder Kriminellen, die deine E-Mails abfangen, nicht gelesen werden können. Alles, was du brauchst, ist ein Computer mit einer Internetverbindung, ein E-Mail-Konto und eine halbe Stunde Zeit.</p>
-
-<p>Auch wenn du nichts zu verbergen hast, die Verwendung von Verschlüsselung schützt die Privatsphäre der Menschen, mit denen du kommunizierst, und macht den Systemen der Massenüberwachung das Leben schwer. Wenn du doch etwas wichtiges verbergen möchtest, bist du in guter Gesellschaft: Dies sind die gleichen Werkzeuge, die Edward Snowden benutzt hat, um seine bekannten Geheimnisse über die NSA zu verbreiten.</p>
-
-<p>Sich gegen Überwachung zu wehren, erfordert neben der Verwendung von Verschlüsselung den politischen Kampf dafür, dass <a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">weniger Daten über uns gesammelt werden</a>. Aber der erste Schritt ist es, dich selber zu schützen und die Überwachung deiner Kommunikation so schwer wie möglich zu machen. Los geht's!</p>
-
- </div><!-- End .intro -->
-
- </div>
- </header><!-- End #header -->
-
-<!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
- <section class="row" id="section1">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#1</em> Installiere die Programme</h2>
-<!-- START DELETION 04, KEEP IN index -->
-<p class="notes">Diese Anleitung basiert auf freier Software. Freie Software ist transparent und kann von allen kopiert und angepasst werden. Dadurch ist sie sicherer vor Überwachung als nicht-freie Software (wie Windows). Lerne mehr über freie Software auf <a href="https://u.fsf.org/ys">fsf.org</a>.</p>
-
-<p>Auf den meisten GNU/Linux-Systemen ist GnuPG bereits installiert, also musst du es nicht herunterladen. Bevor du GnuPG konfigurierst, brauchst du jedoch ein E-Mail-Programm. Bei den meisten GNU/Linux-Distributionen kann man eine freie Version des Programms Thunderbird installieren. E-Mail-Programme sind eine weitere Art auf E-Mail-Konten zuzugreifen, die ähnlich wie Webmail funktioniert, aber mehr Funktionen bieten.</p>
-<!-- END DELETION 04 -->
-<!-- START DELETION 05, KEEP IN mac -->
-<p class="notes">Diese Anleitung basiert auf freier Software. Freie Software ist transparent und kann von allen kopiert und angepasst werden. Dadurch ist sie sicherer vor Überwachung als nicht-freie Software (wie Mac OS). Um deine Freiheit zu verteidigen und dich vor Überwachung zu schützen, empfehlen wir dir, zu einem freien Betriebsystem wie GNU/Linux zu wechseln. Lerne mehr über freie Software auf <a href="https://u.fsf.org/ys">fsf.org</a>.</p>
-<!-- END DELETION 05 -->
-<!-- START DELETION 11, KEEP IN windows -->
-<p class="notes">Diese Anleitung basiert auf freier Software. Freie Software ist transparent und kann von allen kopiert und angepasst werden. Dadurch ist sie sicherer vor Überwachung als nicht-freie Software (wie Windows). Um deine Freiheit zu verteidigen und dich vor Überwachung zu schützen, empfehlen wir dir, zu einem freien Betriebsystem wie GNU/Linux zu wechseln. Lerne mehr über freie Software auf <a href="https://u.fsf.org/ys">fsf.org</a>.</p>
-<!-- END DELETION 11 -->
-<!-- START DELETION 12, KEEP IN mac windows -->
-
-<p>Zu Beginn brauchst du ein E-Mail-Programm. In dieser Anleitung wird eine freie Version des Programms Thunderbird verwendet. E-Mail-Programme sind eine weitere Art auf E-Mail-Konten zuzugreifen, die ähnlich wie Webmail funktioniert, aber mehr Funktionen bieten.</p>
-<!-- END DELETION 12 -->
-
- <p>Wenn du bereits ein E-Mail-Programm hast, kannst du zu <a href="#step-1b">Schritt 1.b</a> springen.</p>
-</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-1a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Schritt 1.a</em> Konfiguriere dein E-Mail-Programm für dein Konto</h3>
- <p>Öffne dein E-Mail-Programm und folge dem Assistenten, der es für dein E-Mail-Konto konfiguriert.</p>
-
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Der Assistent startet nicht</dt>
- <dd>Du kannst den Assistenten selbst starten. Die Bezeichnung des Menuepunktes haengt vom verwendeten Mail-Programm ab. Die Option "Neue E-Mail-Adresse..." oder "Existierendes E-Mail-Konto..." befindet sich im Hauptmenue des Programms, unter "Neu" oder etwas aehnlichem.</dd>
- <dt>Der Assistent findet mein E-Mail-Konto nicht oder lädt keine E-Mails herunter.</dt>
- <dd>Bevor du im Web suchst empfehlen wir, andere Menschen, die das gleiche E-Mail-System benutzen, nach den richtigen Einstellungen zu fragen.</dd>
- <dt class="feedback">Findest du keine Lösung für dein Problem?</dt>
- <dd class="feedback">Sag uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a> Bescheid.</dd>
- </dl>
- </div><!-- /.troubleshooting -->
-
- </div><!-- End .main -->
- </div><!-- End #step1-a .step -->
-
-<!-- START DELETION 06, KEEP IN mac -->
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-1b" class="step">
- <div class="main">
-
- <h3><em>Schritt 1.b</em> Hol dir GnuPG, indem du GPGTools herunterlädst</h3>
-
- <p>GPGTools ist ein Software-Paket, das GnuPG enthält. <a href="https://gpgtools.org/#gpgsuite">Lade es herunter</a>, installiere es und wähle dabei immer die vorgeschlagenen Standard-Optionen. Nachdem es installiert wurde, kannst du alle Fenster schließen, die es geöffnet hat.</p>
-
- </div><!-- End .main -->
-</div><!-- End #step1-b .step -->
-<!-- END DELETION 06 -->
-<!-- START DELETION 07, KEEP IN windows -->
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-1b" class="step">
- <div class="main">
-
- <h3><em>Schritt 1.b</em> Hol dir GnuPG, indem du GPG4Win herunterlädst</h3>
-
- <p>GPG4Win ist ein Software-Paket, das GnuPG enthält. <a href="https://www.gpg4win.org">Lade es herunter</a>, installiere es und wähle dabei immer die vorgeschlagenen Standard-Optionen. Nachdem es installiert wurde, kannst du alle Fenster schließen, die es geöffnet hat.</p>
-
- </div><!-- End .main -->
-</div><!-- End #step1-b .step -->
-<!-- END DELETION 07 -->
-<!-- START DELETION 08, KEEP IN mac windows -->
-
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-1c" class="step">
- <div class="sidebar">
- <ul class="images">
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/step1b-01-tools-addons.png" alt="Step 1.C: Tools -> Add-ons" /></li>
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/step1b-02-search.png" alt="Step 1.C: Search Add-ons" /></li>
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/step1b-03-install.png" alt="Step 1.C: Install Add-ons" /></li>
- </ul>
- </div><!-- /.sidebar -->
- <div class="main">
-
- <h3><em>Schritt 1.c</em> Installiere das Enigmail-Plugin für dein E-Mail-Programm</h3>
-<!-- END DELETION 08 -->
-<!-- START DELETION 09, KEEP IN index -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-1b" class="step">
- <div class="sidebar">
- <ul class="images">
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/step1b-02-search.png" alt="Step 1.B: Search Add-ons" /></li>
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/step1b-03-install.png" alt="Step 1.B: Install Add-ons" /></li>
- </ul>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Schritt 1.b</em> Installiere das Enigmail-Plugin für dein E-Mail-Programm</h3>
-<!-- END DELETION 09 -->
-
- <p>Klicke im Menü deines E-Mail-Programmes auf Add-ons (es könnte auch im Untermenü Extras sein). Vergewissere dich, dass auf der linken Seite Erweiterungen ausgewählt ist. Kannst du Enigmail sehen? Wenn ja, dann überspringe diesen Schritt.</p>
- <p>Wenn nicht, suche "Enigmail" mit Hilfe der Suchleiste oben rechts. Installiere es und starte dein E-Mail-Programm anschließend neu.</p>
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Ich kann das Menü nicht finden.</dt>
- <dd>In vielen neuen E-Mail-Programmen wird das Hauptmenü durch drei horizontale Balken dargestellt.</dd>
-
- <dt class="feedback">Findest du keine Lösung für dein Problem?</dt>
- <dd class="feedback">Sag uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a> Bescheid.</dd>
- </dl>
- </div><!-- /.troubleshooting -->
- </div><!-- End .main -->
- </div><!-- End #step-1(b|c) .step -->
- </div>
- </section><!-- End #section1 -->
-
-<!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
- <section class="row" id="section2">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#2</em> Erstelle deine Schlüssel</h2>
- <p>Um GnuPG zu verwenden, benötigt man einen öffentlichen und einen privaten Schlüssel (beide bilden ein Schlüsselpaar). Jeder Schlüssel ist eine sehr große Zahl und ist einzigartig. Beide Schlüssel sind mit einer speziellen mathematischen Funktion verbunden.</p>
-
-<p>Dein öffentlicher Schlüssel ist nicht wie ein Hausschlüssel, da er im Internet auf einem Schlüsselserver gespeichert wird. Die Leute können ihn so herunterladen und ihn benutzen, wenn sie dir verschlüsselte E-Mails verschicken. Man kann sich den Schlüsselserver wie ein Telefonbuch vorstellen, von wo Leute, die dir eine Verschlüsselte E-Mail schicken möchten, deinen öffentlichen Schlüssel herunterladen können.</p>
-
-<p>Dein privater Schlüssel ist eher wie ein Hausschlüssel, weil ihn niemand außer dir besitzen darf. Der private Schlüssel wird eingesetzt, wenn du E-Mails entschlüsselst.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-2a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Schritt 2.a</em> Erstelle ein Schlüsselpaar</h3>
- <p>Der Enigmail-Assistent startet möglicherweise automatisch, falls nicht, wähle Enigmail → Enigmail-Assistent im Menü deines E-Mail-Programms aus. Du musst den Text im nächsten Fenster nicht unbedingt lesen, wenn du nicht willst, aber es ist eine gute Idee, die Texte der späteren Schritte des Assistenten zu lesen. Nutze die Standard-Optionen, außer bei folgenden Punkten:</p>
- <ul>
- <li>Im Schritt "Verschlüsselung", wähle "Verschlüssle alle meine Nachrichten, weil mir meine Privatsphäre wichtig ist"</li>
- <li>Im Schritt "Unterschreiben", wähle "Meine Nachrichten sollen nicht standardmäßig unterschrieben werden"</li>
- <li>Im Schritt "Schlüsselauswahl", wähle "Ich möchte ein neues Schlüsselpaar erzeugen"</li>
- <li>Im Schritt "OpenPGP-Schlüssel erzeugen" solltest du ein starkes Passwort verwenden! Dein Passwort sollte mindestens 12 Zeichen lang sein und mindestens je einen Kleinbuchstaben und Großbuchstaben und mindestens eine Zahl oder ein Satzzeichen enthalten. Vergiss das Passwort nicht, sonst ist diese gesamte Arbeit umsonst!
- </li>
- </ul>
- <p class="notes">Das Programm wird einige Minuten brauchen, um den nächsten Schritt "Schlüsselerzeugung" abzuschließen. Während du wartest, solltest du etwas anderes mit deinem Computer tun, wie einen Film anschauen oder im Web surfen. Je mehr du deinen Computer in dieser Zeit nutzt, desto schneller wird der Schlüssel generiert.</p>
- <p>Wenn der Schritt "Enigmail-Bestätigung" kommt, klicke auf "Zertifikat erzeugen" und speichere es an einem sicheren Ort auf deinem Computer (wir empfehlen einen Ordner namens "Widerrufszertifikat" in deinem Home-Verzeichnis). Du wirst mehr über das Widerrufszertifikat in <a href="#section5">Sektion 5</a> lernen.</p>
-
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Ich kann das Enigmail-Menü nicht finden.</dt>
- <dd>In vielen neuen E-Mail-Programmen wird das Hauptmenü durch drei horizontale Balken dargestellt. Enigmail könnte in einer Sektion namens Tools sein.</dd>
-
-<!-- START DELETION 10, KEEP IN index -->
- <dt>Der assistent kann GnuPG nicht finden.</dt>
-
- <dd>Öffne das Programm, das du zur Installation von Software benutzt, suche nach GnuPG und installiere es. Starte dann den Assistenten unter Enigmail → Enigmail-Assistent neu.</dd>
-<!-- END DELETION 10 -->
- <dt class="feedback">Findest du keine Lösung für dein Problem?</dt>
- <dd class="feedback">Sag uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a> Bescheid.</dd>
- </dl>
- </div><!-- /.troubleshooting -->
- </div><!-- End .main -->
- </div><!-- End #step-2a .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-2b" class="step">
- <div class="main">
- <h3><em>Schritt 2.b</em> Lade deinen öffentlichen Schlüssel auf einen Schlüsselserver</h3>
- <p>Wähle Enigmail → Schlüssel verwalten... im Menü aus.</p>
-<p>Rechtsklicke auf deinen Schlüssel und klicke dann auf Auf Schlüssel-Server hochladen.... Wähle dazu den voreingestellten Schlüsselserver im Pop-up.</p>
-<p class="notes"> Jetzt kann jemand, der dir eine verschlüsselte Nachricht übermitteln möchte, deinen Schlüssel vom Internet herunterladen.</p>
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Der Fortschrittsbalken bewegt sich nicht.</dt>
- <dd>Schließe das Pop-Up, überprüfe deine Internetverbindung und probiere es noch einmal. Wenn das nicht funktioniert, versuche es noch einmal und wähle einen anderen Schlüsselserver.</dd>
-<dt>Mein Schlüssel taucht nicht in der Liste auf.</dt>
- <dd>Probiere, auf das Feld "Standardmäßig alle Schlüssel anzeigen" zu klicken.</dd>
-
- <dt class="feedback">Findest du keine Lösung für dein Problem?</dt>
- <dd class="feedback">Sag uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a> Bescheid.</dd>
-
- </dl>
- </div><!-- /.troubleshooting -->
- </div><!-- End .main -->
- </div><!-- End #step-2a .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="terminology" class="step">
- <div class="main">
- <h3>GnuPG, OpenPGP, was?</h3>
- <p>Die Begriffe GnuPG, GPG, GNU Privacy Guard, OpenPGP und PGP werden oft verwendet, um das gleiche zu bezeichnen. Technisch gesehen, ist OpenPGP (Pretty Good Privacy) der Verschlüsselungsstandard und GNU Privacy Guard (abgekürzt GPG oder GnuPG) das Programm, dass diesen Standard umsetzt. Enigmail ist eine Erweiterung für dein E-Mail-Programm und fungiert als Schnittstelle zu GnuPG.</p>
- </div><!-- End .main -->
- </div><!-- End #terminology.step-->
-
-
- </div>
- </section><!-- End #section2 -->
-
-<!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
- <section class="row" id="section3">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#3</em> Probier es aus!</h2>
- <p>Jetzt wirst du mit einem Programm namens Edward kommunizieren, das weiß, wie man E-Mails verschlüsselt. Das sind, abgesehen von den gekennzeichneten Ausnahmen, die gleichen Schritte, wie wenn du mit einer realen, lebenden Person kommunizierst.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Schritt 3.a</em> Schick Edward deinen öffentlichen Schlüssel</h3>
- <p>Dies ist ein spezieller Schritt, den du nicht machen musst, wenn du mit echten Menschen kommunizierst. Gehe im Menü deines E-Mail-Programms auf Enigmail → Schlüssel verwalten. Du solltest deinen Schlüssel in der Liste sehen, die erscheint. Klicke mit der rechten Maustaste auf deinen Schlüssel und wähle dann "Öffentliche Schlüssel per E-Mail senden". Dies erstellt eine neue Nachricht, so als hättest du auf Verfassen geklickt.</p>
-
-<p>Schreibe die Nachricht an <a href="mailto:edward-de@fsf.org" >edward-de@fsf.org</a>. Schreibe mindestens ein Wort in den Betreff und in den Text der E-Mail.</p>
-
-<p>Unten rechts im E-Mail-Verfassen-Fenster sollte ein gelbes Schlüsselsymbol sein. Das bedeutet, dass die Verschlüsselung aktiviert ist. Allerdings wollen wir, dass diese besondere Nachricht an Edward nicht verschlüsselt ist. Klicke auf den Schlüssel um die Verschlüsselung auszuschalten. Der Schlüssel sollte grau werden (der blaue Kreis weisst darauf hin, dass du die Standardeinstellung abgeändert hast). Sobald die Verschlüsselung aus ist, drücke Senden.</p>
-
-<p class="notes">Es könnte sein, dass Edward einige Minuten braucht, um zurückzuschreiben. Lese derweil die Sektion <a href="#section5">Nutze es richtig</a>. Gehe weiter zum nächsten Schritt, wenn er geantwortet hat. Ab hier tust du das gleiche, wie wenn du mit einer normalen Person kommunizierst.</p>
-
-<p>Wenn du Edwards Antwort öffnest, könnte Enigmail dich auffordern dein Passwort einzugeben, bevor mit deinem privaten Schlüssel die Antwort entschlüsselt wird.</p>
-
- </div><!-- End .main -->
- </div><!-- End #step-3a .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3b" class="step">
- <div class="main">
- <h3><em>Schritt 3.b</em> Sende eine verschlüsselte Test-E-Mail</h3>
- <p>Schreibe eine neue E-Mail in Deinem E-Mail-Programm an edward-de@fsf.org. Schreibe "Verschlüsselungstest" oder etwas ähnliches in den Betreff und irgendetwas in den Text der Nachricht.</p>
- <p>Das Icon mit dem Schlüssel unten rechts im Fenster der E-Mail sollte gelb sein. Das bedeutet die Verschlüsselung ist aktiviert. Dies wird ab jetzt deine Standardeinstellung sein.</p>
- <p class="notes">Neben dem Schlüssel siehst du das Bild eines Stiftes. Das Anklicken dieses Symbols veranlasst Enigmail, eine spezielle eindeutige Unterschrift auf der Basis deines privaten Schlüssels zu deiner Nachricht hinzuzufügen. Dies ist ein anderes Verfahren als die Verschlüsselung, das du im Rahmen dieser Anleitung nicht benutzten musst.</p>
- <p>Drücke auf Senden. Enigmail wird eine Meldung "Nicht gefundene Empfänger" zeigen.</p>
-
- <p>Um eine E-Mail an Edward zu verschlüsseln, benötigst du seinen öffentlichen Schlüssel, also muss Enigmail ihn jetzt von einem Schlüsselserver herunterladen. Klicke auf "Fehlende Schlüssel herunterladen", wähle den ersten (Schlüssel-ID C09A61E8) und klicke dann auf OK. Klicke im nächsten Pop-up-Fenster wieder auf OK.</p>
-
- <p>Jetzt bist du zurück beim Dialog "Nicht gefundene Empfänger". Wähle den Kasten vor Edwards Schlüssel an und klicke auf Absenden. Sollte die E-Mail nicht automatisch versendet werden, kannst du jetzt auf Senden drücken.</p>
-
- <p class="notes">Da du die E-Mail mit Edwards öffentlichem Schlüssel verschlüsselt hast, braucht man Edwards privaten Schlüssel, um die E-Mail entschlüsseln zu können. Nur Edward besitzt seinen privaten Schlüssel, also kann niemand außer ihm — nicht einmal du — die E-Mail entschlüsseln.</p>
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Enigmail kann Edwards Schlüssel nicht finden.</dt>
- <dd>Schließe alle Pop-ups, die aufgetaucht sind, nachdem du auf Senden geklickt hast. Vergewissere dich, dass du mit dem Internet verbunden bist, und versuche es noch einmal. Wenn dies nicht funktioniert, wiederhole das Vorgehen und wähle dabei einen anderen Schlüsselserver aus.</dd>
- <dt class="feedback">Findest du keine Lösung für dein Problem?</dt>
- <dd class="feedback">Sag uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a> Bescheid.</dd>
- </dl>
- </div><!-- /.troubleshooting -->
- </div><!-- End .main -->
- </div><!-- End #step-3b .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-headers_unencrypted" class="step">
- <div class="main">
- <h3><em>Wichtig:</em> Der Betreff wird nicht verschlüsselt</h3>
- <p>Auch wenn du die E-Mail verschlüsselst, bleibt der Betreff unverschlüsselt, also solltest du dort keine vertraulichen Informationen hineinschreiben. Die Sender- und Empfängeradressen werden ebenfalls nicht verschlüsselt und können deshalb von einem Überwachungssystem gelesen werden. Wenn du Anhänge versendest, wird Enigmail dir anbieten, sie zu verschlüsseln.</p>
- </div><!-- End .main -->
- </div><!-- End #step-headers_unencrypted .step-->
-
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3c" class="step">
- <div class="main">
- <h3><em>Schritt 3.c</em> Empfange eine Antwort</h3>
- <p>Wenn Edward deine E-Mail empfangen hat, entschlüsselt er sie mit seinem privaten Schlüssel. Dann wird er deinen öffentlichen Schlüssel verwenden (den du ihm in <a href="#step-3a">Schritt 3.A</a> geschickt hast), um seine Antwort an dich zu verschlüsseln.</p>
- <p class="notes">Edward braucht vermutlich zwei, drei Minuten, um zu antworten. In der Zwischenzeit könntest du vorspringen und die Rubrik <a href="#section5">Nutze es richtig</a> lesen.</p>
- <p>Wenn du Edwards E-Mail bekommst und sie öffnest, erkennt Enigmail automatisch, dass sie mit deinem öffentlichen Schlüssel verschlüsselt wurde, und wird dann deinen privaten Schlüssel benutzen, um sie zu entschlüsseln.</p>
- <p>Beachte die Leiste mit Informationen über Edwards Schlüssel, die über der Nachricht eingeblendet wird.</p>
- </div><!-- End .main -->
- </div><!-- End #step-3c .step -->
-
-<!-- STEP 3D IS COMMENTED OUT UNTIL WE FIND A WAY TO VALIDATE SIGNATURES
- <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>
- </div>-->
- </div>
- </section><!-- End #section3 -->
-
-
-<!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
- <section class="row" id="section4">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#4</em> Verstehe das Web of Trust</h2>
- <p>E-Mail-Verschlüsselung ist zwar eine leistungsfähige Technologie, sie hat aber eine Schwäche: Sie benötigt eine Methode zur Überprüfung, ob ein öffentlicher Schlüssel tatsächlich der angegebenen Person gehört. Ansonsten gäbe es keine Möglichkeit, eine Angreiferin davon abzuhalten, Schlüssel mit dem Namen deines Freundes zu erstellen und sich als dein Freund auszugeben. Aus diesem Grund haben die Programmierer freier Software, die E-Mail-Verschlüsselung erfunden haben, Signaturen und das Web of Trust erfunden.</p>
-
-<p>Wenn du den Schlüssel von jemandem signierst, dann sagst du öffentlich, dass du glaubst, dass der Schlüssel tatsächlich dieser Person gehört und nicht einem Betrüger. Leute, die deinen öffentlichen Schlüssel benutzen, können sehen, wie viele Signaturen er erhalten hat. Wenn du GnuPG einige Jahre lang verwendet hast, kannst du hunderte Signaturen haben. Das Web of Trust ist eine Konstellation aller GnuPG-Nutzer, die durch Signaturenketten zu einem riesigen Netz verbunden sind. Je mehr Signaturen ein Schlüssel hat und je mehr Signaturen die Schlüssel derjenigen, die unterschrieben haben, erhalten haben, desto vertrauenswürdiger ist dieser Schlüssel.</p>
-
-<p>Öffentliche Schlüssel werden normalerweise anhand ihres Fingerabdrucks identifiziert, einer Zeichenkette wie F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (für Edwards Schlüssel). Sehen kannst du den Fingerabdruck deines öffentlichen Schlüssels – und anderer öffentlicher Schlüssel, die du gespeichert hast, indem du zu Enigmail → Schlüssel verwalten im Menü deines E-Mail-Programms gehst und dann mit der rechten Maustaste auf den Schlüssel klickst und die Schlüsseleigenschaften auswählst. Es ist sinnvoll, deinen Fingerabdruck immer weiterzugeben, wenn du anderen deine E-Mail-Adresse mitteilst, so dass diese Menschen kontrollieren können, ob sie deinen richtigen Schlüssel von einem Schlüsselserver herunterladen.</p>
-
-<p class="notes">Du wirst sehen, dass man sich auch über die Schlüssel-ID auf öffentliche Schlüssel bezieht, dabei handelt es sich einfach um die letzten 8 Zeichen des Fingerabdrucks, z.B. C09A61E8 für Edward. Die Schlüssel-ID ist direkt im Fenster Schlüssel verwalten sichtbar. Diese Schlüssel-ID ist wie der Vorname einer Person (es ist eine nützliche Abkürzung, aber ist vielleicht nicht eindeutig), während der Fingerabdruck tatsächlich den Schlüssel eindeutig und ohne Möglichkeit der Verwechslung identifiziert. Wenn du nur die Schlüssel-ID hast, kannst du den Schlüssel (und seinen Fingerabdruck) immer noch nachschlagen, wie du es in Schritt 3 getan hast, aber wenn mehrere Möglichkeiten auftauchen, brauchst du den Fingerabdruck der Person, mit der du kommunizieren willst, um zu klären, welchen Schlüssel du benutzen sollst.</p>
-
-
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-4a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/section4-web-of-trust.png" alt="Rubrik 4: Web of Trust" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Schritt 4.a</em> Signiere einen Schlüssel</h3>
- <p>Gehe in deinem E-Mail-Programm zu Enigmail → Schlüssel verwalten.</p>
- <p>Klicke mit der rechten Maustaste auf Edwards öffentlichen Schlüssel und wähle "Unterschreiben" aus dem Kontextmenü aus.</p>
- <p>Im Pop-up-Fenster wähle "Keine Antwort" und klicke auf OK.</p>
- <p>Zurück in Enigmail-Schlüssel verwalten wähle Schlüssel-Server → Schlüssel hochladen und klicke auf OK.</p>
- <p class="notes">Du hast gerade gesagt, dass du darauf vertraust, dass Edwards Schlüssel tatsächlich Edward gehört. Dies bedeutet wenig, da Edward keine echte Person ist, es ist aber gute Praxis.</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" placeholder="xD41A008" name="FROM"></p>
- <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" 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 -->
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-sign_real_keys" class="step">
- <div class="main">
- <h3><em>Wichtig:</em> Überprüfe die Identität der Leute, deren Schlüssel du signierst.</h3>
- <p>Bevor du einen Schlüssel einer realen Person signierst, überprüfe stets, ob der Schlüssel ihr gehört und ob sie ist, wer sie behauptet zu sein. Frage sie nach ihrem Ausweis (außer du vertraust ihr sehr stark) und dem Fingerabdruck ihres öffentlichen Schlüssels -- nicht nur nach der kurzen Schlüssel-ID, die zusätzlich auch zu einem anderen Schlüssel gehören könnte. Antworte ehrlich auf die Frage "Haben Sie überprüft, ob dieser Schlüssel tatsächlich dem oben genannten Absender gehört?" in Enigmail..</p>
- </div><!-- End .main -->
- </div><!-- End #step-sign_real_keys .step-->
-
-
-
- </div>
- </section><!-- End #section4 -->
-
-<!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
- <section id="section5" class="row">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#5</em> Nutze es richtig</h2>
-<p>Alle nutzen GnuPG ein wenig anders, aber es ist wichtig, ein paar wesentliche Regeln zu befolgen, um deine E-Mails zu sichern. Wenn du sie nicht befolgst, gefährdest du die Privatheit der Menschen, mit denen du kommunizierst, und deine eigene, und du beschädigst das Web of Trust.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-5a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/section5-01-use-it-well.png" alt="Rubrik 5: Benutze es richtig" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3>Wann soll ich verschlüsseln?</h3>
-
- <p>Je öfter du deine Nachrichten verschlüsselst, desto besser. Wenn du E-Mails nur hin und wieder verschlüsselt, könnte jede verschlüsselte Nachricht die Aufmerksamkeit der Überwachungssysteme wecken. Wenn alle oder die meisten deiner E-Mails verschlüsselt sind, wissen die Überwacher nicht, wo sie anfangen sollen.</p>
-
-<p>Das heißt nicht, dass es sinnlos ist, nur einige Nachrichten zu verschlüsseln -- es ist ein guter Start und macht Massenüberwachung schwieriger.</p>
-
- </div><!-- End .main -->
- </div><!-- End #step-5a .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-5b" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/section5-02-use-it-well.png" alt="Rubrik 5: Benutze es richtig" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Wichtig:</em> Nimm dich vor ungültigen Schlüsseln in acht</h3>
- <p>GnuPG macht E-Mails sicherer, aber es ist immer noch wichtig, nach ungültigen Schlüsseln Ausschau zu halten, die in die falschen Hände gefallen sein könnten. E-Mails, die mit ungültigen Schlüsseln verschlüsselt worden sind, könnten von Überwachungsprogrammen gelesen werden. </p>
- <p>Gehe in deinem E-Mail-Programm zurück zur zweiten E-Mail, die dir Edward gesendet hat. Weil sie mit deinem Schlüssel verschlüsselt wurde, gibt es oben eine Leiste, die sagt, dass die E-Mail verschlüsselt ist.</p>
-<p><b>Wenn Du GnuPG benutzt, gewöhne es dir an, dass du auf diese Leiste schaust. Enigmail wird dich dort warnen, wenn Du eine E-Mail erhältst, die mit einem nicht vertrauenswürdigen Schlüssel verschlüsselt worden sind.</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>Speichere dein Widerrufszertifikat an einem sicheren Ort</h3>
- <p>Erinnerst du dich daran, als du deine Schlüssel erzeugt hast und das Widerrufszertifikat gespeichert hast, das GnuPG erzeugt hat? Nun ist es an der Zeit, das Zertifikat an den sichersten Ort zu kopieren, den du hast -- ideal ist ein Flashmedium oder eine Festplatte, die du an einem sicheren Ort in deinem Haus aufbewahrst.</p>
-<p>Sollte dein privater Schlüssel jemals gestohlen werden oder verloren gehen, brauchst du dieses Zertifikat, um anderen mitzuteilen, dass du dieses Schlüsselpaar nicht mehr benutzt.</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>Wichtig:</em> Reagiere schnell, wenn jemand deinen privaten Schlüssel bekommt</h3>
- <p>Wenn du deinen privaten Schlüssel verlierst oder ihn jemand anders erhält (z.B. wenn jemand deinen Computer stiehlt oder sich unberechtigt Zugang verschafft), ist es wichtig, ihn sofort zurückzuziehen, bevor ihn jemand benutzt, um deine verschlüsselten E-Mails zu lesen. Wie dies geht, wird in dieser Anleitung nicht beschrieben, du kannst dies aber im <a href="https://www.gnupg.org/gph/de/manual/c319.html#AEN389" >Handbuch von GnuPG</a> nachlesen. Wenn du mit dem Widerruf fertig bist, schicke eine E-Mail an alle, mit denen du normalerweise deinen Schlüssel benutzt, um sie zu informieren.</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>Mache deinen öffentlichen Schlüssel zu einem Teil deiner Online-Identität</h3>
- <p>Füge als erstes deinen Schlüssel-Fingerabdruck zu deiner E-Mail-Signatur hinzu. Dann schreibe an mindestens fünf deiner Freunde eine E-Mail, um ihnen mitzuteilen, dass du gerade GnuPG eingerichtet hast, und um den Fingerabdruck deines öffentlichen Schlüssels bekanntzugeben. Verlinke auf diese Anleitung und bitte sie, deinem Beispiel zu folgen. Vergiss nicht, dass es eine tolle <a href="infographic.html">Infografik</a> gibt, die du weitergeben kannst.</p>
-
-<p class="notes">Schreibe den Fingerabdruck deines öffentlichen Schlüssels überall hin, wo jemand deine E-Mail-Adresse sieht: deine Profile in sozialen Netzwerken, Blog, Webseiten oder Visitenkarten. (Bei der Free Software Foundation schreiben wir unseren auf unsere <a href="https://fsf.org/about/staff">Mitarbeiterseiten</a>.) Wir müssen unsere Kultur so verändern, dass wir den Eindruck haben, dass etwas fehlt, wenn wir eine E-Mail-Adresse ohne einen Schlüssel-Fingerabdruck sehen.</p>
- </div><!-- End .main
- </div> End #step-5d .step-->
-
-
- </div>
- </section><!-- End #section5 -->
-
-
-
-<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
- <section class="row" id="section6">
- <div id="step-click_here" class="step">
- <div class="main">
- <h2><a href="next_steps.html">Gut gemacht! Sieh dir die nächsten Schritte an.</a></h2>
-
- </div><!-- End .main -->
- </div><!-- End #step-click_here .step-->
-
- </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>
- <div class="sidebar">
- <h2>FAQ</h2>
- </div>
-
- <div class="main">
- <dl>
- <dt>My key expired</dt>
- <dd>Answer coming soon.</dd>
-
- <dt>Who can read encrypted messages? Who can read signed ones?</dt>
- <dd>Answer coming soon.</dd>
-
- <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>
- </div>
- </section> --><!-- End #faq -->
-
-<!-- include virtual="footer.html" -->
-
-<!-- include virtual="javascript.html" -->
+++ /dev/null
-<!-- include virtual="head.html" -->
-
- <header class="row centered" id="header">
- <div>
- <p class="back">← Lies die <a href="index.html">Anleitung</a></p>
- <h3><a href="https://fsf.org/share?u=https://u.fsf.org/zc&t=Wie%20asymmetrische%20Verschlüsselung%20funktioniert.%20Infografik%20von%20%40fsf%20%23EmailSelfDefense">Teile unsere Infografik</a> mit dem Hashtag #EmailSelfDefense</h3>
-
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/de/full-infographic.png" alt="Teile unsere Infografik!" /></p>
-
- <p><a href="emailselfdefense_source.zip">Hol dir den Quellcode</a> der Infografik</p>
- <p class="back">← Lies die <a href="index.html">Anleitung</a></p>
- </div>
- </header><!-- End #header -->
-
-<!-- include virtual="footer.html" -->
-
-<!-- include virtual="javascript.html" -->
+++ /dev/null
-<script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"
-type="text/javascript"></script>
-
-<script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js" type="text/javascript"></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>
-
+++ /dev/null
-<!-- include virtual="head.html" -->
-
-<!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
-
- <header class="row" id="header">
- <div>
- <h1>Gut gemacht!</h1>
-
- </div>
- </header><!-- End #header -->
-
-
-<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
- <section class="row" id="section6">
- <div>
- <!-- ~~~~~~~~~ section title + graphics ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#6</em> Nächste Schritte</h2>
- <p>Du hast jetzt die Grundlagen von E-Mail-Verschlüsselung mit GnuPG gelernt und tust damit etwas gegen die Massenüberwachung. Herzlichen Glückwunsch! Die nächsten Schritte helfen dir, mehr aus deinen heutigen Anstrengungen zu machen.</p>
- </div><!-- End .section-intro -->
-
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-political" class="step">
- <div class="sidebar">
- <p><a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/de/infographic-button.png" alt="Sieh dir unsere Infografik an und verbreite sie weiter →" /></a></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3>Tritt der Bewegung bei</h3>
-
-<p>Du hast gerade einen großen Schritt in Richtung Schutz deiner Privatsphäre getan. Aber wenn wir dies alle alleine tun, ist es nicht genug. Um die Massenüberwachung zu stürzen, müssen wir eine Bewegung aufbauen für die Autonomie und Freiheit aller Computernutzer. Trete der Community der Free Software Foundation bei, um Gleichgesinnte zu treffen und zusammen für einen Wandel zu arbeiten:</p>
-
-<p style="font-size:150%"><a href="https://status.fsf.org/fsf">GNU Social</a> | <a href="http://microca.st/fsf">Pump.io</a> | <a href="https://www.twitter.com/fsf">Twitter</a></p>
-<p><a href="https://www.fsf.org/twitter"><small>Lies, warum GNU Social und Pump.io besser sind als Twitter.</small></a></p>
-<br />
-<div class="newsletter">
-<p style="font-size:150%">Wenig frequentierte Mailingliste</p>
- <form method="post" action="https://my.fsf.org/civicrm/profile/create?reset=1&gid=31">
- <input type="text" placeholder="Schreibe deine E-Mail-Adresse..." name="email-Primary" id="frmEmail" />
- <input type="submit" value="Füge mich hinzu" name="_qf_Edit_next" />
- <input type="hidden" value="https://emailselfdefense.fsf.org/de/confirmation.html" name="postURL" />
- <input type="hidden" value="1" name="group[25]" />
- <input type="hidden" value="https://my.fsf.org/civicrm/profile?reset=1&gid=31" name="cancelURL" />
- <input type="hidden" value="Edit:cancel" name="_qf_default" />
- </form>
-<!--<p><small>Du wirst Aktionsweise und Updates von unserer wenig frequentierten Mailingliste erhalten. -->
-<p><small>Lies unsere <a href="https://my.fsf.org/donate/privacypolicy.html">Datenschutzerklärung</a>.</small></p>
- </div><!-- End .newsletter -->
-<!-- <br>
-<p>Folge uns auf Microblogging-Diensten:</p>
-<p style="font-size:150%"><a href="https://status.fsf.org/fsf">GNU Social</a> | <a href="http://microca.st/fsf">Pump.io</a> | <a href="https://www.twitter.com/fsf">Twitter</a></p>
-<p><a href="https://www.fsf.org/twitter"><small>Lies, warum GNU Social und Pump.io besser sind als Twitter.</small></a></p>-->
-
- </div><!-- End .main -->
- </div><!-- End #step-political .step -->
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-friends" class="step">
-<div class="main">
-
- <h3>Hilf deinen Freundinnen und Freunden</h3>
-<p><strong>Dies ist die wichtigste einzelne Sache, die du tun kannst, um E-Mail-Verschlüsselung zu fördern.</strong></p>
-
-<p>Bevor du diese Anleitung schließt, nutze unsere <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Nutze Verschlüsselung mit mir durch %23#EMailSelfDefense %40fsf ">Seite zum Teilen</a>, um eine Nachricht an einige Freunde zu schicken, in der du sie bittest, genauso wie du E-Mails zu verschlüsseln. Denke daran, deinen <a href="index.html#section4">Schlüssel-Fingerabdruck</a> hinzuzufügen, so dass sie deinen öffentlichen Schlüssel einfach herunterladen können.</p>
-
-<p>Es ist außerdem gut, den Fingerabdruck deines öffentlichen Schlüssels deiner E-Mail-Signatur hinzuzufügen, so dass Leute, mit denen du kommunizierst, wissen, dass du verschlüsselte E-Mails annimmst.</p>
-
-<p class="notes">Wir empfehlen, noch einen Schritt weiter zu gehen und ihn zu deinen Profilen in sozialen Netzwerken, Blog, Webseiten oder Visitenkarten hinzuzufügen. (Bei der Free Software Foundation schreiben wir unseren Schlüssel auf unsere <a href="https://fsf.org/about/staff">Mitarbeiterseiten</a>.) Wir müssen unsere Kultur so verändern, dass wir den Eindruck haben, dass etwas fehlt, wenn wir eine E-Mail-Adresse ohne einen Schlüssel-Fingerabdruck sehen.</p>
-
- </div><!-- End .main -->
- </div><!-- End #step-friends .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-more_technologies" class="step">
-
-
-
-<div class="main">
-
-
-
- <h3>Schütze mehr Teile deines digitalen Lebens</h3>
-
- <p>Lerne mehr über überwachungsresistente Software-Lösungen auf <a href="https://directory.fsf.org/wiki/Collection:Privacy_pack">der Seite zum Schutz der Privatsphäre des Free Software Directorys</a> und <a href="https://prism-break.org">prism-break.org</a>.</p> <p> Wenn du Windows, Mac OS oder ein anderes proprietäres Betriebbsystem verwendest, ist der Wechsel zu einem freien Betriebssystem wie GNU/Linux ein großer Schitt in die richtige Richtung, denn freie Software ist weniger anfällig für Angriffe durch versteckte Hintertüren. Schaue dir die von der Free Software Foundation <a href="http://www.gnu.org/distros/free-distros.html">empfohlenen Versionen von GNU/Linux</a> an.</p>
- </div><!-- End .main -->
- </div><!-- End #step-more_technologies .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-better" class="step">
-<div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/de/screenshots/section6-next-steps.png" alt="Rubrik 6: Nächste Schritte" /></p> <br><p class="back" style="text-align:center">← <a href="index.html">Zurück zur Anleitung</a></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3>Mach die Programme zur E-Mail-Selbstverteidigung noch besser</h3>
-<p><a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Gib uns ein Feedback oder schlage Verbesserungen vor</a>. Wir können Übersetzungen gut gebrauchen, kontaktiere uns aber zuerst (<a href="mailto:campaigns@fsf.org">campaigns@fsf.org</a>), bevor du anfängst, so dass wir dich mit den anderen Übersetzern deiner Sprache in Verbindung bringen können.</p>
-
- <p>Wenn du gerne programmierst, kannst du bei <a href="https://www.gnupg.org/">GnuPG</a> oder <a href="https://www.enigmail.net/home/index.php">Enigmail</a> mithelfen.</p>
-
-<p>Du kannst auch die Free Software Foundation unterstützen, so dass sie die E-Mail-Selbstverteidigung weiter verbessern kann und mehr ähnliche Werkzeuge produzieren kann.</p><p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Spenden" src="//static.fsf.org/nosvn/enc-dev0/img/de/donate.png" /></a></p>
-
-<br>
-
- </div><!-- End .main -->
- </div><!-- End #step-better .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
- <div id="step-learn_more" class="step">
- <div class="main">
- <h3>Learn more about GnuPG</h3>
- <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 -->
-
-
- </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>
- <div class="sidebar">
- <h2>FAQ</h2>
- </div>
-
- <div class="main">
- <dl>
- <dt>My key expired</dt>
- <dd>Answer coming soon.</dd>
-
- <dt>Who can read encrypted messages? Who can read signed ones?</dt>
- <dd>Answer coming soon.</dd>
-
- <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>
- </div>
- </section> End #faq -->
-
-<!-- include virtual="footer.html" -->
-
-<!-- include virtual="javascript.html" -->
+++ /dev/null
-<!-- Language list for browsers that do not have JS enabled -->
-<ul id="languages" class="os">
-<li><a href="/en">english</a></li>
-<li><a href="/es">español</a></li>
-<li><a href="/fr">français</a></li>
-<li><a href="/de" class="current">deutsch</a></li>
-<li><a href="/it">italiano</a></li>
-<li><a href="/pt-br">português do Brasil</a></li>
-<li><a href="/tr">türkçe</a></li>
-<li><a href="/ro">română</a></li>
-<li><a href="/ru">русский</a></li>
-<!--<li><a href="/ml">മലയാളം</a></li>-->
-<!--<li><a href="/ko">한국어</a></li>-->
-<li><a href="/ja">日本語</a></li>
-<li><a href="/el">ελληνικά</a></li>
-<!--<li><a href="/ar">العربية</a></li>-->
-</ul>
+++ /dev/null
-<!-- mac-step.html -->
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-1b" class="step">
-
- <div class="main">
- <h3><em>Schritt 1.b</em> Hole dir GnuPG, indem du GPGTools herunterlädst</h3>
- <p>GPGTools ist ein Software-Paket, das GnuPG enthält. <a href="https://gpgtools.org/#gpgsuite">Lade es herunter</a> und installiere es. Wähle immer die Standard-Antworten. Nachdem es installiert wurde, kannst du alle Fenster schließen, die es geöffnet hat.</p>
- </div><!-- End .main -->
-</div><!-- End #step1-b .step -->
-
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-1c" class="step">
- <div class="sidebar">
- <ul class="images">
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>
- <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>Schritt 1.c</em>Installiere das Enigmail-Plugin für dein E-Mail-Programm</h3>
- <p>
- In dem Menü von deinen Programm, klicke auf Add-ons (es könnte auch im Untermenü "Werkzeuge" sein). Vergewissere dich, dass " Erweiterungen" links ausgewählt wurde. Kannst du Enigmail sehen? Wenn ja, dann überspringe diesen Schritt.</p>
- <p>Wenn nicht, suche "Enigmail" mit Hilfe der Suchleiste. Installiere es. Starte dein E-Mail-Programm anschließend neu.</p>
- <!-- ~~~~~~~~~ Probleme? ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Ich kann das Menü nicht finden.</dt>
- <dd>
- In vielen neuen E-Mail-Programmen wird das Hauptmenü durch drei horizontale Balken dargestellt.</dd>
-
- <dt class="feedback">Fidest du keine Lösung für deine Probleme?</dt>
- <dd class="feedback">Frage uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a>.</dd>
- </dl>
- </div><!-- /.troubleshooting -->
- </div><!-- End .main -->
-
-</div><!-- End #step-1c .step -->
-</section><!-- End #section1 -->
+++ /dev/null
-<!DOCTYPE html>
-<html>
- <head>
- <meta charset="utf-8">
-
- <title>Email Self-Defense - a guide to fighting surveillance with GnuPG encryption</title>
- <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail" />
- <meta name="description" content="Email surveillance violates our fundamental rights and makes free speech risky. This guide will teach you email self-defense in 30 minutes with GnuPG.">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css">
- <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
-
- </head>
- <body>
-<!--
- <nav class="nav">
- <div>
- <ul class="lang">
- <li class="help"><a href="http://libreplanet.org/wiki/GPG_guide">Translate this guide!</a></li>
- </ul>
- </div>
- </nav>
--->
-
-<!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
-<!-- ~~~~~~~~~ Revision as of 18:53, 1 June 2014 by Zakkai ~~~~~~~~~ -->
- <header class="row" id="header">
-
-<!-- <div class="highlight" style="background: red;">
- <h3 style="text-align: center;"><strong style="color: white;">Website Under Construction</strong></h3>
- </div>-->
-
- <div>
- <h1>Email Self-Defense</h1>
- <ul class="os">
- <li><a href="index.html">GNU/Linux</a></li>
- <li><a href="mac.html" class="current">Mac OS</a></li>
- <li><a href="windows.html">Windows</a></li>
- <li class="share"><a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">#EmailSelfDefense</a></li>
- </ul>
-
- <!-- ~~~~~~~~~ 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>
- <span style="font-size:125%"><p>We fight for computer user's rights, and promote the development of free (as in freedom) software. Resisting bulk surveillance is very important to us.</p><p><strong>We want to heavily promote tools like this in-person and online, to help as many people as possible take the first step towards using free software to protect their privacy. Can you make a donation or become a member to help us achieve this goal?</strong></p></span>
-
- <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/donate.en.png"></a> <a href="https://u.fsf.org/yr"><img alt="Join now" src="//static.fsf.org/nosvn/enc-dev0/img/join.en.png"></a></p>
-
- </div><!-- End #fsf-intro -->
-
- <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
- <div class="intro">
- <p>
- <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/infographic-button.png" alt="View & share our infographic →" /></a>
- Bulk surveillance violates our fundamental rights and makes free speech risky. This guide will teach you a basic surveillance self-defense skill: email encryption. 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 that intercepts your email can't read it. All you need is a computer with an Internet connection, an email account and about half an hour.</p>
-
-<p>Even if you have nothing to hide, using encryption helps protect the privacy of people you communicate with, and makes life difficult for bulk surveillance systems. If you do have something important to hide, you're in good company; these are the same tools that Edward Snowden used to share his famous secrets about the NSA.</p>
-
-<p>In addition to using encryption, standing up to surveillance requires fighting politically for a <a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">reduction in the amount of data collected on us</a>, but the essential first step is to protect yourself and make surveillance of your communication as difficult as possible. Let's get started!</p>
-
- </div>
-
- </div>
- </header><!-- End #header -->
-
-<!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
- <section class="row" id="section1">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#1</em> Get the pieces</h2>
- <p class="notes">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). To defend your freedom as well as protect yourself from surveillance, we recommend you switch to a free software operating system like GNU/Linux. Learn more about free software at <a href="https://u.fsf.org/ys">fsf.org</a>.</p>
- <p>To get started, you'll need a desktop email program installed on your computer. This guide works with free software versions of the Thunderbird email program, and with Thunderbird itself. Email programs are another way to access the same email accounts you can access in a browser (like GMail), but provide extra features.</p>
- <p>If you are already have one of these, you can skip to <a href="#step-1b">Step 1.b</a>.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-1a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Step 1.a</em> Set your email program up with your email account (if it isn't already)</h3>
- <p>Open your email program and follow the wizard that sets it up with your email account.</p>
-
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <dl>
- <dt>What's a wizard?</dt>
- <dd>A wizard is a series of windows that pop up to make it easy to get something done on a computer, like installing a program. You click through it, selecting options as you go.</dd>
- <dt>My email program can't find my account or isn't downloading my mail</dt>
- <dd>Before searching the Web, we recommend you start by asking other people who use your email system, to figure out the correct settings.</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 #step1-a .step -->
-
-
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-1b" class="step">
-
- <div class="main">
- <h3><em>Step 1.b</em> Get GnuPG by downloading GPGTools</h3>
- <p>GPGTools is a software package that includes GnuPG. <a href="https://gpgtools.org/#gpgsuite">Download</a> and install it, choosing default options whenever asked. After it's installed, you can close any windows that it creates.</p>
-
- </div><!-- End .main -->
- </div><!-- End #step1-b .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-1c" class="step">
- <div class="sidebar">
- <ul class="images">
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>
- <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.c</em> Install the Enigmail plugin for your email program</h3>
- <p>In your email program's menu, select Add-ons (it may be in the Tools section). Make sure Extensions is selected on the left. Do you see Enigmail? if so, skip this step.</p>
- <p>If not, search "Enigmail" with the search bar in the upper right. You can take it from here. Restart your email program when you're done.</p>
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <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>
- </section><!-- End #section1 -->
-
-<!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
- <section class="row" id="section2">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#2</em> Make your keys</h2>
- <p>To use the GnuPG system, you'll need a public key and a private key (known together as a keypair). Each is a long string of randomly generated numbers and letters that are unique to you. Your public and private keys are linked together by a special mathematical function.</p>
-
-<p>Your public key isn't like a physical key, because it's stored in the open in an online directory called a keyserver. People download it and use it, along with GnuPG, to encrypt emails they send to you. You can think of the keyserver as phonebook, where people who want to send you an encrypted email look up your public key.</p>
-
-<p>Your private key is more like a physical key, because you keep it to yourself (on your computer). You use GnuPG and your private key to decode encrypted emails other people send to you.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-2a" class="step">
- <div class="sidebar">
- <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>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 12 characters and include at least one lower case and upper case letter and at least one number or punctuation symbol. Don't forget the password, or all this work will be wasted!</p>
- <p class="notes">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 <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>
-
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <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 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-2a .step -->
- <div id="step-2b" class="step">
- <div class="main">
- <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
- <p>In your email program's menu, select OpenPGP → Key Management.</p>
-<p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
-<p class="notes">Now someone who wants to send you an encrypted message can download your public key from the Internet. There are multiple keyservers that you can select from the menu when you upload, but they are all copies of each other, so it doesn't matter which one you use. However, it sometimes takes a few hours for them to match each other when a new key is uploaded.</p>
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <dl>
- <dt>The progress bar never finishes</dt>
- <dd>Close the upload popup, make sure you are on the Internet and try again. If that doesn't work, try again, selecting a different keyserver.</dd>
-<dt>My key doesnt appear in the list</dt>
- <dd>Try checking Show Default Keys.</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-2a .step -->
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="terminology" class="step">
- <div class="main">
- <h3>GnuPG, OpenPGP, what?</h3>
- <p>You're using a program called GnuPG, but the menu in your email program is called OpenPGP. Confusing, right? In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used interchangeably, though they all have slightly different meanings.</p>
- </div><!-- End .main -->
- </div><!-- End #terminology.step-->
- </div>
- </section><!-- End #section2 -->
-
-<!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
- <section class="row" id="section3">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#3</em> Try it out!</h2>
- <p>Now you'll try a test correspondence with a computer program named Adele, which knows how to use encryption. Except where noted, these are the same steps you'd follow when corresponding with a real, live person.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Step 3.a</em> Send Adele your public key</h3>
- <p>This is a special step that you won't have to do when corresponding with real people. In your email program's menu, go to OpenPGP → Key Management. You should see your key in the list that pops up. Right click on your key and select Send Public Keys by Email. This will create a new draft message, as if you had just hit the Write button.</p>
-
-<p>Address the message to adele-en@gnupp.de. Put at least one word (whatever you want) in the subject and body of the email, then hit send.</p>
-
-<p class="notes">It may take two or three minutes for Adele to respond. In the meantime, you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section of this guide. Once she's responded, head to the next step. From here on, you'll be doing just the same thing as when corresponding with a real person.</p>
- </div><!-- End .main -->
- </div><!-- End #step-3b .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3b" class="step">
- <div class="main">
- <h3><em>Step 3.b</em> Send a test encrypted email</h3>
- <p>Write a new email in your email program, addressed to adele-en@gnupp.de. Make the subject "Encryption test" or something similar and write something in the body. Don't send it yet.</p>
- <p>Click the icon of the key in the bottom right of the composition window (it should turn yellow). This tells Enigmail to encrypt the email with the key you downloaded in the last step.</p>
- <p class="notes">Next to the key, you'll notice an icon of a pencil. Clicking this tells Enigmail to add a special, uniqe signature to your message, generated using your private key. This is a separate feature from encryption, and you don't have to use it for this guide.</p>
-<p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
-
- <p>To encrypt and email to Adele, you need her public key, and so now you'll have Enigmail download it from a keyserver. Click Download Missing Keys and use the default in the pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key ID starting with C), then select ok. Select ok in the next pop-up.</p>
-
- <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Select Adele's key from the list and click Ok. If the message doesn't send automatically, you can hit send now.</p>
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <dl>
- <dt>Enigmail can't find Adele's key</dt>
- <dd>Close the pop-ups that have appeared since you clicked. Make sure you are connected to the Internet and try again. If that doesn't work, repeat the process, choosing a different keyserver when it asks you to pick one.</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 -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-headers_unencrypted" class="step">
- <div class="main">
- <h3><em>Important:</em> Security tips</h3>
- <p>Even if you encrypted your email, the subject line is not encrypted, so don't put private information there. The sending and receiving addresses aren't encrypted either, so they could be read by a surveillance system. When you send attachments, Enigmail will give you an option of whether you want to encrypt them.</p>
-<p>It's also good practice to click the key icon in your email composition window <strong>before</strong> you start to write. Otherwise, your email client could save an unencrypted draft on the mail server, potentially exposing it to snooping.</p>
- </div><!-- End .main -->
- </div><!-- End #step-headers_unencrypted .step-->
-
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3c" class="step">
- <div class="main">
- <h3><em>Step 3.c</em> Receive a response</h3>
- <p>When Adele receives your email, she will use her private key to decrypt it, then fetch your public key from a keyserver and use it to encrypt a response to you.</p>
- <p class="notes">Since you encrypted this email with Adele's public key, Adele's private key is required to decrypt it. Adele is the only one with her private key, so no one except her — not even you — can decrypt it.</p>
- <p class="notes">It may take two or three minutes for Adele to respond. In the meantime, you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section of this guide.</p>
- <p>When you receive Adele's email and open it, Enigmail will automatically detect that it is encrypted with your public key, and then it will use your private key to decrypt it.</p>
- <p>Notice the bar that Enigmail shows you above the message, with information about the status of Adele's key.</p>
- </div><!-- End .main -->
- </div><!-- End #step-3c .step -->
-
-<!-- STEP 3D IS COMMENTED OUT UNTIL WE FIND A WAY TO VALIDATE SIGNATURES
- <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>
- </div>-->
- </div>
- </section><!-- End #section3 -->
-
-
-<!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
- <section class="row" id="section4">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#4</em> Learn the Web of Trust</h2>
- <p>Email encryption is a powerful technology, but it has a weakness; it requires a way to verify that a person's public key is actually theirs. Otherwise, there would be no way to stop an attacker from making an email address with your friend's name, creating keys to go with it and impersonating your friend. That's why the free software programmers that developed email encryption created keysigning and the Web of Trust.</p>
-
-<p>When you sign someone's key, you are publicly saying that you trust that it does belong to them and not an impostor. People who use your public key can see the number of signatures it has. Once you've used GnuPG for a long time, you may have hundreds of signatures. The Web of Trust is the constellation of all GnuPG users, connected to each other by chains of trust expressed through signatures, into a giant network. The more signatures a key has, and the more signatures its signers' keys have, the more trustworthy that key is.</p>
-
-<p>People's public keys are usually identified by their key fingerprint, which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Adele's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to OpenPGP → Key Management in your email program's menu, then right clicking on the key and choosing Key Properties. It's good practice to share your fingerprint wherever you share your email address, so that so that people can double-check that they have the correct public key when they download yours from a keyserver.</p>
-
-<p class="notes">You may also see public keys referred to by their key ID, which is simply the last 8 digits of the fingerprint, like C09A61E8 for Adele. The key ID is visible directly from the Key Management Window. This key ID is like a person's first name (it is a useful shorthand but may not be unique to a given key), whereas the fingerprint actually identifies the key uniquely without the possibility of confusion. If you only have the key ID, you can still look up the key (as well as its fingerprint), like you did in Step 3, but if multiple options appear, you'll need the fingerprint of the person to are trying to communicate to verify which one to use.</p>
-
-
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-4a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
- </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>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 class="notes">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, but it's good practice.</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" placeholder="xD41A008" name="FROM"></p>
- <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" 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 -->
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-sign_real_keys" class="step">
- <div class="main">
- <h3><em>Important:</em> check people's identification before signing their keys</h3>
- <p>Before signing a real person's key, always make sure it actually belongs to them, and that they are who they say they are. Ask them to show you their ID (unless you trust them very highly) and their public key fingerprint -- not just the shorter public key ID, which could refer to another key as well. In Enigmail, 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>
- </div><!-- End .main -->
- </div><!-- End #step-sign_real_keys .step-->
-
-
-
- </div>
- </section><!-- End #section4 -->
-
-<!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
- <section id="section5" class="row">
- <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="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <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.</p>
-
- </div><!-- End .main -->
- </div><!-- End #step-5a .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-5b" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Important:</em> Be wary of invalid keys</h3>
- <p>GnuPG makes email safer, but it's still important to watch out for invalid keys, 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 Adele encrypted it with your public 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>Copy your revocation certificate to somewhere safe</h3>
- <p>Remember when you created your keys and saved the revocation certificate that GnuPG made? It's time to copy that certificate 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 read your encrypted email. This guide doesn't cover how to revoke a key, but you can follow the <a href="https://www.gnupg.org/gph/en/manual.html#AEN305">instructions on the GnuPG site</a>. 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 your public key part of your online identity</h3>
- <p> First add your public key fingerprint to your email signature, then compose an email to at least five of your friends, telling them you just set up GnuPG and mentioning your public key fingerprint. Link to this guide and ask them to join you. Don't forget that there's also an awesome <a href="infographic.html">infographic to share.</a></p>
-
-<p class="notes">Start writing your public key fingerprint anywhere someone would see your email address: your social media profiles, blog, Website, or business card. (At the Free Software Foundation, we put ours on our <a href="https://fsf.org/about/staff">staff page</a>.) 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 fingerprint.</p>
- </div><!-- End .main
- </div><!-- End #step-5d .step-->
-
-
- </div>
- </section><!-- End #section5 -->
-
-<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
- <section class="row" id="section6">
- <div id="step-click_here" class="step">
- <div class="main">
- <h2><a href="next_steps.html">Click here when you're done</a></h2>
-
- </div><!-- End .main -->
- </div><!-- End #step-click_here .step-->
-
- </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>
- <div class="sidebar">
- <h2>FAQ</h2>
- </div>
-
- <div class="main">
- <dl>
- <dt>My key expired</dt>
- <dd>Answer coming soon.</dd>
-
- <dt>Who can read encrypted messages? Who can read signed ones?</dt>
- <dd>Answer coming soon.</dd>
-
- <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>
- </div>
- </section> --><!-- End #faq -->
-
-<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
- <footer class="row" id="footer">
- <div>
- <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 © 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>
- <p><em>Version 2.0, launched 6/18/2014. <!--LANGUAGE translation by NAME, NAME and NAME.--></em></p>
-<p>The images on this page are under a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 license (or later version)</a>, and the rest of it is under a <a href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons Attribution-ShareAlike 4.0 license (or later version)</a>. — <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
- <p>Download the source packages for <a href="gnupg-guide.zip">this guide</a> and for <a href="gnupg-infographic.zip">the infographic</a>. Fonts used in the guide & infographic: <a href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo Impallari, <a href="http://www.google.com/fonts/specimen/Signika">Signika</a> by Anna Giedryś <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="http://www.thegopherarchive.com/gopher-files-hacks-pxl2000-119351.htm">PXL-2000</a> by Florian Cramer.</p>
- <p>
- <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
- rel="jslicense">
- JavaScript license information
- </a>
- </p>
- </div><!-- /#copyright -->
- <p class="credits">
- Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" alt="Journalism++" /></a>
- </p><!-- /.credits -->
- </div>
- </footer><!-- End #footer -->
-
- <script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
- <script src="//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>
+++ /dev/null
-
-<!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
- <section class="row" id="section2">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#2</em> Make your keys</h2>
- <p>To use the GnuPG system, you'll need a public key and a private key (known together as a keypair). Each is a long string of randomly generated numbers and letters that are unique to you. Your public and private keys are linked together by a special mathematical function.</p>
-
-<p>Your public key isn't like a physical key, because it's stored in the open in an online directory called a keyserver. People download it and use it, along with GnuPG, to encrypt emails they send to you. You can think of the keyserver as phonebook, where people who want to send you an encrypted email look up your public key.</p>
-
-<p>Your private key is more like a physical key, because you keep it to yourself (on your computer). You use GnuPG and your private key to decode encrypted emails other people send to you.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-2a" class="step">
- <div class="sidebar">
- <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>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 12 characters and include at least one lower case and upper case letter and at least one number or punctuation symbol. Don't forget the password, or all this work will be wasted!</p>
- <p class="notes">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 <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>
-
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <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 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-2a .step -->
- <div id="step-2b" class="step">
- <div class="main">
- <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
- <p>In your email program's menu, select OpenPGP → Key Management.</p>
-<p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
-<p class="notes">Now someone who wants to send you an encrypted message can download your public key from the Internet. There are multiple keyservers that you can select from the menu when you upload, but they are all copies of each other, so it doesn't matter which one you use. However, it sometimes takes a few hours for them to match each other when a new key is uploaded.</p>
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <dl>
- <dt>The progress bar never finishes</dt>
- <dd>Close the upload popup, make sure you are on the Internet and try again. If that doesn't work, try again, selecting a different keyserver.</dd>
-<dt>My key doesnt appear in the list</dt>
- <dd>Try checking Show Default Keys.</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-2a .step -->
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="terminology" class="step">
- <div class="main">
- <h3>GnuPG, OpenPGP, what?</h3>
- <p>You're using a program called GnuPG, but the menu in your email program is called OpenPGP. Confusing, right? In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used interchangeably, though they all have slightly different meanings.</p>
- </div><!-- End .main -->
- </div><!-- End #terminology.step-->
- </div>
- </section><!-- End #section2 -->
-
-<!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
- <section class="row" id="section3">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#3</em> Try it out!</h2>
- <p>Now you'll try a test correspondence with a computer program named Adele, which knows how to use encryption. Except where noted, these are the same steps you'd follow when corresponding with a real, live person.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Step 3.a</em> Send Adele your public key</h3>
- <p>This is a special step that you won't have to do when corresponding with real people. In your email program's menu, go to OpenPGP → Key Management. You should see your key in the list that pops up. Right click on your key and select Send Public Keys by Email. This will create a new draft message, as if you had just hit the Write button.</p>
-
-<p>Address the message to adele-en@gnupp.de. Put at least one word (whatever you want) in the subject and body of the email, then hit send.</p>
-
-<p class="notes">It may take two or three minutes for Adele to respond. In the meantime, you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section of this guide. Once she's responded, head to the next step. From here on, you'll be doing just the same thing as when corresponding with a real person.</p>
- </div><!-- End .main -->
- </div><!-- End #step-3b .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3b" class="step">
- <div class="main">
- <h3><em>Step 3.b</em> Send a test encrypted email</h3>
- <p>Write a new email in your email program, addressed to adele-en@gnupp.de. Make the subject "Encryption test" or something similar and write something in the body. Don't send it yet.</p>
- <p>Click the icon of the key in the bottom right of the composition window (it should turn yellow). This tells Enigmail to encrypt the email with the key you downloaded in the last step.</p>
- <p class="notes">Next to the key, you'll notice an icon of a pencil. Clicking this tells Enigmail to add a special, uniqe signature to your message, generated using your private key. This is a separate feature from encryption, and you don't have to use it for this guide.</p>
-<p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
-
- <p>To encrypt and email to Adele, you need her public key, and so now you'll have Enigmail download it from a keyserver. Click Download Missing Keys and use the default in the pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key ID starting with C), then select ok. Select ok in the next pop-up.</p>
-
- <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Select Adele's key from the list and click Ok. If the message doesn't send automatically, you can hit send now.</p>
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <dl>
- <dt>Enigmail can't find Adele's key</dt>
- <dd>Close the pop-ups that have appeared since you clicked. Make sure you are connected to the Internet and try again. If that doesn't work, repeat the process, choosing a different keyserver when it asks you to pick one.</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 -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-headers_unencrypted" class="step">
- <div class="main">
- <h3><em>Important:</em> Security tips</h3>
- <p>Even if you encrypted your email, the subject line is not encrypted, so don't put private information there. The sending and receiving addresses aren't encrypted either, so they could be read by a surveillance system. When you send attachments, Enigmail will give you an option of whether you want to encrypt them.</p>
-<p>It's also good practice to click the key icon in your email composition window <strong>before</strong> you start to write. Otherwise, your email client could save an unencrypted draft on the mail server, potentially exposing it to snooping.</p>
- </div><!-- End .main -->
- </div><!-- End #step-headers_unencrypted .step-->
-
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3c" class="step">
- <div class="main">
- <h3><em>Step 3.c</em> Receive a response</h3>
- <p>When Adele receives your email, she will use her private key to decrypt it, then fetch your public key from a keyserver and use it to encrypt a response to you.</p>
- <p class="notes">Since you encrypted this email with Adele's public key, Adele's private key is required to decrypt it. Adele is the only one with her private key, so no one except her — not even you — can decrypt it.</p>
- <p class="notes">It may take two or three minutes for Adele to respond. In the meantime, you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section of this guide.</p>
- <p>When you receive Adele's email and open it, Enigmail will automatically detect that it is encrypted with your public key, and then it will use your private key to decrypt it.</p>
- <p>Notice the bar that Enigmail shows you above the message, with information about the status of Adele's key.</p>
- </div><!-- End .main -->
- </div><!-- End #step-3c .step -->
-
-<!-- STEP 3D IS COMMENTED OUT UNTIL WE FIND A WAY TO VALIDATE SIGNATURES
- <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>
- </div>-->
- </div>
- </section><!-- End #section3 -->
-
-
-<!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
- <section class="row" id="section4">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#4</em> Learn the Web of Trust</h2>
- <p>Email encryption is a powerful technology, but it has a weakness; it requires a way to verify that a person's public key is actually theirs. Otherwise, there would be no way to stop an attacker from making an email address with your friend's name, creating keys to go with it and impersonating your friend. That's why the free software programmers that developed email encryption created keysigning and the Web of Trust.</p>
-
-<p>When you sign someone's key, you are publicly saying that you trust that it does belong to them and not an impostor. People who use your public key can see the number of signatures it has. Once you've used GnuPG for a long time, you may have hundreds of signatures. The Web of Trust is the constellation of all GnuPG users, connected to each other by chains of trust expressed through signatures, into a giant network. The more signatures a key has, and the more signatures its signers' keys have, the more trustworthy that key is.</p>
-
-<p>People's public keys are usually identified by their key fingerprint, which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Adele's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to OpenPGP → Key Management in your email program's menu, then right clicking on the key and choosing Key Properties. It's good practice to share your fingerprint wherever you share your email address, so that so that people can double-check that they have the correct public key when they download yours from a keyserver.</p>
-
-<p class="notes">You may also see public keys referred to by their key ID, which is simply the last 8 digits of the fingerprint, like C09A61E8 for Adele. The key ID is visible directly from the Key Management Window. This key ID is like a person's first name (it is a useful shorthand but may not be unique to a given key), whereas the fingerprint actually identifies the key uniquely without the possibility of confusion. If you only have the key ID, you can still look up the key (as well as its fingerprint), like you did in Step 3, but if multiple options appear, you'll need the fingerprint of the person to are trying to communicate to verify which one to use.</p>
-
-
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-4a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
- </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>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 class="notes">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, but it's good practice.</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" placeholder="xD41A008" name="FROM"></p>
- <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" 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 -->
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-sign_real_keys" class="step">
- <div class="main">
- <h3><em>Important:</em> check people's identification before signing their keys</h3>
- <p>Before signing a real person's key, always make sure it actually belongs to them, and that they are who they say they are. Ask them to show you their ID (unless you trust them very highly) and their public key fingerprint -- not just the shorter public key ID, which could refer to another key as well. In Enigmail, 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>
- </div><!-- End .main -->
- </div><!-- End #step-sign_real_keys .step-->
-
-
-
- </div>
- </section><!-- End #section4 -->
-
-<!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
- <section id="section5" class="row">
- <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="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <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.</p>
-
- </div><!-- End .main -->
- </div><!-- End #step-5a .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-5b" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Important:</em> Be wary of invalid keys</h3>
- <p>GnuPG makes email safer, but it's still important to watch out for invalid keys, 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 Adele encrypted it with your public 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>Copy your revocation certificate to somewhere safe</h3>
- <p>Remember when you created your keys and saved the revocation certificate that GnuPG made? It's time to copy that certificate 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 read your encrypted email. This guide doesn't cover how to revoke a key, but you can follow the <a href="https://www.gnupg.org/gph/en/manual.html#AEN305">instructions on the GnuPG site</a>. 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 your public key part of your online identity</h3>
- <p> First add your public key fingerprint to your email signature, then compose an email to at least five of your friends, telling them you just set up GnuPG and mentioning your public key fingerprint. Link to this guide and ask them to join you. Don't forget that there's also an awesome <a href="infographic.html">infographic to share.</a></p>
-
-<p class="notes">Start writing your public key fingerprint anywhere someone would see your email address: your social media profiles, blog, Website, or business card. (At the Free Software Foundation, we put ours on our <a href="https://fsf.org/about/staff">staff page</a>.) 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 fingerprint.</p>
- </div><!-- End .main
- </div><!-- End #step-5d .step-->
-
-
- </div>
- </section><!-- End #section5 -->
-
-<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
- <section class="row" id="section6">
- <div id="step-click_here" class="step">
- <div class="main">
- <h2><a href="next_steps.html">Click here when you're done</a></h2>
-
- </div><!-- End .main -->
- </div><!-- End #step-click_here .step-->
-
- </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>
- <div class="sidebar">
- <h2>FAQ</h2>
- </div>
-
- <div class="main">
- <dl>
- <dt>My key expired</dt>
- <dd>Answer coming soon.</dd>
-
- <dt>Who can read encrypted messages? Who can read signed ones?</dt>
- <dd>Answer coming soon.</dd>
-
- <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>
- </div>
- </section> --><!-- End #faq -->
+++ /dev/null
-<body>
-
- <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
-
- <header class="row" id="header">
- <div>
- <h1>Gut Gemacht!</h1>
-
- </div>
- </header><!-- End #header -->
-
-
- <!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
- <section class="row" id="section6">
- <div>
- <!-- ~~~~~~~~~ section title + graphics ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#6</em> Nächste Schritte</h2>
- <p>
- Du hast jetzt die Grundlagen von GnuPG gelernt und tust etwas gegen massive Überwachung. Herzlichen Glückwunsch! Die nächsten Schritte zeigen dir, wie du mehr aus dem Aufwand, den du heute geleistet hast, machen kannst.</p>
- </div><!-- End .section-intro -->
-
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-political" class="step">
- <div class="sidebar">
- <p><a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/infographic-button.png" alt="View & share our infographic →" /></a></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3>Trete der Bewegung bei</h3>
-
- <p>
- Du hast gerade einen großen Schritt in Richtung des Schutzes deiner Privatsphäre getan.
- Aber wenn jeder dies alleine tut, ist das nicht genug, wir müssen eine Bewegung aufbauen
- für die Freiheit und Selbstständigkeit aller Computernutzer. Trete der Community der Free
- Software Foundation bei um Gleichgesinnte zu treffen und zusammen für den Wandel zu arbeiten.</p>
- <div class="newsletter">
- <form method="post" action="https://my.fsf.org/civicrm/profile/create?reset=1&gid=31">
- <input type="text" placeholder="Schreibe deine E-Mail-Adresse..." name="email-Primary" id="frmEmail">
- <input type="submit" value="Füge mich hinzu" name="_qf_Edit_next">
- <input type="hidden" value="confirmation.html" name="postURL">
- <input type="hidden" value="1" name="group[25]">
- <input type="hidden" value="https://my.fsf.org/civicrm/profile?reset=1&gid=31" name="cancelURL">
- <input type="hidden" value="Edit:cancel" name="_qf_default">
- </form>
- <p><small>Dies abonniert unseren Newsletter, der zur Zeit leider nur auf Englisch, Französisch und Spanisch verfügbar ist. <a href="https://my.fsf.org/donate/privacypolicy.html">Datenschutzerklärung</a>.</small></p>
- </div><!-- End .newsletter -->
- <br>
- <p>Folge uns auf Microblogging-Diensten:</p>
- <p style="font-size:150%">
- <a href="https://status.fsf.org/fsf">
- <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"
- class="share-logo" alt="[GNU Social]">
- GNU Social
- </a> |
- <a href="http://microca.st/fsf">
- <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"
- class="share-logo" alt="[Pump.io]">
- Pump.io
- </a> |
- <a href="https://www.twitter.com/fsf">Twitter</a>
- </p>
- <a href="https://www.fsf.org/twitter">Lies, warum GNU Social und Pump.io besser als Twitter sind.</a></p>
-
- </div><!-- End .main -->
- </div><!-- End #step-political .step -->
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-friends" class="step">
- <div class="main">
-
- <h3>Hilf deinen Freunden</h3>
- <p>Bevor du diese Anleitung schließt, nutze unsere <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Nuztze%20Verschlüsselung%20mit%20mir%20und%20%40fsf%20%23EmailSelbstverteidigung">Seite zum Teilen</a>, um eine Nachricht an einige Freunde zu schicken, in der du sie bittest, mit dir vsrschlüsselte E-Mails zu schreiben. Denke daran, deine <a href="#section4">Schlüssel-ID</a> hinzuzufügen, sodass sie deinen öffentlichen Schlüssel herunterladen können.</p>
-
- </div><!-- End .main -->
- </div><!-- End #step-friends .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-more_technologies" class="step">
- <div class="main">
- <h3>Schütze mehr Teile deines digitalen Lebens</h3>
- <p>Lerne über überwachungsresistente Software-Lösungen auf <a href="https://directory.fsf.org/wiki/Collection:Privacy_pack">der Seite zum Schutz der Privatsphäre des Free Software Directorys</a> und <a href="https://prism-break.org">prism-break.org</a>.</p> <p> Wenn du Windows, Mac OS oder ein anderes proprietäres Betriebbsystem verwendest, ist der wechsel zu einen freien Betriebssystem wie GNU/Linux ein großer Schitt in die richtige Richtung, denn freie Software ist weniger anfällig für Angriffe durch versteckte Hintertüren. Schaue dir die <a href="http://www.gnu.org/distros/free-distros.html">empfohlenen Versionen von GNU/Linux</a> an.</p>
- </div><!-- End .main -->
- </div><!-- End #step-more_technologies .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-better" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section6-next-steps.png" alt="Section 6: Next Steps" /></p> <br><p class="back" style="text-align:center">← <a href="index.html">Zurück zur Anleitung</a></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3>Verbessere die E-Mail-Selbstverteidigungsprogramme</h3>
- <p><a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Gib uns ein Feedback oder schlage Verbesserungen vor</a>. Wir können Übersetzungen gut gebrauchen, kontaktiere uns aber zuerst (<a href="mailto:campaigns@fsf.org">campaigns@fsf.org</a>) bevor du anfängst, sodass wir dich mit den anderen Übersetzern deiner Sprache in Verbindung bringen können.</p>
-
- <p>Wenn du gerne programmierst, kannst du bei <a href="https://www.gnupg.org/">GnuPG</a> oder <a href="https://www.enigmail.net/home/index.php">Enigmail</a> mithelfen.</p>
-
- <p>Du kannst auch die Free Software Foundation unterstützen, sodass sie die E-Mail-Selbstverteidigung so viel wie möglich verbreiten kann und mehr ähnliche Werkzeuge produzieren kann.<p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/donate.en.png"></a> <a href="https://u.fsf.org/yr"><img alt="Join now" src="//static.fsf.org/nosvn/enc-dev0/img/join.en.png"></a></p>
-
-</div><!-- End .main -->
-</div><!-- End #step-better .step -->
-
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
- <div id="step-learn_more" class="step">
- <div class="main">
- <h3>Learn more about GnuPG</h3>
- <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>
- </div> End #step-learn_more .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>
- <div class="sidebar">
- <h2>FAQ</h2>
- </div>
-
- <div class="main">
- <dl>
- <dt>My key expired</dt>
- <dd>Answer coming soon.</dd>
-
- <dt>Who can read encrypted messages? Who can read signed ones?</dt>
- <dd>Answer coming soon.</dd>
-
- <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>
- </div>
- </section> --><!-- End #faq -->
+++ /dev/null
-<!-- begin rest.html -->
-<!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
-<section class="row" id="section2">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#2</em> Erstelle deine Schlüssel</h2>
- <p>Um GnuPG zu verwenden, benötigt man einen öffentlichen und einen privaten Schlüssel (beide bilden ein Schlüsselpaar). Jeder Schlüssel ist eine sehr große Zahl und ist einzigartig. Beide Schlüssel sind mit einer speziellen mathematischen Funktion verbunden.</p>
-
- <p>Dein öffentlicher Schlüssel ist nicht wie ein Hausschlüssel, da er im Internet auf einem Schlüsselserver gespeichert wird. Die Leute können ihn so herunterladen und ihn benutzen, wenn sie dir verschlüsselte E-Mails verschicken. Man kann sich den Schlüsselserver wie ein Telefonbuch vorstellen, wo Leute, die dir eine Verschlüsselte E-Mail schicken möchten, deinen öffentlichen Schlüssel herunterladen können.</p>
-
- <p>
- Dein privater Schlüssel ist eher wie ein Hausschlüssel, weil ihn niemand außer dir besitzen darf. Der private Schlüssel wird eingesetzt, wenn du E-Mails entschlüsselst.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-2a" class="step">
- <div class="sidebar">
- <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 -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div class="main">
- <h3><em>Schritt 2.a</em>Erstelle ein Schlüsselpaar</h3>
- <p>Wähle im Menü deines E-Mail-Programmes OpenPGP → Setup Wizard.
- Du musst den Text nicht lesen, wenn du nicht willst, aber es ist eine gute Idee bei späteren Schritten den Text zu lesen.</p>
- <p>Im zweiten Schritt, mit dem Titel "Unterschreiben", wähle "Nein, ich möchte in Empfängerregeln festlegen, wann unterschrieben werden soll."</p>
- <p>Nutze die Standard-Optionen, bis du am Schritt "Schlüssel erzeugen" angelangt bist.</p>
- <p>
- Beim Schritt namens "Schlüssel erzeugen", solltest du ein starkes Passwort verwenden. Vergesse es nicht, sonst ist diese gesamte Arbeit umsonst!</p>
- <p class="notes"> Das Programm wird einige Minuten brauchen während es den nächsten Schritt ausführt. Während du wartest, solltest du etwas anderes mit deinem Computer tun, wie einen Film anschauen oder im Internet surfen. Je mehr du deinen Computer nutzt, desto schneller wird der Schlüssel generiert.</p>
- <p>Wenn der Schritt zur Bestätigung kommt, klicke auf Zertifikat generieren und speichere es auf einem sicheren Ort (wir empfehlen ein externen Datenträger). Du wirst mehr über dieses Zertifikat in <a href="#section5">Sektion 5</a> lernen.</p>
- <!-- <p class="notes"> -->
- <!-- Nachdem du deinen Schlüssel generiert hast, lädt der Enigmail-Assistent den öffentlichen Schlüssel auf einen Schlüsselserver hoch, das ist ein Computer, der alle Schlüssel über das Internet verfügbar macht.</p> -->
-
- <!-- ~~~~~~~~~ Probleme? ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Ich kann das OpenPGP-Menü nicht finden.</dt>
- <dd>
- In vielen neuen E-Mail-Programmen wird das Hauptmenü durch drei horizontale Streifen dargestellt. OpenPGP könnte in einer Sektion namens Tools sein.</dd>
- <dt>Der assistent kann GnuPG nicht finden.</dt>
-
- <dd>Öffne das Programm, das du benutzt um Software zu installieren, suche GnuPG und installiere es. Starte dann den Assistenten unter OpenPGP → OpenPGP-Assistent neu.</dd>
- <!--<dt>Was heißt OpenPGP?</dt>
-
- <dd>OpenPGP ist ein Protokoll, das von GnuPG benutzt wird, so ähnlich wie HTTP, welches zum Surfen im Internet verwendet wird. Es ist eine etwas missverständliche Bezeichung die Enigmail verwendet.</dd>-->
- <dt class="feedback">Fidest du keine Lösung für deine Probleme?</dt>
- <dd class="feedback">Frage uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a>.</dd>
- </dl>
- </div><!-- /.troubleshooting -->
- </div><!-- End .main -->
- </div><!-- End #step-2a .step -->
- <div id="step-2b" class="step">
- <div class="main">
- <h3><em>Schritt 2.b</em>Lade den öffentlichen Schlüssel auf den Schlüsselserver hoch</h3>
- <p>Wähle OpenPGP → Schlüsselverwaltung im Menü aus.</p>
- <p>Mache einen Rechtsklick auf deinen Schlüssel und klicke dan auf Öffentlichen Schlüssel Hochladen. Nutze den voreingestellten Schlüsselserver im Pop-up.</p>
- <p class="notes"> Jetzt kann jemand, der dir eine verschlüsselte Nachricht übermitteln möchte, deinen Schlüssel vom Internet herunterladen.</p>
-
- <!-- ~~~~~~~~~ Probleme? ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Der Fortschrittsbalken hört nie auf.</dt>
- <dd>
- Schließe das Pop-Up, überprüfe deine Internetverbindung und probiere es noch einmal. Wenn das nicht funktioniert, versuche es noch einmal und wähle einen anderen Schlüsselserver.</dd>
- <dt>Mein Schlüssel erscheint nicht in der Liste.</dt>
- <dd>Klicke auf das Feld "Standardmäßig alle Schlüssel anzeigen"</dd>
-
- <dt class="feedback">Fidest du keine Lösung für deine Probleme?</dt>
- <dd class="feedback">Frage uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a>.</dd>
- </dl>
- </div><!-- /.troubleshooting -->
- </div>
- </div>
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="terminology" class="step">
- <div class="main">
- <h3>GnuPG, OpenPGP, was?</h3>
- <p>
- Du nutzt ein Programm namens GnuPG, im Menü steht aber OpenPGP. Missverständlich, oder? Die Begriffe GnuPG, GPG, GNU Privacy Guard, OpenPGP und PGP werden oft verwendet, um das gleiche zu bezeichnen, sie haben aber leicht unterschiedliche Bedeutungen.</p>
- </div><!-- End .main -->
- </div><!-- End #terminology.step-->
- </div>
-</section><!-- End #section2 -->
-
-<!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
-<section class="row" id="section3">
- <div>
- <div class="section-intro">
- <h2><em>#3</em> Probiere es aus!</h2>
- <p> Jetzt wirst du mit einem Programm namens Edward kommunizieren, das weiß, wie man E-Mails verschlüsselt.
- Das ist so, als würdest du mit einer echten Person kommunizieren.</p>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
- </div>
- <div class="main">
- <h3><em>Schritt 3.a</em>Schicke Edward deinen öffentlichen Schlüssel</h3>
- <p>Dies ist ein spezieller Schritt, den du nicht machen musst, wenn du mit echten Menschen kommunizierst. Im Menü deines E-Mail programms, gehe auf OpenPGP → Schlüsselverwaltung. Du solltest deinen Schlüssel in der Liste sehen. Klicke auf deinen Schlüssel mit der rechten Maustaste und wähle dann Öffentliche Schlüssel per E-Mail senden. Dies erstellt eine neue Nachricht, so als hättest du auf Schreiben gedrückt.</p>
-
- <p>Schreibe die Nachricht an <a href="mailto:edward-de@fsf.org" >edward-de@fsf.org</a>. Schreibe mindestens ein Wort in den Betreff und in den Körper der E-Mail und klicke auf Senden.</p>
-
- <p class="notes">Es könnte sein, dass Edward einige Minuten braucht, um zurückzuschreiben. Lese derweil die Sektion <a href="#section5">Nutze es richtig</a>. Gehe weiter zum nächsten Schritt, wenn sie geantwortet hat. Ab hier tust du das gleiche wie wenn du mit einer normalen Person kommunizierst.</p>
- </div><!-- End .main -->
- </div><!-- End #Step-3b .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3b" class="step">
- <div class="main">
- <h3><em>Schritt 3.b</em>Sende eine Verschlüsselte E-Mail</h3>
- <p>Schreibe eine E-Mail an <a href="mailto:edward-de@fsf.org" >edward-de@fsf.org</a>. Schreibe "Verschlüsselungstest" oder etwas ähnliches in den Betreff und schreibe irgendetwas in den Text der Nachricht. Schicke sie noch nicht ab.</p>
- <p>
- Klicke auf das Icon mit dem Schlüssel am unteren Rand des Fensters (er sollte gelb werden).
- Das sagt Enigmail, dass die E-Mail verschlüsselt werden soll.
- </p>
- <p>Drücke auf Senden. Es sollte eine Meldung kommen, auf der steht "Nicht gefundene Empfänger".</p>
-
- <p>Um Edward verschlüsselte E-Mails zu senden, benötigst du ihren öffentlichen Schlüssel, also muss Enigmail ihn jetzt vom einem Schlüsselserver herunterladen. Klicke auf Fehlende Schlüssel herunterladen und klicke auf den ersten (Schlüssel-ID C09A61E8), klicke dann auf OK.</p>
-
- <p>
- Jetzt bist du zurück am "Nicht gefundene Empfänger"-Dialog. Jetzt musst du auf OK klicken. Sollte die E-Mail nicht automatisch versendet werden, dann kannst du jetzt auf Senden drücken.
- </p>
- <!-- ~~~~~~~~~ Probleme? ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Enigmail kann Edwards Schlüssel nicht finden.</dt>
- <dd>
- Schließe alle Pop-Ups die seitdem du geklickt hast aufgetreten sind. Vergewissere dich, dass du mit dem Internet verbunden bist und versuche es nochmal. Wenn dies nicht funktioniert, wähle einen anderen Schlüsselserver aus.</dd>
- <dt class="feedback">Fidest du keine Lösung für deine Probleme?</dt>
- <dd class="feedback">Frage uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a>.</dd>
- </dl>
- </div><!-- /.troubleshooting -->
- </div><!-- End .main -->
- </div><!-- End #step-3b .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-headers_unencrypted" class="step">
- <div class="main">
- <h3><em>Wichtig:</em> Der Betreff wird nicht verschlüsselt</h3>
- <p>
- Auch wenn du die E-Mail verschlüsselst, ist der Betreff nicht verschlüsselt, also solltest du dort keine
- privaten Informationen hineinschreiben. Die Sender- und Empfängeradressen sind ebenfalls unverschlüsselt (woher sollte sonst das Programm sonst wissen, wohin die E-Mail geht?).
- </p>
- </div><!-- End .main -->
- </div><!-- End #step-headers_unencrypted .step-->
-
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3c" class="step">
- <div class="main">
- <h3><em>Schritt 3.c</em> Empfange eine Antwort</h3>
- <p>
- Wenn Edward deine E-Mail empfangen hat, entschlüsselt er sie mit ihrem privaten Schlüssel. Dann wird er deinen öffentlichen Schlüssel von einem Schlüsselserver holen und ihn verwenden um die Antwort zu verschlüsseln.
- </p>
- <p class="notes">
- Da du die E-Mail mit Edwards öffentlichen Schlüssel verschlüsselt hast, braucht man Edwards privaten Schlüssel um die E-Mail zu entschlüsseln. Nur Edward besitzt den privaten Schlüssel, aslo kann niemand außer ihr — nicht einmal du — die E-Mail entschlüsseln..
- </p>
- <p class="notes">
- Edward braucht einige Minuten um zu antworten. In der zwischenzeit wäre es eine gute Idee, die Sektion <a href="#section5">Nutze es richtig</a> zu lesen.</p>
- <p>
- Wenn du Edwards E-Mail bekommen und geöffnet hast, stellt Enigmail automatisch fest, dass sie mit deinem öffentlichen Schlüssel verschlüsselt wurde und entschlüsselt dann die E-Mail mit deinem privaten Schlüssel.
- </p>
- <p>
- Beachte die Leiste die über der Nachricht erscheint mit Informationen über Edwards Schlüssel.
- </p>
- </div><!-- End .main -->
- </div><!-- End #step-3c .step -->
-
- <!-- STEP 3D IS COMMENTED OUT UNTIL WE FIND A WAY TO VALIDATE SIGNATURES
- <div id="step-3d" class="step">
- <div class="main">
- <h3><em>Schritt 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>
- </div>-->
- </div>
-</section>
-<!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
-<section class="row" id="section4">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#4</em> Verwende das Web of Trust</h2>
- <p>
- E-Mail-Verschlüsselung ist zwar eine leistungsfähige Technologie, hat aber eine Schwäche: sie braucht eine Möglichkeit um überprüfen zu können, ob die Schlüssel tatsächlich der angegebenen Person gehören. Ansonsten gäbe es keine Art und Weise einen Angreifer davon abzuhalten, Schlüssel mit dem namen deines Freundes zu erstellen und dich glauben zu lassen, er sei dein Freund. Also wurden Signaturen und das Web of Trust erfunden.</p>
-
- <p>Wenn du den Schlüssel von jemandem signierst, dann sagst du öffentlich, dass du glaubst, dass der Schlüssel tatsächlich dieser Person gehört und nicht einem Angreifer. Man kann sehen, wer deinen Schlüssel signiert hast. Wenn du GnuPG einige Jahre lang verwendet hast, kannst du hunderte Signaturen haben. Die Web of Trust ist eine Konstellation aller GnuPG-Nutzer, die durch Signaturenketten zu einem Netz verbunden sind. Je mehr signaturen ein Schlüssel hat, desto vertrauenswürdiger ist er.</p>
-
- <p>Öffentliche Schlüssel werden normalerweiße mit einer 8-stelligen Schlüssel-ID wie C09A61E8 (für Edwards Schlüssel) identifiziert. Du kannst deine Schlüssel-ID in OpenPGP → Key Management im Menü deines E-Mail-Programms sehen. Auf diese Schlüssel-ID sollte man sich jedoch nicht vollständig verlassen, da es Schlüssel geben kann, die die gleiche Schlüssel-ID besitzen.</p>
- <p>
- Es ist einie gute Idee, deine Schlüssel-ID zu verbreiten, sodass Leute einfacher deinen Schlüssel auf dem Schlüsselserver finden können. Du wirst auch öffentliche Schlüssel finden, die mit dem Fingerabdruck identifiziert werden, welcher eine wesentlich längere Zahlenfolge ist, wie F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8. Die Schlüssel-ID besteht nur aus den letzten 8 Stellen des Fingerabdrucks. Dieser Fingerabdruck ist tatsächlich einzigartig.
- </p>
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-4a" class="step">
- <div class="sidebar">
- <p><img src="/img/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Schritt 4.a</em>Signiere einen Schlüssel</h3>
- <p>In deinen E-Mail-Programm, gehe zu OpenPGP → Schlüsselverwaltung.</p>
- <p>Klicke mit der rechten Maustaste auf Edwards öffentlichen Schlüssel und wähle jetzt Unterschreiben.</p>
- <p>In dem Fenster was erscheint, wähle "Keine Antwort" und klicke auf OK.</p>
- <p>Wähle Edwards Schlüssel aus der Liste aus und gehe dann auf Schlüsselserver → Schlüssel Hochladen und klicke auf OK.</p>
- <p class="notes">Du hast gerade gesagt, dass du darauf vertraust, dass Edwards Schlüssel tatsächlich Edward gehört. Dies bedeutet wenig, da Edward keine echte Person ist, ist aber eine gute Praxis.</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" placeholder="xD41A008" name="FROM"></p>
- <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
- <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
- </form>
- </div> -->
-
- </div><!-- End .main -->
- </div><!-- End #step-4a .step -->
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-sign_real_keys" class="step">
- <div class="main">
- <h3><em>Wichtig:</em> Überprüfe die Identität der Leute, deren Schlüssel du signierst.</h3>
- <p>Bevor du einen Schlüssel signierst, überprüfe die Identität des Eigentümers, am besten an einem Ausweis. Hierfür sollte man sich am besten persönlich treffen. Du solltest auf die Frage, wie gut du die Identität überprüft hast, immer mit "Keine Antwort" antworten, da diese Frage wenig nutzen hat und viel mehr Informationen über deine Sozialen Kontakte liefert als normale signaturen.</p>
- </div><!-- End .main -->
- </div><!-- End #step-sign_real_keys .step-->
- </div>
- </div>
-</section><!-- End #section4 -->
-<!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
-<section id="section5" class="row">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#5</em> Nutze es richtig</h2>
- <p>Jeder nutzt GnuPG auf seine Art und Weise, es ist aber wichtig einige einfache Praktiken zu befolgen. Wenn du sie nicht befolgst riskierst du deine eigene Privatsphäre und die deiner Kommunikationspartner. Außerdem beschädigst du die Web of Trust.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-5a" class="step">
- <div class="sidebar">
- <p><img src="/img/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3>Wann sollte ich verschlüsseln?</h3>
-
- <p>
- Je mehr du verschlüsselst, desto besser. Wenn du nur E-Mails hin und wieder verschlüsselt, könnte jede verschlüsselte Nachricht aufmerksamer von den Geheimdiensten verfolgt werden. Wenn alle oder die meisten deiner Nachrichten verschlüsselt sind, wissen die Überwacher nicht, ow sie anfangen sollen.</p>
-
- <p>
- Das heißt nicht, dass nur einige Nachrichten zu verschlüsseln sinnlos ist -- Es ist ein guter Start und macht massiver Überwachung schwieriger.</p>
-
- </div><!-- End .main -->
- </div><!-- End #step-5a .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-5b" class="step">
- <div class="sidebar">
- <p><img src="/img/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Wichtig:</em> Nimm dich vor ungültigen Schlüsseln in Acht!</h3>
- <p>
- GnuPG macht E-Mails sicherer, es ist aber wichtig für ungültige Schlüssel Ausschau zu halten. E-Mails, die mit ungültigen Schlüsseln verschlüsselt wurden könnten von Überwachungsprogrammen gelesen werden. </p>
- <p>
- Gehe in deinem E-Mail-Programm zurück zur zweiten E-Mail, die dir Edward gesendet hat. Weil sie mit ihrem Schlüssel verschlüsselt wurde, gibt es oben eine Leiste die sagt, dass die E-Mail verschlüsselt ist.</p>
- <p><b>
-Gewöhne es dir an, dass du auf diese Leiste schaust. Enigmail wird dich warnen, wenn E-Mails mit ungültigen Schlüsseln verschlüsselt wurden.</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>Speichere dein Widerrufszertifikat an einem sichren Ort.</h3>
- <p>
-Kopiere das Widerrufszertifikat auf das sicherste Speichermedium was du hast. Das ideale wäre ein Flash-Speicher, der an einem sicheren Ort aufbewahrt wird.</p>
- <p>Sollte dein privater Schlüssel gestohlen werden oder verloren gehen, benötigst du dieses Zertifikat.</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>Wichtig:</em> Reagiere schnell, wenn jemand deinen Privaten Schlüssel bekommt!</h3>
- <p> Wenn du deinen privaten Schlüssel verlierst (z.B. jemand klaut deinen Computer) ist es wichtig ihn sofort zu annulieren bevor ihn jemand benutzt, um deine E-Mails zu lesen. Wie dies geht wird in dieser Anleitung nicht beschrieben, du kannst dies aber im <a href="https://www.gnupg.org/gph/de/manual/c319.html#AEN389" >Handbuch von GnuPG</a> nachlesen.</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>Mache deinen öffentlichen Schlüssel zu einem Teil deiner Online-Identität.</h3>
- <p>Füge erst einmal deine Schlüssel-ID zu deiner E-Mail-Signatur hinzu, schriebe dann E-Mails an mindestens fünf deiner Freunde, in denen steht, dass du gerade GnuPG installiert hast und deine Schlüssel-ID. Vergesse nicht, dass es eine tolle <a href="http://de.gpcf.eu/selbstvertidigung" >Infographik</a> gibt, die du mit deinen Freunden teilen kannst.</p>
-
- <p class="notes">
- Schreibe deine Schlüssel-ID überall hin, wo jemand deine E-Mail-Adresse sehen könnte: deine Profile auf sozialen Netzwerken, Blogs, Websiten oder Visitenkarten. Wir müssen unsere Kultur so verändern, dass wir glauben, dass etwas fehlt, wenn wir eine E-Mail-Adresse ohne eine Schlüssel-ID sehen.</p>
- </div><!-- End .main -->
- </div><!-- End #step-5d .step-->
- </div>
-</section>
-
-
-<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
-<section class="row" id="section6">
- <div id="step-click_here" class="step">
- <div class="main">
- <h2><a href="next_steps.html">Klicke hier, wenn du fertig bist</a></h2>
-
- </div><!-- End .main -->
- </div><!-- End #step-click_here .step-->
-
-</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>
- <div class="sidebar">
- <h2>FAQ</h2>
- </div>
-
- <div class="main">
- <dl>
- <dt>My key expired</dt>
- <dd>Answer coming soon.</dd>
-
- <dt>Who can read encrypted messages? Who can read signed ones?</dt>
- <dd>Answer coming soon.</dd>
-
- <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>
- </div>
- </section> --><!-- End #faq -->
-
+++ /dev/null
-<!-- top-bar-gnu.html -->
-<ul id="menu" class="os">
- <li class="spacer">
- <a href="index.html" class="current">GNU/Linux</a>
- </li>
- <li>
- <a href="mac.html">Mac OS</a>
- </li>
- <li>
- <a href="windows.html">Windows</a>
- </li>
+++ /dev/null
-<!-- top-bar-mac -->
-<ul id="menu" class="os">
- <li class="spacer">
- <a href="index.html" >GNU/Linux</a>
- </li>
- <li>
- <a href="mac.html" class="current" >Mac OS</a>
- </li>
- <li>
- <a href="windows.html">Windows</a>
- </li>
+++ /dev/null
-<!-- top-bar-mac -->
-<ul id="menu" class="os">
- <li class="spacer">
- <a href="index.html" >GNU/Linux</a>
- </li>
- <li>
- <a href="mac.html" >Mac OS</a>
- </li>
- <li>
- <a href="windows.html" class="current" >Windows</a>
- </li>
+++ /dev/null
-<!-- win-step.html -->
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-1b" class="step">
-
- <div class="main">
- <h3><em>Schritt 1.b</em> Hole dir GnuPG, indem du GPG4Win herunterlädst</h3>
- <p>GPG4Win ist ein Software-Paket, das GnuPG enthält. <a href="https://www.gpg4win.org">Lade es herunter</a> und installiere es. Wähle immer die Standard-Antworten. Nachdem es installiert wurde, kannst du alle Fenster schließen, die es geöffnet hat.</p>
- </div><!-- End .main -->
-</div><!-- End #step1-b .step -->
-
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
-<div id="step-1c" class="step">
- <div class="sidebar">
- <ul class="images">
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>
- <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>Schritt 1.c</em>Installiere das Enigmail-Plugin für dein E-Mail-Programm</h3>
- <p>
- In dem Menü von deinen Programm, klicke auf Add-ons (es könnte auch im Untermenü "Werkzeuge" sein). Vergewissere dich, dass " Erweiterungen" links ausgewählt wurde. Kannst du Enigmail sehen? Wenn ja, dann überspringe diesen Schritt.</p>
- <p>Wenn nicht, suche "Enigmail" mit Hilfe der Suchleiste. Installiere es. Starte dein E-Mail-Programm anschließend neu.</p>
- <!-- ~~~~~~~~~ Probleme? ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Probleme?</h4>
- <dl>
- <dt>Ich kann das Menü nicht finden.</dt>
- <dd>
- In vielen neuen E-Mail-Programmen wird das Hauptmenü durch drei horizontale Balken dargestellt.</dd>
-
- <dt class="feedback">Fidest du keine Lösung für deine Probleme?</dt>
- <dd class="feedback">Frage uns auf unserer <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Feedback-Seite</a>.</dd>
- </dl>
- </div><!-- /.troubleshooting -->
- </div><!-- End .main -->
-
-</div><!-- End #step-1c .step -->
-</section><!-- End #section1 -->
+++ /dev/null
-<!DOCTYPE html>
-<html>
- <head>
- <meta charset="utf-8">
-
- <title>Email Self-Defense - a guide to fighting surveillance with GnuPG encryption</title>
- <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail" />
- <meta name="description" content="Email surveillance violates our fundamental rights and makes free speech risky. This guide will teach you email self-defense in 30 minutes with GnuPG.">
-
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css">
- <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
-
- </head>
- <body>
-<!--
- <nav class="nav">
- <div>
- <ul class="lang">
- <li class="help"><a href="http://libreplanet.org/wiki/GPG_guide">Translate this guide!</a></li>
- </ul>
- </div>
- </nav>
--->
-
-<!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
-<!-- ~~~~~~~~~ Revision as of 18:53, 1 June 2014 by Zakkai ~~~~~~~~~ -->
- <header class="row" id="header">
-
- <!--<div class="highlight" style="background: red;">
- <h3 style="text-align: center;"><strong style="color: white;">Website Under Construction</strong></h3>
- </div>-->
-
- <div>
- <h1>Email Self-Defense</h1>
- <ul class="os">
- <li><a href="index.html">GNU/Linux</a></li>
- <li><a href="mac.html">Mac OS</a></li>
- <li><a href="windows.html" class="current">Windows</a></li>
- <li class="share"><a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">#EmailSelfDefense</a></li>
- </ul>
-
- <!-- ~~~~~~~~~ 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>
- <span style="font-size:125%"><p>We fight for computer user's rights, and promote the development of free (as in freedom) software. Resisting bulk surveillance is very important to us.</p><p><strong>We want to heavily promote tools like this in-person and online, to help as many people as possible take the first step towards using free software to protect their privacy. Can you make a donation or become a member to help us achieve this goal?</strong></p></span>
-
- <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/donate.en.png"></a> <a href="https://u.fsf.org/yr"><img alt="Join now" src="//static.fsf.org/nosvn/enc-dev0/img/join.en.png"></a></p>
-
- </div><!-- End #fsf-intro -->
-
- <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
- <div class="intro">
- <p>
- <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/infographic-button.png" alt="View & share our infographic →" /></a>
- Bulk surveillance violates our fundamental rights and makes free speech risky. This guide will teach you a basic surveillance self-defense skill: email encryption. 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 that intercepts your email can't read it. All you need is a computer with an Internet connection, an email account and about half an hour.</p>
-
-<p>Even if you have nothing to hide, using encryption helps protect the privacy of people you communicate with, and makes life difficult for bulk surveillance systems. If you do have something important to hide, you're in good company; these are the same tools that Edward Snowden used to share his famous secrets about the NSA.</p>
-
-<p>In addition to using encryption, standing up to surveillance requires fighting politically for a <a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">reduction in the amount of data collected on us</a>, but the essential first step is to protect yourself and make surveillance of your communication as difficult as possible. Let's get started!</p>
-
- </div>
- </div>
- </header><!-- End #header -->
-
-<!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
- <section class="row" id="section1">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#1</em> Get the pieces</h2>
- <p class="notes">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). To defend your freedom as well as protect yourself from surveillance, we recommend you switch to a free software operating system like GNU/Linux. Learn more about free software at <a href="https://u.fsf.org/ys">fsf.org</a>.</p>
- <p>To get started, you'll need a desktop email program installed on your computer. This guide works with free software versions of the Thunderbird email program, and with Thunderbird itself. Email programs are another way to access the same email accounts you can access in a browser (like GMail), but provide extra features.</p>
- <p>If you are already have one of these, you can skip to <a href="#step-1b">Step 1.b</a>.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-1a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Step 1.a</em> Set your email program up with your email account (if it isn't already)</h3>
- <p>Open your email program and follow the wizard that sets it up with your email account.</p>
-
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <dl>
- <dt>What's a wizard?</dt>
- <dd>A wizard is a series of windows that pop up to make it easy to get something done on a computer, like installing a program. You click through it, selecting options as you go.</dd>
- <dt>My email program can't find my account or isn't downloading my mail</dt>
- <dd>Before searching the Web, we recommend you start by asking other people who use your email system, to figure out the correct settings.</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 #step1-a .step -->
-
-<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-1b" class="step">
-
- <div class="main">
- <h3><em>Step 1.b</em> Get GnuPG by downloading GPG4Win</h3>
- <p>GPG4Win is a software package that includes GnuPG. <a href="https://www.gpg4win.org">Download</a> and install it, choosing default options whenever asked. After it's installed, you can close any windows that it creates.</p>
-
- </div><!-- End .main -->
- </div><!-- End #step1-b .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-1c" class="step">
- <div class="sidebar">
- <ul class="images">
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>
- <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.c</em> Install the Enigmail plugin for your email program</h3>
- <p>In your email program's menu, select Add-ons (it may be in the Tools section). Make sure Extensions is selected on the left. Do you see Enigmail? if so, skip this step.</p>
- <p>If not, search "Enigmail" with the search bar in the upper right. You can take it from here. Restart your email program when you're done.</p>
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <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>
- </section><!-- End #section1 -->
-
-<!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
- <section class="row" id="section2">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#2</em> Make your keys</h2>
- <p>To use the GnuPG system, you'll need a public key and a private key (known together as a keypair). Each is a long string of randomly generated numbers and letters that are unique to you. Your public and private keys are linked together by a special mathematical function.</p>
-
-<p>Your public key isn't like a physical key, because it's stored in the open in an online directory called a keyserver. People download it and use it, along with GnuPG, to encrypt emails they send to you. You can think of the keyserver as phonebook, where people who want to send you an encrypted email look up your public key.</p>
-
-<p>Your private key is more like a physical key, because you keep it to yourself (on your computer). You use GnuPG and your private key to decode encrypted emails other people send to you.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-2a" class="step">
- <div class="sidebar">
- <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>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 12 characters and include at least one lower case and upper case letter and at least one number or punctuation symbol. Don't forget the password, or all this work will be wasted!</p>
- <p class="notes">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 <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>
-
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <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 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-2a .step -->
- <div id="step-2b" class="step">
- <div class="main">
- <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
- <p>In your email program's menu, select OpenPGP → Key Management.</p>
-<p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
-<p class="notes">Now someone who wants to send you an encrypted message can download your public key from the Internet. There are multiple keyservers that you can select from the menu when you upload, but they are all copies of each other, so it doesn't matter which one you use. However, it sometimes takes a few hours for them to match each other when a new key is uploaded.</p>
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <dl>
- <dt>The progress bar never finishes</dt>
- <dd>Close the upload popup, make sure you are on the Internet and try again. If that doesn't work, try again, selecting a different keyserver.</dd>
-<dt>My key doesnt appear in the list</dt>
- <dd>Try checking Show Default Keys.</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-2a .step -->
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="terminology" class="step">
- <div class="main">
- <h3>GnuPG, OpenPGP, what?</h3>
- <p>You're using a program called GnuPG, but the menu in your email program is called OpenPGP. Confusing, right? In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used interchangeably, though they all have slightly different meanings.</p>
- </div><!-- End .main -->
- </div><!-- End #terminology.step-->
- </div>
- </section><!-- End #section2 -->
-
-<!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
- <section class="row" id="section3">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#3</em> Try it out!</h2>
- <p>Now you'll try a test correspondence with a computer program named Adele, which knows how to use encryption. Except where noted, these are the same steps you'd follow when corresponding with a real, live person.</p>
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Step 3.a</em> Send Adele your public key</h3>
- <p>This is a special step that you won't have to do when corresponding with real people. In your email program's menu, go to OpenPGP → Key Management. You should see your key in the list that pops up. Right click on your key and select Send Public Keys by Email. This will create a new draft message, as if you had just hit the Write button.</p>
-
-<p>Address the message to adele-en@gnupp.de. Put at least one word (whatever you want) in the subject and body of the email, then hit send.</p>
-
-<p class="notes">It may take two or three minutes for Adele to respond. In the meantime, you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section of this guide. Once she's responded, head to the next step. From here on, you'll be doing just the same thing as when corresponding with a real person.</p>
- </div><!-- End .main -->
- </div><!-- End #step-3b .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3b" class="step">
- <div class="main">
- <h3><em>Step 3.b</em> Send a test encrypted email</h3>
- <p>Write a new email in your email program, addressed to adele-en@gnupp.de. Make the subject "Encryption test" or something similar and write something in the body. Don't send it yet.</p>
- <p>Click the icon of the key in the bottom right of the composition window (it should turn yellow). This tells Enigmail to encrypt the email with the key you downloaded in the last step.</p>
- <p class="notes">Next to the key, you'll notice an icon of a pencil. Clicking this tells Enigmail to add a special, uniqe signature to your message, generated using your private key. This is a separate feature from encryption, and you don't have to use it for this guide.</p>
-<p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
-
- <p>To encrypt and email to Adele, you need her public key, and so now you'll have Enigmail download it from a keyserver. Click Download Missing Keys and use the default in the pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key ID starting with C), then select ok. Select ok in the next pop-up.</p>
-
- <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Select Adele's key from the list and click Ok. If the message doesn't send automatically, you can hit send now.</p>
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
- <div class="troubleshooting">
- <h4>Troubleshooting</h4>
- <dl>
- <dt>Enigmail can't find Adele's key</dt>
- <dd>Close the pop-ups that have appeared since you clicked. Make sure you are connected to the Internet and try again. If that doesn't work, repeat the process, choosing a different keyserver when it asks you to pick one.</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 -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-headers_unencrypted" class="step">
- <div class="main">
- <h3><em>Important:</em> Security tips</h3>
- <p>Even if you encrypted your email, the subject line is not encrypted, so don't put private information there. The sending and receiving addresses aren't encrypted either, so they could be read by a surveillance system. When you send attachments, Enigmail will give you an option of whether you want to encrypt them.</p>
-<p>It's also good practice to click the key icon in your email composition window <strong>before</strong> you start to write. Otherwise, your email client could save an unencrypted draft on the mail server, potentially exposing it to snooping.</p>
- </div><!-- End .main -->
- </div><!-- End #step-headers_unencrypted .step-->
-
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-3c" class="step">
- <div class="main">
- <h3><em>Step 3.c</em> Receive a response</h3>
- <p>When Adele receives your email, she will use her private key to decrypt it, then fetch your public key from a keyserver and use it to encrypt a response to you.</p>
- <p class="notes">Since you encrypted this email with Adele's public key, Adele's private key is required to decrypt it. Adele is the only one with her private key, so no one except her — not even you — can decrypt it.</p>
- <p class="notes">It may take two or three minutes for Adele to respond. In the meantime, you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section of this guide.</p>
- <p>When you receive Adele's email and open it, Enigmail will automatically detect that it is encrypted with your public key, and then it will use your private key to decrypt it.</p>
- <p>Notice the bar that Enigmail shows you above the message, with information about the status of Adele's key.</p>
- </div><!-- End .main -->
- </div><!-- End #step-3c .step -->
-
-<!-- STEP 3D IS COMMENTED OUT UNTIL WE FIND A WAY TO VALIDATE SIGNATURES
- <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>
- </div>-->
- </div>
- </section><!-- End #section3 -->
-
-
-<!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
- <section class="row" id="section4">
- <div>
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
- <div class="section-intro">
- <h2><em>#4</em> Learn the Web of Trust</h2>
- <p>Email encryption is a powerful technology, but it has a weakness; it requires a way to verify that a person's public key is actually theirs. Otherwise, there would be no way to stop an attacker from making an email address with your friend's name, creating keys to go with it and impersonating your friend. That's why the free software programmers that developed email encryption created keysigning and the Web of Trust.</p>
-
-<p>When you sign someone's key, you are publicly saying that you trust that it does belong to them and not an impostor. People who use your public key can see the number of signatures it has. Once you've used GnuPG for a long time, you may have hundreds of signatures. The Web of Trust is the constellation of all GnuPG users, connected to each other by chains of trust expressed through signatures, into a giant network. The more signatures a key has, and the more signatures its signers' keys have, the more trustworthy that key is.</p>
-
-<p>People's public keys are usually identified by their key fingerprint, which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Adele's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to OpenPGP → Key Management in your email program's menu, then right clicking on the key and choosing Key Properties. It's good practice to share your fingerprint wherever you share your email address, so that so that people can double-check that they have the correct public key when they download yours from a keyserver.</p>
-
-<p class="notes">You may also see public keys referred to by their key ID, which is simply the last 8 digits of the fingerprint, like C09A61E8 for Adele. The key ID is visible directly from the Key Management Window. This key ID is like a person's first name (it is a useful shorthand but may not be unique to a given key), whereas the fingerprint actually identifies the key uniquely without the possibility of confusion. If you only have the key ID, you can still look up the key (as well as its fingerprint), like you did in Step 3, but if multiple options appear, you'll need the fingerprint of the person to are trying to communicate to verify which one to use.</p>
-
-
- </div><!-- End .section-intro -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-4a" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
- </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>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 class="notes">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, but it's good practice.</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" placeholder="xD41A008" name="FROM"></p>
- <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" 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 -->
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-sign_real_keys" class="step">
- <div class="main">
- <h3><em>Important:</em> check people's identification before signing their keys</h3>
- <p>Before signing a real person's key, always make sure it actually belongs to them, and that they are who they say they are. Ask them to show you their ID (unless you trust them very highly) and their public key fingerprint -- not just the shorter public key ID, which could refer to another key as well. In Enigmail, 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>
- </div><!-- End .main -->
- </div><!-- End #step-sign_real_keys .step-->
-
-
-
- </div>
- </section><!-- End #section4 -->
-
-<!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
- <section id="section5" class="row">
- <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="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <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.</p>
-
- </div><!-- End .main -->
- </div><!-- End #step-5a .step -->
-
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
- <div id="step-5b" class="step">
- <div class="sidebar">
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
- </div><!-- /.sidebar -->
- <div class="main">
- <h3><em>Important:</em> Be wary of invalid keys</h3>
- <p>GnuPG makes email safer, but it's still important to watch out for invalid keys, 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 Adele encrypted it with your public 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>Copy your revocation certificate to somewhere safe</h3>
- <p>Remember when you created your keys and saved the revocation certificate that GnuPG made? It's time to copy that certificate 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 read your encrypted email. This guide doesn't cover how to revoke a key, but you can follow the <a href="https://www.gnupg.org/gph/en/manual.html#AEN305">instructions on the GnuPG site</a>. 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 your public key part of your online identity</h3>
- <p> First add your public key fingerprint to your email signature, then compose an email to at least five of your friends, telling them you just set up GnuPG and mentioning your public key fingerprint. Link to this guide and ask them to join you. Don't forget that there's also an awesome <a href="infographic.html">infographic to share.</a></p>
-
-<p class="notes">Start writing your public key fingerprint anywhere someone would see your email address: your social media profiles, blog, Website, or business card. (At the Free Software Foundation, we put ours on our <a href="https://fsf.org/about/staff">staff page</a>.) 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 fingerprint.</p>
- </div><!-- End .main
- </div><!-- End #step-5d .step-->
-
-
- </div>
- </section><!-- End #section5 -->
-
-<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
- <section class="row" id="section6">
- <div id="step-click_here" class="step">
- <div class="main">
- <h2><a href="next_steps.html">Click here when you're done</a></h2>
-
- </div><!-- End .main -->
- </div><!-- End #step-click_here .step-->
-
- </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>
- <div class="sidebar">
- <h2>FAQ</h2>
- </div>
-
- <div class="main">
- <dl>
- <dt>My key expired</dt>
- <dd>Answer coming soon.</dd>
-
- <dt>Who can read encrypted messages? Who can read signed ones?</dt>
- <dd>Answer coming soon.</dd>
-
- <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>
- </div>
- </section> --><!-- End #faq -->
-
-<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
- <footer class="row" id="footer">
- <div>
- <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 © 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>
- <p><em>Version 2.0, launched 6/18/2014. <!--LANGUAGE translation by NAME, NAME and NAME.--></em></p>
-<p>The images on this page are under a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 license (or later version)</a>, and the rest of it is under a <a href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons Attribution-ShareAlike 4.0 license (or later version)</a>. — <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
- <p>Download the source packages for <a href="gnupg-guide.zip">this guide</a> and for <a href="gnupg-infographic.zip">the infographic</a>. Fonts used in the guide & infographic: <a href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo Impallari, <a href="http://www.google.com/fonts/specimen/Signika">Signika</a> by Anna Giedryś <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="http://www.thegopherarchive.com/gopher-files-hacks-pxl2000-119351.htm">PXL-2000</a> by Florian Cramer.</p>
- <p>
- <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
- rel="jslicense">
- JavaScript license information
- </a>
- </p>
- </div><!-- /#copyright -->
- <p class="credits">
- Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" alt="Journalism++" /></a>
- </p><!-- /.credits -->
- </div>
- </footer><!-- End #footer -->
-
- <script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
- <script src="//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>
projects / enc-live.git / commitdiff