projects / enc.git / blame
? search:
summary | shortlog | log | commit | commitdiff | tree
blob | blame (incremental) | history | HEAD
en: reformat.
[enc.git] / ml / windows.html
CommitLineData
ab8f60eb 1<!DOCTYPE html>
c35c9b77 2<html lang="ml">
ab8f60eb 3 <head>
668de811 4 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
ab8f60eb
DT		 5
6 <title>Email Self-Defense - a guide to fighting surveillance with GnuPG encryption</title>
7 <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail" />
9363be98 8 <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." />
ab8f60eb 9
9363be98
TG		 10 <meta name="viewport" content="width=device-width, initial-scale=1" />
11 <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />
ab8f60eb
DT		 12 <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
13
14 </head>
15 <body>
ab8f60eb
DT		 16
17<!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
18<!-- ~~~~~~~~~ Revision as of 18:53, 1 June 2014 by Zakkai ~~~~~~~~~ -->
19 <header class="row" id="header">
20
21 <!--<div class="highlight" style="background: red;">
22 <h3 style="text-align: center;"><strong style="color: white;">Website Under Construction</strong></h3>
23 </div>-->
24
25 <div>
0c168c2e 26 <h1>Email Self-Defense</h1>
9363be98
TG		 27
28 <!-- Language list for browsers that do not have JS enabled -->
29 <ul id="languages" class="os">
30<li><a href="/en">English - v4.0</a></li>
9363be98
TG		 31<li><a href="/cs">Čeština - v4.0</a></li>
32<li><a href="/de">Deutsch - v3.0</a></li>
33<li><a href="/el">ελληνικά - v3.0</a></li>
34<li><a href="/es">español - v4.0</a></li>
35<li><a href="/fa">فارسی - v4.0</a></li>
36<li><a href="/fr">français - v4.0</a></li>
37<li><a href="/it">italiano - v3.0</a></li>
38<li><a href="/ja">日本語 - v4.0</a></li>
9363be98
TG		 39<li><a href="/pt-br">português do Brasil - v3.0</a></li>
40<li><a href="/ro">română - v3.0</a></li>
41<li><a href="/ru">русский - v4.0</a></li>
42<li><a href="/sq">Shqip - v4.0</a></li>
43<li><a href="/sv">svenska - v4.0</a></li>
44<li><a href="/tr">Türkçe - v4.0</a></li>
45<li><a href="/zh-hans">简体中文 - v4.0</a></li>
275d311e 46<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide"><strong><span style="color: #2F5FAA;">Translate!</span></strong></a></li>
9363be98
TG		 47</ul>
48
0c168c2e
DT		 49 <ul class="os">
50 <li><a href="index.html">GNU/Linux</a></li>
51 <li><a href="mac.html">Mac OS</a></li>
52 <li><a href="windows.html" class="current">Windows</a></li>
53 <li class="spacer">
54 <a href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email encryption for everyone via %40fsf">
55 Share&nbsp;
56 <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"
9363be98 57 class="share-logo" alt="[GNU Social]" />&nbsp;
0c168c2e 58 <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"
9363be98 59 class="share-logo" alt="[Pump.io]" />&nbsp;
0c168c2e 60 <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"
9363be98 61 class="share-logo" alt="[Reddit]" />&nbsp;
0c168c2e 62 <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png"
9363be98 63 class="share-logo" alt="[Hacker News]" />
0c168c2e
DT		 64 </a>
65 </li>
66 </ul>
ab8f60eb
DT		 67
68 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
69 <div id="fsf-intro">
9363be98 70 <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>
ab8f60eb
DT		 71 <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>
72
9363be98 73 <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&amp;id=14&amp;pk_campaign=email_self_defense&amp;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>
ab8f60eb
DT		 74
75 </div><!-- End #fsf-intro -->
76
77 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
78 <div class="intro">
79 <p>
80 <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/infographic-button.png" alt="View &amp; share our infographic &rarr;" /></a>
81 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>
82
83<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>
84
85<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>
86
87 </div>
88 </div>
89 </header><!-- End #header -->
90
91<!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
92 <section class="row" id="section1">
93 <div>
94 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
95 <div class="section-intro">
96 <h2><em>#1</em> Get the pieces</h2>
97 <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>
98 <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>
99 <p>If you are already have one of these, you can skip to <a href="#step-1b">Step 1.b</a>.</p>
100 </div><!-- End .section-intro -->
101
102 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
103 <div id="step-1a" class="step">
104 <div class="sidebar">
105 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>
106 </div><!-- /.sidebar -->
107 <div class="main">
108 <h3><em>Step 1.a</em> Set your email program up with your email account (if it isn't already)</h3>
109 <p>Open your email program and follow the wizard that sets it up with your email account.</p>
110
111 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
112 <div class="troubleshooting">
113 <h4>Troubleshooting</h4>
114 <dl>
115 <dt>What's a wizard?</dt>
116 <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>
117 <dt>My email program can't find my account or isn't downloading my mail</dt>
118 <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>
119 <dt class="feedback">Don't see a solution to your problem?</dt>
120 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
121 </dl>
122 </div><!-- /.troubleshooting -->
123
124 </div><!-- End .main -->
125 </div><!-- End #step1-a .step -->
126
127<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
128 <div id="step-1b" class="step">
129
130 <div class="main">
131 <h3><em>Step 1.b</em> Get GnuPG by downloading GPG4Win</h3>
b57f5bf0 132 <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>
ab8f60eb
DT		 133
134 </div><!-- End .main -->
135 </div><!-- End #step1-b .step -->
136
137 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
138 <div id="step-1c" class="step">
139 <div class="sidebar">
140 <ul class="images">
9363be98
TG		 141 <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-01-tools-addons.png" alt="Step 1.C: Tools -> Add-ons" /></li>
142 <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-02-search.png" alt="Step 1.C: Search Add-ons" /></li>
143 <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-03-install.png" alt="Step 1.C: Install Add-ons" /></li>
ab8f60eb
DT		 144 </ul>
145 </div><!-- /.sidebar -->
146 <div class="main">
147 <h3><em>Step 1.c</em> Install the Enigmail plugin for your email program</h3>
148 <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>
149 <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>
150 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
151 <div class="troubleshooting">
152 <h4>Troubleshooting</h4>
153 <dl>
154 <dt>I can't find the menu.</dt>
155 <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars.</dd>
156
157 <dt class="feedback">Don't see a solution to your problem?</dt>
158 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
159 </dl>
160 </div><!-- /.troubleshooting -->
161 </div><!-- End .main -->
162 </div><!-- End #step-1c .step -->
163 </div>
164 </section><!-- End #section1 -->
165
166<!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
167 <section class="row" id="section2">
168 <div>
169 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
170 <div class="section-intro">
171 <h2><em>#2</em> Make your keys</h2>
172 <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>
173
174<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>
175
176<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>
177 </div><!-- End .section-intro -->
178
179 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
180 <div id="step-2a" class="step">
181 <div class="sidebar">
182 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>
183 </div><!-- /.sidebar -->
184 <div class="main">
185 <h3><em>Step 2.a</em> Make a keypair</h3>
186 <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>
187 <p>On the second screen, titled "Signing," select "No, I want to create per-recipient rules for emails that need to be signed."</p>
188 <p>Use the default options until you reach the screen titled "Create Key".</p>
189 <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>
190 <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>
191 <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>
192
193 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
194 <div class="troubleshooting">
195 <h4>Troubleshooting</h4>
196 <dl>
197 <dt>I can't find the OpenPGP menu.</dt>
198 <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>
199
200 <dt class="feedback">Don't see a solution to your problem?</dt>
201 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
202 </dl>
203 </div><!-- /.troubleshooting -->
204 </div><!-- End .main -->
205 </div><!-- End #step-2a .step -->
206 <div id="step-2b" class="step">
207 <div class="main">
208 <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
209 <p>In your email program's menu, select OpenPGP &rarr; Key Management.</p>
210<p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
211<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>
212 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
213 <div class="troubleshooting">
214 <h4>Troubleshooting</h4>
215 <dl>
216 <dt>The progress bar never finishes</dt>
217 <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>
218<dt>My key doesnt appear in the list</dt>
219 <dd>Try checking Show Default Keys.</dd>
220
221 <dt class="feedback">Don't see a solution to your problem?</dt>
222 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
223
224 </dl>
225 </div><!-- /.troubleshooting -->
226
227
228
229 </div><!-- End .main -->
230 </div><!-- End #step-2a .step -->
231 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
232 <div id="terminology" class="step">
233 <div class="main">
234 <h3>GnuPG, OpenPGP, what?</h3>
235 <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>
236 </div><!-- End .main -->
237 </div><!-- End #terminology.step-->
238 </div>
239 </section><!-- End #section2 -->
240
241<!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
242 <section class="row" id="section3">
243 <div>
244 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
245 <div class="section-intro">
246 <h2><em>#3</em> Try it out!</h2>
247 <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>
248 </div><!-- End .section-intro -->
249
250 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
251 <div id="step-3a" class="step">
252 <div class="sidebar">
253 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
254 </div><!-- /.sidebar -->
255 <div class="main">
256 <h3><em>Step 3.a</em> Send Adele your public key</h3>
257 <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>
258
259<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>
260
261<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>
262 </div><!-- End .main -->
263 </div><!-- End #step-3b .step -->
264
265 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
266 <div id="step-3b" class="step">
267 <div class="main">
268 <h3><em>Step 3.b</em> Send a test encrypted email</h3>
269 <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>
270 <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>
271 <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>
272<p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
273
357dc69d 274 <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>
ab8f60eb
DT		 275
276 <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>
277 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
278 <div class="troubleshooting">
279 <h4>Troubleshooting</h4>
280 <dl>
281 <dt>Enigmail can't find Adele's key</dt>
282 <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>
283 <dt class="feedback">Don't see a solution to your problem?</dt>
284 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
285 </dl>
286 </div><!-- /.troubleshooting -->
287 </div><!-- End .main -->
288 </div><!-- End #step-3b .step -->
289
290 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
291 <div id="step-headers_unencrypted" class="step">
292 <div class="main">
293 <h3><em>Important:</em> Security tips</h3>
294 <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>
295<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>
296 </div><!-- End .main -->
297 </div><!-- End #step-headers_unencrypted .step-->
298
299
300 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
301 <div id="step-3c" class="step">
302 <div class="main">
303 <h3><em>Step 3.c</em> Receive a response</h3>
304 <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>
305 <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>
306 <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>
307 <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>
308 <p>Notice the bar that Enigmail shows you above the message, with information about the status of Adele's key.</p>
309 </div><!-- End .main -->
310 </div><!-- End #step-3c .step -->
311
312<!-- STEP 3D IS COMMENTED OUT UNTIL WE FIND A WAY TO VALIDATE SIGNATURES
313 <div id="step-3d" class="step">
314 <div class="main">
315 <h3><em>Step 3.d</em> Send a test signed email to a friend</h3>
316 <p>Write a new email in your email program, addressed to a friend. If you want, tell them about this guide!</p>
317 <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>
318 <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>
319 </div>
320 </div>-->
321 </div>
322 </section><!-- End #section3 -->
323
324
325<!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
326 <section class="row" id="section4">
327 <div>
328 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
329 <div class="section-intro">
330 <h2><em>#4</em> Learn the Web of Trust</h2>
331 <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>
332
333<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>
334
2334cfdb 335<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 &rarr; 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>
ab8f60eb 336
2334cfdb 337<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>
ab8f60eb
DT		 338
339
340 </div><!-- End .section-intro -->
341
342 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
343 <div id="step-4a" class="step">
344 <div class="sidebar">
345 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
346 </div><!-- /.sidebar -->
347 <div class="main">
348 <h3><em>Step 4.a</em> Sign a key</h3>
349 <p>In your email program's menu, go to OpenPGP &rarr; Key Management.</p>
350 <p>Right click on Adele's public key and select Sign Key from the context menu.</p>
351 <p>In the window that pops up, select "I will not answer" and click OK.</p>
352 <p>In your email program's menu, go to OpenPGP &rarr; Key Management &rarr; Keyserver &rarr; Upload Public Keys and hit OK.</p>
353 <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>
354
355
356 <!--<div id="pgp-pathfinder">
357 <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
358 <p><strong>From:</strong> <input type="text" placeholder="xD41A008" name="FROM"></p>
359 <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
360 <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
361 </form>
9363be98 362 </div>--><!-- End #pgp-pathfinder -->
ab8f60eb
DT		 363
364 </div><!-- End .main -->
365 </div><!-- End #step-4a .step -->
366 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
367 <div id="step-sign_real_keys" class="step">
368 <div class="main">
369 <h3><em>Important:</em> check people's identification before signing their keys</h3>
370 <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>
371 </div><!-- End .main -->
372 </div><!-- End #step-sign_real_keys .step-->
373
374
375
376 </div>
377 </section><!-- End #section4 -->
378
379<!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
380 <section id="section5" class="row">
381 <div>
382 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
383 <div class="section-intro">
384 <h2><em>#5</em> Use it well</h2>
385<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>
386 </div><!-- End .section-intro -->
387
388 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
389 <div id="step-5a" class="step">
390 <div class="sidebar">
391 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well" /></p>
392 </div><!-- /.sidebar -->
393 <div class="main">
394 <h3>When should I encrypt?</h3>
395
396 <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>
397
398<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>
399
400 </div><!-- End .main -->
401 </div><!-- End #step-5a .step -->
402
403 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
404 <div id="step-5b" class="step">
405 <div class="sidebar">
406 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
407 </div><!-- /.sidebar -->
408 <div class="main">
409 <h3><em>Important:</em> Be wary of invalid keys</h3>
410 <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>
411 <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>
412<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>
413 </div><!-- End .main -->
414 </div><!-- End #step-5b .step -->
415
416 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
417 <div id="step-5c" class="step">
418 <div class="main">
419 <h3>Copy your revocation certificate to somewhere safe</h3>
420 <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>
421<p>If your private key ever gets lost or stolen, you'll need this certificate file.</p>
422 </div><!-- End .main -->
423 </div><!-- End #step-5c .step -->
424
425 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
426 <div id="step-lost_key" class="step">
427 <div class="main">
428 <h3><em>Important:</em> act swiftly if someone gets your private key</h3>
429 <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>
430 </div><!-- End .main -->
431 </div><!-- End #step-lost_key .step-->
432
433 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
434 <div id="step-5d" class="step">
435 <div class="main">
436 <h3>Make your public key part of your online identity</h3>
437 <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>
438
439<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>
9363be98
TG		 440 </div>--><!-- End .main
441 </div>--><!-- End #step-5d .step-->
ab8f60eb
DT		 442
443
444 </div>
445 </section><!-- End #section5 -->
446
447<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
448 <section class="row" id="section6">
449 <div id="step-click_here" class="step">
450 <div class="main">
451 <h2><a href="next_steps.html">Click here when you're done</a></h2>
452
453 </div><!-- End .main -->
454 </div><!-- End #step-click_here .step-->
455
456 </section><!-- End #section6 -->
457
458<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
459<!-- When un-commenting this section go to main.css and search
460 for /* Guide Sections Background */ then add #faq to the desired color
461
462 <section class="row" id="faq">
463 <div>
464 <div class="sidebar">
465 <h2>FAQ</h2>
466 </div>
467
468 <div class="main">
469 <dl>
470 <dt>My key expired</dt>
471 <dd>Answer coming soon.</dd>
472
473 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
474 <dd>Answer coming soon.</dd>
475
476 <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>
477 <dd>Answer coming soon.</dd>
478 </dl>
479 </div>
480 </div>
481 </section> --><!-- End #faq -->
482
483<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
484 <footer class="row" id="footer">
485 <div>
486 <div id="copyright">
9363be98 487 <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>
ab8f60eb
DT		 488 <p>Copyright &copy; 2014 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. <a href="https://u.fsf.org/yr">Join.</a></p>
489 <p><em>Version 2.0, launched 6/18/2014. <!--LANGUAGE translation by NAME, NAME and NAME.--></em></p>
490<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>. &mdash; <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
491 <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 &amp; 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&#347; <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>
492 <p>
493 <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
494 rel="jslicense">
495 JavaScript license information
496 </a>
497 </p>
498 </div><!-- /#copyright -->
499 <p class="credits">
500 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>
501 </p><!-- /.credits -->
502 </div>
503 </footer><!-- End #footer -->
504
505 <script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
506 <script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
507
508 <!-- Piwik -->
509 <script type="text/javascript">
510 /*
511 @licstart The following is the entire license notice for the
512 JavaScript code in this page.
513
514 Copyright 2014 Matthieu Aubry
515
516 This program is free software: you can redistribute it and/or modify
517 it under the terms of the GNU General Public License as published by
518 the Free Software Foundation, either version 3 of the License, or
519 (at your option) any later version.
520
521 This program is distributed in the hope that it will be useful,
522 but WITHOUT ANY WARRANTY; without even the implied warranty of
523 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
524 GNU General Public License for more details.
525
526 You should have received a copy of the GNU General Public License
527 along with this program. If not, see http://www.gnu.org/licenses/.
528
529 @licend The above is the entire license notice
530 for the JavaScript code in this page.
531 */
532 var _paq = _paq || [];
533 _paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
534 _paq.push(["setCookieDomain", "*.www.fsf.org"]);
535 _paq.push(["setDomains", ["*.www.fsf.org","*.www.fsf.org"]]);
536 _paq.push(["trackPageView"]);
537 _paq.push(["enableLinkTracking"]);
538
539 (function() {
540 var u=(("https:" == document.location.protocol) ? "https" : "http") + "://piwik.fsf.org/";
541 _paq.push(["setTrackerUrl", u+"piwik.php"]);
542 _paq.push(["setSiteId", "5"]);
543 var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
544 g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
545 })();
546 </script>
547 <!-- End Piwik Code -->
548 </body>
549</html>
Unnamed repository; edit this file 'description' to name the repository.