de: step 5 translated
[enc-live.git] / de / rest.html
1 <!-- begin rest.html -->
2 <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
3 <section class="row" id="section2">
4 <div>
5 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
6 <div class="section-intro">
7 <h2><em>#2</em> Make your keys</h2>
8 <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>
9
10 <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>
11
12 <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>
13 </div><!-- End .section-intro -->
14
15 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
16 <div id="step-2a" class="step">
17 <div class="sidebar">
18 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>
19 </div><!-- /.sidebar -->
20 <div class="main">
21 <h3><em>Step 2.a</em> Make a keypair</h3>
22 <p>In your email program's menu, select OpenPGP &rarr; Setup Wizard. You don't need to read the text in the window that pops up unless you'd like to, but it's good to read the text on the later screens of the wizard.</p>
23 <p>On the second screen, titled "Signing," select "No, I want to create per-recipient rules for emails that need to be signed."</p>
24 <p>Use the default options until you reach the screen titled "Create Key".</p>
25 <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>
26 <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>
27 <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>
28
29 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
30 <div class="troubleshooting">
31 <h4>Troubleshooting</h4>
32 <dl>
33 <dt>I can't find the OpenPGP menu.</dt>
34 <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>
35 <dt>The wizard says that it cannot find GnuPG.</dt>
36
37 <dd>Open whatever program you usually use for installing software, and search for GnuPG, then install it. Then restart the Engimail setup wizard by going to OpenPGP &rarr; Setup Wizard.</dd>
38
39 <dt class="feedback">Don't see a solution to your problem?</dt>
40 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
41 </dl>
42 </div><!-- /.troubleshooting -->
43 </div><!-- End .main -->
44 </div><!-- End #step-2a .step -->
45
46 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
47 <div id="step-2b" class="step">
48 <div class="main">
49 <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
50 <p>In your email program's menu, select OpenPGP &rarr; Key Management.</p>
51 <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
52 <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>
53 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
54 <div class="troubleshooting">
55 <h4>Troubleshooting</h4>
56 <dl>
57 <dt>The progress bar never finishes</dt>
58 <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>
59 <dt>My key doesnt appear in the list</dt>
60 <dd>Try checking Show Default Keys.</dd>
61
62 <dt class="feedback">Don't see a solution to your problem?</dt>
63 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
64
65 </dl>
66 </div><!-- /.troubleshooting -->
67 </div><!-- End .main -->
68 </div><!-- End #step-2a .step -->
69 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
70 <div id="terminology" class="step">
71 <div class="main">
72 <h3>GnuPG, OpenPGP, what?</h3>
73 <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>
74 </div><!-- End .main -->
75 </div><!-- End #terminology.step-->
76
77
78 </div>
79 </section><!-- End #section2 -->
80
81 <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
82 <section class="row" id="section3">
83 <div>
84 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
85 <div class="section-intro">
86 <h2><em>#3</em> Try it out!</h2>
87 <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>
88 </div><!-- End .section-intro -->
89
90 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
91 <div id="step-3a" class="step">
92 <div class="sidebar">
93 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
94 </div><!-- /.sidebar -->
95 <div class="main">
96 <h3><em>Step 3.a</em> Send Adele your public key</h3>
97 <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 &rarr; 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>
98
99 <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>
100
101 <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>
102 </div><!-- End .main -->
103 </div><!-- End #step-3b .step -->
104
105 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
106 <div id="step-3b" class="step">
107 <div class="main">
108 <h3><em>Step 3.b</em> Send a test encrypted email</h3>
109 <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>
110 <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>
111 <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>
112 <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
113
114 <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 9), then select ok. Select ok in the next pop-up.</p>
115
116 <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>
117 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
118 <div class="troubleshooting">
119 <h4>Troubleshooting</h4>
120 <dl>
121 <dt>Enigmail can't find Adele's key</dt>
122 <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>
123 <dt class="feedback">Don't see a solution to your problem?</dt>
124 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
125 </dl>
126 </div><!-- /.troubleshooting -->
127 </div><!-- End .main -->
128 </div><!-- End #step-3b .step -->
129
130 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
131 <div id="step-headers_unencrypted" class="step">
132 <div class="main">
133 <h3><em>Important:</em> Security tips</h3>
134 <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>
135 <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>
136 </div><!-- End .main -->
137 </div><!-- End #step-headers_unencrypted .step-->
138
139
140 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
141 <div id="step-3c" class="step">
142 <div class="main">
143 <h3><em>Step 3.c</em> Receive a response</h3>
144 <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>
145 <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 &mdash; not even you &mdash; can decrypt it.</p>
146 <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>
147 <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>
148 <p>Notice the bar that Enigmail shows you above the message, with information about the status of Adele's key.</p>
149 </div><!-- End .main -->
150 </div><!-- End #step-3c .step -->
151
152 <!-- STEP 3D IS COMMENTED OUT UNTIL WE FIND A WAY TO VALIDATE SIGNATURES
153 <div id="step-3d" class="step">
154 <div class="main">
155 <h3><em>Step 3.d</em> Send a test signed email to a friend</h3>
156 <p>Write a new email in your email program, addressed to a friend. If you want, tell them about this guide!</p>
157 <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>
158 <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>
159 </div>
160 </div>-->
161 </div>
162 </section><!-- End #section3 -->
163
164 <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
165 <section class="row" id="section4">
166 <div>
167 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
168 <div class="section-intro">
169 <h2><em>#4</em> Verwende das Web of Trust</h2>
170 <p>
171 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>
172
173 <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>
174
175 <p>Öffentliche Schlüssel werden normalerweiße mit einer 8-stelligen Schlüssel-ID wie 92AB3FF7 (für Adeles Schlüssel) identifiziert. Du kannst deine Schlüssel-ID in OpenPGP &rarr; 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>
176 <p>
177 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 DD878C06E8C2BEDDD4A440D3E573346992AB3FF7. Die Schlüssel-ID besteht nur aus den letzten 8 Stellen des Fingerabdrucks. Dieser Fingerabdruck ist tatsächlich einzigartig.
178 </p>
179
180 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
181 <div id="step-4a" class="step">
182 <div class="sidebar">
183 <p><img src="/img/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
184 </div><!-- /.sidebar -->
185 <div class="main">
186 <h3><em>Schritt 4.a</em>Signiere einen Schlüssel</h3>
187 <p>In deinen E-Mail-Programm, gehe zu OpenPGP &rarr; Schlüsselverwaltung.</p>
188 <p>Klicke mit der rechten Maustaste auf Adeles öffentlichen Schlüssel und wähle jetzt Unterschreiben.</p>
189 <p>In dem Fenster was erscheint, wähle "Keine Antwort" und klicke auf OK.</p>
190 <p>Wähle Adeles Schlüssel aus der Liste aus und gehe dann auf Schlüsselserver &rarr; Schlüssel Hochladen und klicke auf OK.</p>
191 <p class="notes">Du hast gerade gesagt, dass du darauf vertraust, dass Adeles Schlüssel tatsächlich Adele gehört. Dies bedeutet wenig, da Adele keine echte Person ist, ist aber eine gute Praxis.</p>
192
193
194 <!--<div id="pgp-pathfinder">
195 <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
196 <p><strong>From:</strong> <input type="text" placeholder="xD41A008" name="FROM"></p>
197 <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
198 <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
199 </form>
200 </div><!-- End #pgp-pathfinder -->
201
202 </div><!-- End .main -->
203 </div><!-- End #step-4a .step -->
204 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
205 <div id="step-sign_real_keys" class="step">
206 <div class="main">
207 <h3><em>Wichtig:</em> Überprüfe die Identität der Leute, deren Schlüssel du signierst.</h3>
208 <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>
209 </div><!-- End .main -->
210 </div><!-- End #step-sign_real_keys .step-->
211
212
213
214 </div>
215 </section><!-- End #section4 -->
216 <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
217 <section id="section5" class="row">
218 <div>
219 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
220 <div class="section-intro">
221 <h2><em>#5</em>Nutze es richtig</h2>
222 <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>
223 </div><!-- End .section-intro -->
224
225 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
226 <div id="step-5a" class="step">
227 <div class="sidebar">
228 <p><img src="/img/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well" /></p>
229 </div><!-- /.sidebar -->
230 <div class="main">
231 <h3>Wann sollte ich verschlüsseln?</h3>
232
233 <p>
234 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>
235
236 <p>
237 Das heißt nicht, dass nur einige Nachrichten zu verschlüsseln sinnlos ist -- Es ist ein guter Start und macht massiver Überwachung schwieriger.</p>
238
239 </div><!-- End .main -->
240 </div><!-- End #step-5a .step -->
241
242 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
243 <div id="step-5b" class="step">
244 <div class="sidebar">
245 <p><img src="/img/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
246 </div><!-- /.sidebar -->
247 <div class="main">
248 <h3><em>Wichtig:</em> Nimm dich vor ungültigen Schlüsseln in Acht!</h3>
249 <p>
250 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>
251 <p>
252 Gehe in deinem E-Mail-Programm zurück zur zweiten E-Mail, die dir Adele 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>
253 <p><b>
254 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>
255 </div><!-- End .main -->
256 </div><!-- End #step-5b .step -->
257
258 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
259 <div id="step-5c" class="step">
260 <div class="main">
261 <h3>Speichere dein Widerrufszertifikat an einem sichren Ort.</h3>
262 <p>
263 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>
264 <p>Sollte dein privater Schlüssel gestohlen werden oder verloren gehen, benötigst du dieses Zertifikat.</p>
265 </div><!-- End .main -->
266 </div><!-- End #step-5c .step -->
267
268 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
269 <div id="step-lost_key" class="step">
270 <div class="main">
271 <h3><em>Wichtig:</em> Reagiere schnell, wenn jemand deinen Privaten Schlüssel bekommt!</h3>
272 <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>
273 </div><!-- End .main -->
274 </div><!-- End #step-lost_key .step-->
275
276 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
277 <div id="step-5d" class="step">
278 <div class="main">
279 <h3>Mache deinen öffentlichen Schlüssel zu einem Teil deiner Online-Identität.</h3>
280 <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>
281
282 <p class="notes">
283 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>
284 </div><!-- End .main -->
285 </div><!-- End #step-5d .step-->
286
287
288
289 <!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
290 <section class="row" id="section6">
291 <div id="step-click_here" class="step">
292 <div class="main">
293 <h2><a href="next_steps.html">Click here when you're done</a></h2>
294
295 </div><!-- End .main -->
296 </div><!-- End #step-click_here .step-->
297
298 </section><!-- End #section6 -->
299
300 <!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
301 <!-- When un-commenting this section go to main.css and search
302 for /* Guide Sections Background */ then add #faq to the desired color
303
304 <section class="row" id="faq">
305 <div>
306 <div class="sidebar">
307 <h2>FAQ</h2>
308 </div>
309
310 <div class="main">
311 <dl>
312 <dt>My key expired</dt>
313 <dd>Answer coming soon.</dd>
314
315 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
316 <dd>Answer coming soon.</dd>
317
318 <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>
319 <dd>Answer coming soon.</dd>
320 </dl>
321 </div>
322 </div>
323 </section> --><!-- End #faq -->
324