Commit | Line | Data |
---|---|---|
5f3af91b TG |
1 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" |
2 | "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> | |
3 | <!-- Generated by GNUN --> | |
4 | <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> | |
5 | <head> | |
6 | <meta http-equiv="content-type" content="text/html; charset=utf-8" /> | |
7 | <title>mac-diff.html</title> | |
8 | <style type="text/css"> | |
9 | span.removed { background-color: #f22; color: #000; } | |
10 | span.inserted { background-color: #2f2; color: #000; } | |
11 | </style></head> | |
12 | <body><pre> | |
13 | <!DOCTYPE html> | |
14 | <html> | |
15 | <head> | |
16 | <meta charset="utf-8" /> | |
17 | ||
18 | <title>Email Self-Defense - a guide to fighting surveillance with GnuPG encryption</title> | |
19 | ||
20 | <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail" /> | |
21 | <meta name="description" content="Email surveillance violates our fundamental rights and makes | |
22 | free speech risky. This guide will teach you email self-defense in 30 minutes with GnuPG." /> | |
23 | <meta name="viewport" content="width=device-width, initial-scale=1" /> | |
24 | <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" /> | |
25 | <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" /> | |
26 | </head> | |
27 | ||
28 | <body> | |
29 | <!-- <nav class="nav"> | |
30 | <div> | |
31 | <ul class="lang"> | |
32 | <li class="help"><a href="http://libreplanet.org/wiki/GPG_guide">Translate this | |
33 | guide!</a></li> | |
34 | </ul> | |
35 | ||
36 | </div> | |
37 | </nav> | |
38 | --> | |
39 | ||
40 | <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ --> | |
41 | <header class="row" id="header"><div> | |
42 | ||
43 | <h1>Email Self-Defense</h1> | |
44 | ||
45 | <!-- Language list for browsers that do not have JS enabled --> | |
46 | <ul id="languages" class="os"> | |
47 | <li><a class="current" href="/en">english</a></li> | |
48 | <li><a href="/es">español</a></li> | |
49 | <li><a href="/fr">français</a></li> | |
50 | <li><a href="/de">deutsch</a></li> | |
51 | <li><a href="/it">italiano</a></li> | |
52 | <li><a href="/pt-br">português do Brasil</a></li> | |
53 | <li><a href="/tr">türkçe</a></li> | |
54 | <li><a href="/ro">română</a></li> | |
55 | <li><a href="/ru">русский</a></li> | |
56 | <!--<li><a href="/ml">മലയാളം</a></li>--> | |
57 | <!--<li><a href="/ko">한국어</a></li>--> | |
58 | <li><a href="/ja">日本語</a></li> | |
59 | <li><a href="/el">ελληνικά</a></li> | |
60 | <!--<li><a href="/ar">العربية</a></li>--> | |
61 | </ul> | |
62 | ||
63 | <ul id="menu" class="os"> | |
64 | <li class="spacer"> <a href="index.html">GNU/Linux</a> </li> | |
65 | <li> <a href="mac.html" class="current">Mac OS</a> </li> | |
66 | <li> <a href="windows.html">Windows</a> </li> | |
67 | <li class="spacer"> <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email | |
68 | encryption for everyone via %40fsf"> Share <img | |
69 | src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png" class="share-logo" | |
70 | alt="[GNU Social]"> <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png" | |
71 | class="share-logo" | |
72 | alt="[Pump.io]"> <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png" | |
73 | class="share-logo" | |
74 | alt="[Reddit]"> <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png" | |
75 | class="share-logo" | |
76 | alt="[Hacker News]"> | |
77 | </a> </li> | |
78 | </ul> | |
79 | ||
80 | <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ --> | |
81 | <div id="fsf-intro"> | |
82 | ||
83 | <h3><a href="http://u.fsf.org/ys"><img | |
84 | alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" | |
85 | /></a></h3> | |
86 | ||
87 | <span style="font-size:125%"> | |
88 | ||
89 | <p>We fight for computer users' rights, and promote the development of free (as in freedom) | |
90 | software. Resisting bulk surveillance is very important to us.</p> | |
91 | ||
92 | <p><strong>We want to translate this guide into more languages, and make a version for | |
93 | encryption on mobile devices. Please donate, and help people around the world take the | |
94 | first step towards protecting their privacy with free software.</strong></p> | |
95 | ||
96 | </span> | |
97 | ||
98 | <p><a | |
99 | href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img | |
100 | alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a> </p> | |
101 | ||
102 | </div><!-- End #fsf-intro --> | |
103 | ||
104 | <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ --> | |
105 | <div class="intro"> | |
106 | ||
107 | <p> <a id="infographic" href="infographic.html"><img | |
108 | src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png" | |
109 | alt="View & share our infographic →" /></a> Bulk surveillance violates | |
110 | our fundamental rights and makes free speech risky. This guide will teach you a basic | |
111 | surveillance self-defense skill: email encryption. Once you've finished, you'll be able to | |
112 | send and receive emails that are coded to make sure a surveillance agent or thief intercepting | |
113 | your email can't read it. All you need is a computer with an Internet connection, an email | |
114 | account, and about half an hour.</p> | |
115 | ||
116 | <p>Even if you have nothing to hide, using encryption helps protect the privacy of people | |
117 | you communicate with, and makes life difficult for bulk surveillance systems. If you do | |
118 | have something important to hide, you're in good company; these are the same tools that | |
119 | Edward Snowden used to share his famous secrets about the NSA.</p> | |
120 | ||
121 | <p>In addition to using encryption, standing up to surveillance requires fighting politically | |
122 | for a <a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">reduction in the | |
123 | amount of data collected on us</a>, but the essential first step is to protect yourself | |
124 | and make surveillance of your communication as difficult as possible. Let's get started!</p> | |
125 | ||
126 | </div><!-- End .intro --> | |
127 | </div></header><!-- End #header --> | |
128 | ||
129 | <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ --> | |
130 | <section class="row" id="section1"><div> | |
131 | ||
132 | <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ --> | |
133 | <div class="section-intro"> | |
134 | ||
135 | <h2><em>#1</em> Get the pieces</h2> | |
136 | ||
137 | <p class="notes">This guide relies on software which is freely licensed; it's | |
138 | completely transparent and anyone can copy it or make their own version. This makes | |
139 | it safer from surveillance than proprietary software (like Mac OS). To defend your | |
140 | freedom as well as protect yourself from surveillance, we recommend you switch to a | |
141 | free software operating system like GNU/Linux. Learn more about free software at <a | |
142 | href="https://u.fsf.org/ys">fsf.org</a>.</p> | |
143 | ||
144 | <p>To get started, you'll need a desktop email program installed on your computer. This guide | |
145 | works with free software versions of the Thunderbird email program, and with Thunderbird | |
146 | itself. Email programs are another way to access the same email accounts you can access | |
147 | in a browser (like Gmail), but provide extra features.</p> | |
148 | ||
149 | <p>If you already have <span class="removed"><del><strong>one of these,</strong></del></span> <span class="inserted"><ins><em>an email program,</em></ins></span> you can skip to <a href="#step-1b">Step 1.b</a>.</p> | |
150 | ||
151 | </div><!-- End .section-intro --> | |
152 | ||
153 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
154 | <div id="step-1a" class="step"> | |
155 | <div class="sidebar"> | |
156 | ||
157 | <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" | |
158 | alt="Step 1.A: Install Wizard" /></p> | |
159 | ||
160 | </div><!-- /.sidebar --> | |
161 | <div class="main"> | |
162 | ||
163 | <h3><em>Step 1.a</em> Setup your email program with your email <span class="removed"><del><strong>account (if it isn't | |
164 | already)</h3></strong></del></span> <span class="inserted"><ins><em>account</h3></em></ins></span> | |
165 | ||
166 | <p>Open your email program and follow the wizard <span class="inserted"><ins><em>(step-by-step walkthrough)</em></ins></span> that sets it | |
167 | up with your email account.</p> | |
168 | ||
169 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
170 | <div class="troubleshooting"> | |
171 | ||
172 | <h4>Troubleshooting</h4> | |
173 | ||
174 | <dl> | |
175 | <span class="removed"><del><strong><dt>What's a wizard?</dt> | |
176 | ||
177 | <dd>A</strong></del></span> | |
178 | <span class="inserted"><ins><em><dt>The</em></ins></span> wizard <span class="inserted"><ins><em>doesn't launch</dt> | |
179 | ||
180 | <dd>You can launch the wizard yourself, but the menu option for doing so</em></ins></span> is <span class="removed"><del><strong>a series of windows that pop up</strong></del></span> <span class="inserted"><ins><em>named differently | |
181 | in each email programs. The button</em></ins></span> to <span class="removed"><del><strong>make</strong></del></span> <span class="inserted"><ins><em>launch</em></ins></span> it <span class="removed"><del><strong>easy to get</strong></del></span> <span class="inserted"><ins><em>will be in the program's main menu, under | |
182 | "New" or something similar, titled</em></ins></span> something <span class="removed"><del><strong>done on | |
183 | a computer,</strong></del></span> like <span class="removed"><del><strong>installing a program. You click through it, selecting options as you go.</dd> | |
184 | ||
185 | <dt>My</strong></del></span> <span class="inserted"><ins><em>"Add account" or "New/Existing</em></ins></span> email <span class="removed"><del><strong>program</strong></del></span> | |
186 | <span class="inserted"><ins><em>account."</dd> | |
187 | ||
188 | <dt>The wizard</em></ins></span> can't find my account or isn't downloading my mail</dt> | |
189 | ||
190 | <dd>Before searching the Web, we recommend you start by asking other people who use your | |
191 | email system, to figure out the correct settings.</dd> | |
192 | ||
193 | <dt class="feedback">Don't see a solution to your problem?</dt> | |
194 | ||
195 | <dd class="feedback">Please let us know on the <a | |
196 | href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd> | |
197 | </dl> | |
198 | ||
199 | </div><!-- /.troubleshooting --> | |
200 | </div><!-- End .main --> | |
201 | </div><!-- End #step1-a .step --> | |
202 | ||
203 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
204 | <div id="step-1b" class="step"> | |
205 | <div class="main"> | |
206 | ||
207 | <h3><em>Step 1.b</em> Get GnuPG by downloading GPGTools</h3> | |
208 | ||
209 | <p>GPGTools is a software package that includes GnuPG. <a | |
2f741db8 | 210 | href="https://gpgtools.org/#gpgsuite">Download</a> and |
5f3af91b TG |
211 | install it, choosing default options whenever asked. After it's installed, you can close |
212 | any windows that it creates.</p> | |
213 | ||
214 | </div><!-- End .main --> | |
215 | </div><!-- End #step1-b .step --> | |
216 | ||
217 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
218 | <div id="step-1c" class="step"> | |
219 | <div class="sidebar"> | |
220 | <ul class="images"> | |
221 | <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png" | |
222 | alt="Step 1.C: Tools -> Add-ons" /></li> | |
223 | <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png" | |
224 | alt="Step 1.C: Search Add-ons" /></li> | |
225 | <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png" | |
226 | alt="Step 1.C: Install Add-ons" /></li> | |
227 | </ul> | |
228 | ||
229 | </div><!-- /.sidebar --> | |
230 | <div class="main"> | |
231 | ||
232 | <h3><em>Step 1.c</em> Install the Enigmail plugin for your email program</h3> | |
233 | ||
234 | <p>In your email program's menu, select Add-ons (it may be in the Tools section). Make | |
235 | sure Extensions is selected on the left. Do you see Enigmail? if so, skip this step.</p> | |
236 | ||
237 | <p>If not, search "Enigmail" with the search bar in the upper right. You can take it from | |
238 | here. Restart your email program when you're done.</p> | |
239 | ||
240 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
241 | <div class="troubleshooting"> | |
242 | ||
243 | <h4>Troubleshooting</h4> | |
244 | ||
245 | <dl> | |
246 | <dt>I can't find the menu.</dt> | |
247 | ||
248 | <dd>In many new email programs, the main menu is represented by an image of three stacked | |
249 | horizontal bars.</dd> | |
250 | ||
251 | <dt class="feedback">Don't see a solution to your problem?</dt> | |
252 | ||
253 | <dd class="feedback">Please let us know on the <a | |
254 | href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd> | |
255 | </dl> | |
256 | ||
257 | </div><!-- /.troubleshooting --> | |
258 | </div><!-- End .main --> | |
259 | </div><!-- End #step-1c .step --> | |
260 | </div></section><!-- End #section1 --> | |
261 | ||
262 | <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ --> | |
263 | <section class="row" id="section2"><div> | |
264 | ||
265 | <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ --> | |
266 | <div class="section-intro"> | |
267 | ||
268 | <h2><em>#2</em> Make your keys</h2> | |
269 | ||
270 | <p>To use the GnuPG system, you'll need a public key and a private key (known together as a | |
271 | keypair). Each is a long string of randomly generated numbers and letters that are unique to | |
272 | you. Your public and private keys are linked together by a special mathematical function.</p> | |
273 | ||
274 | <p>Your public key isn't like a physical key, because it's stored in the open in an online | |
275 | directory called a keyserver. People download it and use it, along with GnuPG, to encrypt | |
276 | emails they send to you. You can think of the keyserver as phonebook, where people who | |
277 | want to send you an encrypted email look up your public key.</p> | |
278 | ||
279 | <p>Your private key is more like a physical key, because you keep it to yourself (on your | |
280 | computer). You use GnuPG and your private key to decode encrypted emails other people send | |
281 | to you.</p> | |
282 | ||
283 | </div><!-- End .section-intro --> | |
284 | ||
285 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
286 | <div id="step-2a" class="step"> | |
287 | <div class="sidebar"> | |
288 | ||
289 | <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" | |
290 | alt="Step 2.A: Make a Keypair" /></p> | |
291 | ||
292 | </div><!-- /.sidebar --> | |
293 | <div class="main"> | |
294 | ||
295 | <h3><em>Step 2.a</em> Make a keypair</h3> | |
296 | ||
297 | <span class="removed"><del><strong><p>In your email program's menu,</strong></del></span> | |
298 | ||
299 | <span class="inserted"><ins><em><p>The Enigmail Setup wizard may start automatically. If it doesn't,</em></ins></span> select <span class="removed"><del><strong>OpenPGP</strong></del></span> <span class="inserted"><ins><em>Enigmail</em></ins></span> → | |
300 | Setup <span class="removed"><del><strong>Wizard.</strong></del></span> <span class="inserted"><ins><em>Wizard from your email program's menu.</em></ins></span> You don't need to read the text in the window | |
301 | that pops up unless you'd like to, but it's good to read the text on the later screens of | |
302 | the <span class="removed"><del><strong>wizard.</p> | |
303 | ||
304 | <p>On</strong></del></span> <span class="inserted"><ins><em>wizard. Click Next with the default options selected, except in these instances:</p> | |
305 | ||
306 | <ul> | |
307 | <li>On</em></ins></span> the second screen, titled <span class="inserted"><ins><em>"Encryption," select "Encrypt all of my messages by default, | |
308 | because privacy is critical to me."</li> | |
309 | <li>On the third screen, titled</em></ins></span> "Signing," select <span class="removed"><del><strong>"No, I</strong></del></span> <span class="inserted"><ins><em>"Don't sign my messages by default."</li> | |
310 | <li>On the fourth screen, titled "Key Selection," select "I</em></ins></span> want to create <span class="removed"><del><strong>per-recipient | |
311 | rules</strong></del></span> <span class="inserted"><ins><em>a new key pair</em></ins></span> | |
312 | for <span class="removed"><del><strong>emails that need to be signed."</p> | |
313 | ||
314 | <p>Use the default options until you reach the screen titled "Create Key".</p> | |
315 | ||
316 | <p>On</strong></del></span> <span class="inserted"><ins><em>signing and encryption my email."</li> | |
317 | <li>On</em></ins></span> the screen titled "Create Key," pick a strong password! Your password should be at | |
318 | least 12 characters and include at least one lower case and upper case letter and at least one | |
319 | number or punctuation symbol. Don't forget the password, or all this work will be <span class="removed"><del><strong>wasted!</p></strong></del></span> <span class="inserted"><ins><em>wasted!</li> | |
320 | </ul></em></ins></span> | |
321 | ||
322 | <p class="notes">The program will take a little while to finish the next step, the "Key | |
323 | Creation" screen. While you wait, do something else with your computer, like watching a | |
324 | movie or browsing the Web. The more you use the computer at this point, the faster the | |
325 | key creation will go.</p> | |
326 | ||
327 | <p>When the <span class="removed"><del><strong>OpenPGP Confirm</strong></del></span> <span class="inserted"><ins><em>"Key Generation Completed"</em></ins></span> screen pops up, select Generate Certificate and | |
328 | choose to save it in a safe place on your computer (we recommend making a folder called | |
329 | "Revocation Certificate" in your home folder and keeping it there). You'll learn more | |
330 | about the revocation certificate in <a href="#section5">Section <span class="removed"><del><strong>5</a>. The setup wizard will ask | |
331 | you to move it onto an external device, but that isn't necessary at this moment.</p></strong></del></span> <span class="inserted"><ins><em>5</a>.</p></em></ins></span> | |
332 | ||
333 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
334 | <div class="troubleshooting"> | |
335 | ||
336 | <h4>Troubleshooting</h4> | |
337 | ||
338 | <dl> | |
339 | <dt>I can't find the <span class="removed"><del><strong>OpenPGP</strong></del></span> <span class="inserted"><ins><em>Enigmail</em></ins></span> menu.</dt> | |
340 | ||
341 | <dd>In many new email programs, the main menu is represented by an image of three stacked | |
342 | horizontal bars. <span class="removed"><del><strong>OpenPGP</strong></del></span> <span class="inserted"><ins><em>Enigmail</em></ins></span> may be inside a section called Tools.</dd> | |
343 | ||
344 | <dt class="feedback">Don't see a solution to your problem?</dt> | |
345 | ||
346 | <dd class="feedback">Please let us know on the <a | |
347 | href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd> | |
348 | </dl> | |
349 | ||
350 | </div><!-- /.troubleshooting --> | |
351 | </div><!-- End .main --> | |
352 | </div><!-- End #step-2a .step --> | |
353 | ||
354 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
355 | <div id="step-2b" class="step"> | |
356 | <div class="main"> | |
357 | ||
358 | <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3> | |
359 | ||
360 | <p>In your email program's menu, select <span class="removed"><del><strong>OpenPGP</strong></del></span> <span class="inserted"><ins><em>Enigmail</em></ins></span> → Key Management.</p> | |
361 | ||
362 | <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default | |
363 | keyserver in the popup.</p> | |
364 | ||
365 | <p class="notes">Now someone who wants to send you an encrypted message can download your | |
366 | public key from the Internet. There are multiple keyservers that you can select from the | |
367 | menu when you upload, but they are all copies of each other, so it doesn't matter which | |
368 | one you use. However, it sometimes takes a few hours for them to match each other when a | |
369 | new key is uploaded.</p> | |
370 | ||
371 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
372 | <div class="troubleshooting"> | |
373 | ||
374 | <h4>Troubleshooting</h4> | |
375 | ||
376 | <dl> | |
377 | <dt>The progress bar never <span class="removed"><del><strong>finishes.hes</dt></strong></del></span> <span class="inserted"><ins><em>finishes.</dt></em></ins></span> | |
378 | ||
379 | <dd>Close the upload popup, make sure you are connected to the Internet, and try again. If | |
380 | that doesn't work, try again, selecting a different keyserver.</dd> | |
381 | ||
382 | <dt>My key doesnt appear in the list</dt> | |
383 | ||
384 | <dd>Try checking <span class="removed"><del><strong>Show Default Keys.</dd></strong></del></span> <span class="inserted"><ins><em>"Display All Keys by Default."</dd></em></ins></span> | |
385 | ||
386 | <dt class="feedback">Don't see a solution to your problem?</dt> | |
387 | ||
388 | <dd class="feedback">Please let us know on the <a | |
389 | href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd> | |
390 | </dl> | |
391 | ||
392 | </div><!-- /.troubleshooting --> | |
393 | </div><!-- End .main --> | |
394 | </div><!-- End #step-2b .step --> | |
395 | ||
396 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
397 | <div id="terminology" class="step"> | |
398 | <div class="main"> | |
399 | ||
400 | <h3>GnuPG, OpenPGP, what?</h3> | |
401 | ||
402 | <span class="removed"><del><strong><p>You're using a program called GnuPG, but the menu in your email program is called | |
403 | OpenPGP. Confusing, right? In</strong></del></span> | |
404 | ||
405 | <span class="inserted"><ins><em><p>In</em></ins></span> general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used <span class="removed"><del><strong>interchangeably, though they all have slightly different meanings.</p></strong></del></span> | |
406 | <span class="inserted"><ins><em>interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the encryption standard, | |
407 | and GNU Privacy Guard (often shortened to GPG or GnuPG) is the program that implements the | |
408 | standard. Enigmail is a plug-in program for your email program that provides an interface | |
409 | for GnuPG.</p></em></ins></span> | |
410 | ||
411 | </div><!-- End .main --> | |
412 | </div><!-- End #terminology.step--> | |
413 | </div></section><!-- End #section2 --> | |
414 | ||
415 | <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ --> | |
416 | <section class="row" id="section3"><div> | |
417 | ||
418 | <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ --> | |
419 | <div class="section-intro"> | |
420 | ||
421 | <h2><em>#3</em> Try it out!</h2> | |
422 | ||
423 | <p>Now you'll try a test correspondence with a computer program named Edward, which knows | |
424 | how to use encryption. Except where noted, these are the same steps you'd follow when | |
425 | corresponding with a real, live person.</p> | |
426 | ||
427 | </div><!-- End .section-intro --> | |
428 | ||
429 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
430 | <div id="step-3a" class="step"> | |
431 | <div class="sidebar"> | |
432 | ||
433 | <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png" | |
434 | alt="Try it out." /></p> | |
435 | ||
436 | </div><!-- /.sidebar --> | |
437 | <div class="main"> | |
438 | ||
439 | <h3><em>Step 3.a</em> Send Edward your public key</h3> | |
440 | ||
441 | <p>This is a special step that you won't have to do when corresponding with real people. In | |
442 | your email program's menu, go to <span class="removed"><del><strong>OpenPGP</strong></del></span> <span class="inserted"><ins><em>Enigmail</em></ins></span> → Key Management. You should see your key in | |
443 | the list that pops up. Right click on your key and select Send Public Keys by Email. This | |
444 | will create a new draft message, as if you had just hit the Write button.</p> | |
445 | ||
446 | <p>Address the message to edward-en@fsf.org. Put at least one word (whatever you want) | |
447 | in the subject and body of the <span class="removed"><del><strong>email, then</strong></del></span> <span class="inserted"><ins><em>email. Then</em></ins></span> hit send.</p> | |
448 | ||
449 | <span class="inserted"><ins><em><p>There should be an icon of a yellow key in the bottom right of the composition | |
450 | window. This means that encryption is on, however, we want this first special message to | |
451 | Edward to be unencrypted. Click the key icon once to turn encryption off. The key should | |
452 | become grey, with a blue dot on it (to alert you that the setting has been changed from | |
453 | the default). Once encryption is off, hit Send.</p></em></ins></span> | |
454 | ||
455 | <p class="notes">It may take two or three minutes for Edward to respond. In the meantime, | |
456 | you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section | |
457 | of this guide. Once he's responded, head to the next step. From here on, you'll be doing | |
458 | just the same thing as when corresponding with a real person.</p> | |
459 | ||
460 | <span class="inserted"><ins><em><p>When you open Edward's reply, Enigmail may prompt you for your password before using | |
461 | your private key to decrypt it.</p></em></ins></span> | |
462 | ||
463 | </div><!-- End .main --> | |
464 | </div><!-- End #step-3a .step --> | |
465 | ||
466 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
467 | <div id="step-3b" class="step"> | |
468 | <div class="main"> | |
469 | ||
470 | <h3><em>Step 3.b</em> Send a test encrypted email</h3> | |
471 | ||
472 | <p>Write a new email in your email program, addressed to edward-en@fsf.org. Make the subject | |
473 | "Encryption test" or something similar and write something in the <span class="removed"><del><strong>body. Don't send it yet.</p> | |
474 | ||
475 | <p>Click the icon of the</strong></del></span> <span class="inserted"><ins><em>body.</p> | |
476 | ||
477 | <p>They</em></ins></span> key in the bottom right of the <span class="removed"><del><strong>composition</strong></del></span> window <span class="removed"><del><strong>(it</strong></del></span> should <span class="removed"><del><strong>turn | |
478 | yellow).</strong></del></span> <span class="inserted"><ins><em>be yellow, meaning encryption is | |
479 | on.</em></ins></span> This <span class="removed"><del><strong>tells Enigmail to encrypt the email.</p></strong></del></span> <span class="inserted"><ins><em>will be your default from now on.</p></em></ins></span> | |
480 | ||
481 | <p class="notes">Next to the key, you'll notice an icon of a pencil. Clicking this tells | |
482 | Enigmail to add a special, unique signature to your message, generated using your private | |
483 | key. This is a separate feature from encryption, and you don't have to use it for this | |
484 | guide.</p> | |
485 | ||
486 | <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted | |
487 | or not found."</p> | |
488 | ||
489 | <p>To encrypt an email to Edward, you need his public key, so now you'll have Enigmail | |
490 | download it from a keyserver. Click Download Missing Keys and use the default in the | |
491 | pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key | |
492 | ID starting with C), then select ok. Select ok in the next pop-up.</p> | |
493 | ||
494 | <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. <span class="removed"><del><strong>Select</strong></del></span> <span class="inserted"><ins><em>Check | |
495 | the box in front of</em></ins></span> Edward's key <span class="removed"><del><strong>from the list</strong></del></span> and click <span class="removed"><del><strong>Ok. If</strong></del></span> <span class="inserted"><ins><em>Send.</p> | |
496 | ||
497 | <p class="notes">Since you encrypted this email with Edward's public key, Edward's private | |
498 | key is required to decrypt it. Edward is</em></ins></span> the <span class="removed"><del><strong>message doesn't send automatically,</strong></del></span> <span class="inserted"><ins><em>only one with his private key, so no one | |
499 | except him — not even</em></ins></span> you <span class="inserted"><ins><em>—</em></ins></span> can <span class="removed"><del><strong>hit send now.</p></strong></del></span> <span class="inserted"><ins><em>decrypt it.</p></em></ins></span> | |
500 | ||
501 | <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ --> | |
502 | <div class="troubleshooting"> | |
503 | ||
504 | <h4>Troubleshooting</h4> | |
505 | ||
506 | <dl> | |
507 | <dt>Enigmail can't find Edward's key</dt> | |
508 | ||
509 | <dd>Close the pop-ups that have appeared since you <span class="removed"><del><strong>clicked.</strong></del></span> <span class="inserted"><ins><em>clicked Send.</em></ins></span> Make sure you are connected | |
510 | to the Internet and try again. If that doesn't work, repeat the process, choosing a | |
511 | different keyserver when it asks you to pick one.</dd> | |
512 | ||
513 | <dt class="feedback">Don't see a solution to your problem?</dt> | |
514 | ||
515 | <dd class="feedback">Please let us know on the <a | |
516 | href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd> | |
517 | </dl> | |
518 | ||
519 | </div><!-- /.troubleshooting --> | |
520 | </div><!-- End .main --> | |
521 | </div><!-- End #step-3b .step --> | |
522 | ||
523 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
524 | <div id="step-headers_unencrypted" class="step"> | |
525 | <div class="main"> | |
526 | ||
527 | <h3><em>Important:</em> Security tips</h3> | |
528 | ||
529 | <p>Even if you encrypted your email, the subject line is not encrypted, so don't put | |
530 | private information there. The sending and receiving addresses aren't encrypted either, | |
531 | so they could be read by a surveillance system. When you send attachments, Enigmail will | |
532 | give you an option of whether you want to encrypt them.</p> | |
533 | ||
534 | <span class="removed"><del><strong><p>It's also good practice to click the key icon in your email composition window | |
535 | <strong>before</strong> you start to write. Otherwise, your email client could save an | |
536 | unencrypted draft on the mail server, potentially exposing it to snooping.</p></strong></del></span> | |
537 | ||
538 | </div><!-- End .main --> | |
539 | </div><!-- End #step-headers_unencrypted .step--> | |
540 | ||
541 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
542 | <div id="step-3c" class="step"> | |
543 | <div class="main"> | |
544 | ||
545 | <h3><em>Step 3.c</em> Receive a response</h3> | |
546 | ||
547 | <p>When Edward receives your email, he will use his private key to decrypt it, then <span class="removed"><del><strong>fetch</strong></del></span> <span class="inserted"><ins><em>use</em></ins></span> | |
548 | your public key <span class="removed"><del><strong>from a keyserver and use it</strong></del></span> <span class="inserted"><ins><em>(which you sent him in <a href="#step-3a">Step 3.A</a>)</em></ins></span> to encrypt <span class="removed"><del><strong>a response</strong></del></span> <span class="inserted"><ins><em>his | |
549 | reply</em></ins></span> to you.</p> | |
550 | ||
551 | <p <span class="removed"><del><strong>class="notes">Since you encrypted this email with Edward's public key, Edward's private | |
552 | key is required to decrypt it. Edward is the only one with his private key, so no one | |
553 | except him — not even you — can decrypt it.</p> | |
554 | ||
555 | <p</strong></del></span> class="notes">It may take two or three minutes for Edward to respond. In the meantime, | |
556 | you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section | |
557 | of this guide.</p> | |
558 | ||
559 | <p>When you receive Edward's email and open it, Enigmail will automatically detect that | |
560 | it is encrypted with your public key, and then it will use your private key to decrypt it.</p> | |
561 | ||
562 | <p>Notice the bar that Enigmail shows you above the message, with information about the | |
563 | status of Edward's key.</p> | |
564 | ||
565 | </div><!-- End .main --> | |
566 | </div><!-- End #step-3c .step --> | |
567 | ||
568 | <!-- STEP 3D IS COMMENTED OUT UNTIL WE FIND A WAY TO VALIDATE SIGNATURES <div id="step-3d" | |
569 | class="step"> | |
570 | <div class="main"> | |
571 | ||
572 | <h3><em>Step 3.d</em> Send a test signed email to a friend</h3> | |
573 | ||
574 | <p>Write a new email in your email program, addressed to a friend. If you want, tell them | |
575 | about this guide!</p> | |
576 | ||
577 | <p>Before sending the email, click the icon of the pencil in the bottom right of the | |
578 | composition window (it should turn yellow). This tells Enigmail to sign the email with | |
579 | you private key.</p> | |
580 | ||
581 | <p>After you click send, Enigmail will ask you for your password. It will do this any time | |
582 | it needs to use your public key.</p> | |
583 | ||
584 | </div> | |
585 | </div>--> | |
586 | </div></section><!-- End #section3 --> | |
587 | ||
588 | <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ --> | |
589 | <section class="row" id="section4"><div> | |
590 | ||
591 | <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ --> | |
592 | <div class="section-intro"> | |
593 | ||
594 | <h2><em>#4</em> Learn the Web of Trust</h2> | |
595 | ||
596 | <p>Email encryption is a powerful technology, but it has a weakness; it requires a way to | |
597 | verify that a person's public key is actually theirs. Otherwise, there would be no way to | |
598 | stop an attacker from making an email address with your friend's name, creating keys to | |
599 | go with it and impersonating your friend. That's why the free software programmers that | |
600 | developed email encryption created keysigning and the Web of Trust.</p> | |
601 | ||
602 | <p>When you sign someone's key, you are publicly saying that you trust that it does belong | |
603 | to them and not an impostor. People who use your public key can see the number of signatures | |
604 | it has. Once you've used GnuPG for a long time, you may have hundreds of signatures. The | |
605 | Web of Trust is the constellation of all GnuPG users, connected to each other by chains of | |
606 | trust expressed through signatures, forming a giant network. The more signatures a key has, | |
607 | and the more signatures its signers' keys have, the more trustworthy that key is.</p> | |
608 | ||
609 | <p>People's public keys are usually identified by their key fingerprint, which is a string | |
610 | of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Edward's key). You can see the | |
611 | fingerprint for your public key, and other public keys saved on your computer, by going to <span class="removed"><del><strong>OpenPGP</strong></del></span> | |
612 | <span class="inserted"><ins><em>Enigmail</em></ins></span> → Key Management in your email program's menu, then right clicking on the | |
613 | key and choosing Key Properties. It's good practice to share your fingerprint wherever | |
614 | you share your email address, so that people can double-check that they have the correct | |
615 | public key when they download yours from a keyserver.</p> | |
616 | ||
617 | <p class="notes">You may also see public keys referred to by their key ID, which is simply | |
618 | the last 8 digits of the fingerprint, like C09A61E8 for Edward. The key ID is visible | |
619 | directly from the Key Management <span class="removed"><del><strong>Window.</strong></del></span> <span class="inserted"><ins><em>window.</em></ins></span> This key ID is like a person's first name (it is | |
620 | a useful shorthand but may not be unique to a given key), whereas the fingerprint actually | |
621 | identifies the key uniquely without the possibility of confusion. If you only have the key | |
622 | ID, you can still look up the key (as well as its fingerprint), like you did in Step 3, | |
623 | but if multiple options appear, you'll need the fingerprint of the person to whom are | |
624 | trying to communicate to verify which one to use.</p> | |
625 | ||
626 | </div><!-- End .section-intro --> | |
627 | ||
628 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
629 | <div id="step-4a" class="step"> | |
630 | <div class="sidebar"> | |
631 | ||
632 | <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" | |
633 | alt="Section 4: Web of Trust" /></p> | |
634 | ||
635 | </div><!-- /.sidebar --> | |
636 | <div class="main"> | |
637 | ||
638 | <h3><em>Step 4.a</em> Sign a key</h3> | |
639 | ||
640 | <p>In your email program's menu, go to <span class="removed"><del><strong>OpenPGP</strong></del></span> <span class="inserted"><ins><em>Enigmail</em></ins></span> → Key Management.</p> | |
641 | ||
642 | <p>Right click on Edward's public key and select Sign Key from the context menu.</p> | |
643 | ||
644 | <p>In the window that pops up, select "I will not answer" and click ok.</p> | |
645 | ||
646 | <span class="removed"><del><strong><p>In your email program's menu, go to OpenPGP →</strong></del></span> | |
647 | ||
648 | <span class="inserted"><ins><em><p>Now you should be back at the</em></ins></span> Key Management <span class="removed"><del><strong>→</strong></del></span> <span class="inserted"><ins><em>menu. Select</em></ins></span> Keyserver → Upload Public | |
649 | Keys and hit ok.</p> | |
650 | ||
651 | <p class="notes">You've just effectively said "I trust that Edward's public key actually | |
652 | belongs to Edward." This doesn't mean much because Edward isn't a real person, but it's | |
653 | good practice.</p> | |
654 | ||
655 | <!--<div id="pgp-pathfinder"> | |
656 | ||
657 | <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get"> | |
658 | ||
659 | <p><strong>From:</strong> | |
660 | <input type="text" placeholder="xD41A008" name="FROM"></p> | |
661 | ||
662 | <p><strong>To:</strong> | |
663 | <input type="text" placeholder="50BD01x4" name="TO"></p> | |
664 | ||
665 | <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> | |
666 | <input type="reset" value="reset" name=".reset"></p> | |
667 | ||
668 | </form> | |
669 | ||
670 | </div><!-- End #pgp-pathfinder --> | |
671 | </div><!-- End .main --> | |
672 | </div><!-- End #step-4a .step --> | |
673 | ||
674 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
675 | <div id="step-sign_real_keys" class="step"> | |
676 | <div class="main"> | |
677 | ||
678 | <h3><em>Important:</em> check people's identification before signing their keys</h3> | |
679 | ||
680 | <p>Before signing a real person's key, always make sure it actually belongs to them, and | |
681 | that they are who they say they are. Ask them to show you their ID (unless you trust them | |
682 | very highly) and their public key fingerprint -- not just the shorter public key ID, which | |
683 | could refer to another key as well. In Enigmail, answer honestly in the window that pops | |
684 | up and asks "How carefully have you verified that the key you are about to sign actually | |
685 | belongs to the person(s) named above?".</p> | |
686 | ||
687 | </div><!-- End .main --> | |
688 | </div><!-- End #step-sign_real_keys .step--> | |
689 | </div></section><!-- End #section4 --> | |
690 | ||
691 | <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ --> | |
692 | <section id="section5" class="row"><div> | |
693 | ||
694 | <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ --> | |
695 | <div class="section-intro"> | |
696 | ||
697 | <h2><em>#5</em> Use it well</h2> | |
698 | ||
699 | <p>Everyone uses GnuPG a little differently, but it's important to follow some basic | |
700 | practices to keep your email secure. Not following them, you risk the privacy of the people | |
701 | you communicate with, as well as your own, and damage the Web of Trust.</p> | |
702 | ||
703 | </div><!-- End .section-intro --> | |
704 | ||
705 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
706 | <div id="step-5a" class="step"> | |
707 | <div class="sidebar"> | |
708 | ||
709 | <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png" | |
710 | alt="Section 5: Use it Well" /></p> | |
711 | ||
712 | </div><!-- /.sidebar --> | |
713 | <div class="main"> | |
714 | ||
715 | <h3>When should I encrypt?</h3> | |
716 | ||
717 | <p>The more you can encrypt your messages, the better. If you only encrypt emails | |
718 | occasionally, each encrypted message could raise a red flag for surveillance systems. If all | |
719 | or most of your email is encrypted, people doing surveillance won't know where to start.</p> | |
720 | ||
721 | <p>That's not to say that only encrypting some of your email isn't helpful -- it's a great | |
722 | start and it makes bulk surveillance more difficult.</p> | |
723 | ||
724 | </div><!-- End .main --> | |
725 | </div><!-- End #step-5a .step --> | |
726 | ||
727 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
728 | <div id="step-5b" class="step"> | |
729 | <div class="sidebar"> | |
730 | ||
731 | <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png" | |
732 | alt="Section 5: Use it Well" /></p> | |
733 | ||
734 | </div><!-- /.sidebar --> | |
735 | <div class="main"> | |
736 | ||
737 | <h3><em>Important:</em> Be wary of invalid keys</h3> | |
738 | ||
739 | <p>GnuPG makes email safer, but it's still important to watch out for invalid keys, which | |
740 | might have fallen into the wrong hands. Email encrypted with invalid keys might be readable | |
741 | by surveillance programs.</p> | |
742 | ||
743 | <p>In your email program, go back to the second email that Edward sent you. Because Edward | |
744 | encrypted it with your public key, it will have a message from <span class="removed"><del><strong>OpenPGP</strong></del></span> <span class="inserted"><ins><em>Enigmail</em></ins></span> at the top, which | |
745 | most likely says <span class="removed"><del><strong>"OpenPGP:</strong></del></span> <span class="inserted"><ins><em>"Enigmail:</em></ins></span> Part of this message encrypted."</p> | |
746 | ||
747 | <p><b>When using GnuPG, make a habit of glancing at that bar. The program will warn you | |
748 | there if you get an email encrypted with a key that can't be trusted.</b></p> | |
749 | ||
750 | </div><!-- End .main --> | |
751 | </div><!-- End #step-5b .step --> | |
752 | ||
753 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
754 | <div id="step-5c" class="step"> | |
755 | <div class="main"> | |
756 | ||
757 | <h3>Copy your revocation certificate to somewhere safe</h3> | |
758 | ||
759 | <p>Remember when you created your keys and saved the revocation certificate that GnuPG | |
760 | made? It's time to copy that certificate onto the safest digital storage that you have -- | |
761 | the ideal thing is a flash drive, disk, or hard drive stored in a safe place in your home.</p> | |
762 | ||
763 | <p>If your private key ever gets lost or stolen, you'll need this certificate file to let | |
764 | people know that you are no longer using that keypair.</p> | |
765 | ||
766 | </div><!-- End .main --> | |
767 | </div><!-- End #step-5c .step --> | |
768 | ||
769 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ --> | |
770 | <div id="step-lost_key" class="step"> | |
771 | <div class="main"> | |
772 | ||
773 | <h3><em>Important:</em> act swiftly if someone gets your private key</h3> | |
774 | ||
775 | <p>If you lose your private key or someone else gets ahold of it (say, by stealing or | |
776 | cracking your computer), it's important to revoke it immediately before someone else uses | |
777 | it to read your encrypted email. This guide doesn't cover how to revoke a key, but you | |
778 | can follow the <a href="https://www.gnupg.org/gph/en/manual.html#AEN305">instructions on | |
779 | the GnuPG site</a>. After you're done revoking, send an email to everyone with whom you | |
780 | usually use your key to make sure they know.</p> | |
781 | ||
782 | </div><!-- End .main --> | |
783 | </div><!-- End #step-lost_key .step--> | |
784 | ||
785 | <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ | |
786 | <div id="step-5d" class="step"> | |
787 | <div class="main"> | |
788 | ||
789 | <h3>Make your public key part of your online identity</h3> | |
790 | ||
791 | <p> First add your public key fingerprint to your email signature, then compose an email | |
792 | to at least five of your friends, telling them you just set up GnuPG and mentioning your | |
793 | public key fingerprint. Link to this guide and ask them to join you. Don't forget that | |
794 | there's also an awesome <a href="infographic.html">infographic to share.</a></p> | |
795 | ||
796 | <p class="notes">Start writing your public key fingerprint anywhere someone would see | |
797 | your email address: your social media profiles, blog, Website, or business card. (At the | |
798 | Free Software Foundation, we put ours on our <a href="https://fsf.org/about/staff">staff | |
799 | page</a>.) We need to get our culture to the point that we feel like something is missing | |
800 | when we see an email address without a public key fingerprint.</p> | |
801 | ||
802 | </div><!-- End .main <span class="removed"><del><strong></div><!--</strong></del></span> <span class="inserted"><ins><em></div></em></ins></span> End #step-5d .step--> | |
803 | </div></section><!-- End #section5 --> | |
804 | ||
805 | <!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ --> | |
806 | <section class="row" id="section6"> | |
807 | <div id="step-click_here" class="step"> | |
808 | <div class="main"> | |
809 | ||
810 | <h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2> | |
811 | ||
812 | </div><!-- End .main --> | |
813 | </div><!-- End #step-click_here .step--> | |
814 | </section><!-- End #section6 --> | |
815 | ||
816 | <!-- ~~~~~~~~~ FAQ ~~~~~~~~~ --> | |
817 | <!-- When un-commenting this section go to main.css and search for /* Guide Sections | |
818 | Background */ then add #faq to the desired color | |
819 | <section class="row" id="faq"><div> | |
820 | <div class="sidebar"> | |
821 | ||
822 | <h2>FAQ</h2> | |
823 | ||
824 | </div> | |
825 | <div class="main"> | |
826 | ||
827 | <dl> | |
828 | <dt>My key expired</dt> | |
829 | ||
830 | <dd>Answer coming soon.</dd> | |
831 | ||
832 | <dt>Who can read encrypted messages? Who can read signed ones?</dt> | |
833 | ||
834 | <dd>Answer coming soon.</dd> | |
835 | ||
836 | <dt>My email program is opening at times I don't want it to open/is now my default program | |
837 | and I don't want it to be.</dt> | |
838 | ||
839 | <dd>Answer coming soon.</dd> | |
840 | </dl> | |
841 | ||
842 | </div> | |
843 | </div> | |
844 | </section> --><!-- End #faq --> | |
845 | ||
846 | <!-- ~~~~~~~~~ Footer ~~~~~~~~~ --> | |
847 | <footer class="row" id="footer"><div> | |
848 | <div id="copyright"> | |
849 | ||
850 | <h4><a href="https://u.fsf.org/ys"><img | |
851 | alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" | |
852 | /></a></h4> | |
853 | ||
854 | <p>Copyright © 2014 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, | |
855 | Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. <a | |
856 | href="https://u.fsf.org/yr">Join.</a></p> | |
857 | ||
858 | <p><em>Version <span class="removed"><del><strong>2.1.</strong></del></span> <span class="inserted"><ins><em>3.0.</em></ins></span> <a | |
859 | href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">Source | |
860 | code of Edward reply bot by Josh Drake <zamnedix@gnu.org> available under the GNU | |
861 | General Public License.</a></em></p> | |
862 | ||
863 | <p>The images on this page are under a <a | |
864 | href="https://creativecommons.org/licenses/by/4.0/">Creative Commons | |
865 | Attribution 4.0 license (or later version)</a>, and the rest of it is under | |
866 | a <a href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons | |
867 | Attribution-ShareAlike 4.0 license (or later version)</a>. — <a | |
868 | href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p> | |
869 | ||
870 | <p>Download the source package for <a href="emailselfdefense_source.zip">this | |
871 | guide</a>. Fonts used in the guide & infographic: <a | |
872 | href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo Impallari, <a | |
873 | href="http://www.google.com/fonts/specimen/Signika">Signika</a> by Anna Giedryś, <a | |
874 | href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, | |
875 | <a href="http://www.thegopherarchive.com/gopher-files-hacks-pxl2000-119351.htm">PXL-2000</a> | |
876 | by Florian Cramer.</p> | |
877 | ||
878 | <p> <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" rel="jslicense"> JavaScript | |
879 | license information </a> </p> | |
880 | ||
881 | </div><!-- /#copyright --> | |
882 | ||
883 | <p class="credits"> Infographic and guide design by <a rel="external" | |
884 | href="http://jplusplus.org"><strong>Journalism++</strong> <img | |
885 | src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" | |
886 | alt="Journalism++" /></a> </p><!-- /.credits --> | |
887 | ||
888 | </div></footer><!-- End #footer --> | |
889 | </pre></body></html> |