Translate Section 1.
[enc-live.git] / ko / index.html
1 <!DOCTYPE html>
2 <html>
3 <head>
4 <meta charset="utf-8">
5
6 <title>스스로 이메일 보호하기 - GnuPG 암호화를 이용한 감시 방어 가이드</title>
7 <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail" />
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.">
9
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">
12 <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
13
14 </head>
15 <body>
16
17 <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
18
19 <header class="row" id="header">
20 <div>
21 <h1>스스로 이메일 보호하기</h1>
22
23 <!-- Language list for browsers that do not have JS enabled -->
24 <ul id="languages" class="os">
25 <li><a class="current" href="/en">english</a></li>
26 <li><a href="/es">español</a></li>
27 <li><a href="/fr">français</a></li>
28 <li><a href="/de">deutsch</a></li>
29 <li><a href="/pt-br">português do Brasil</a></li>
30 <li><a href="/tr">türkçe</a></li>
31 <li><a href="/ro">română</a></li>
32 <li><a href="/ru">русский</a></li>
33 <li><a href="/ml">മലയാളം</a></li>
34 <li><a href="/ko">한국어</a></li>
35 <li><a href="/ja">日本語</a></li>
36 </ul>
37
38 <ul id="menu" class="os">
39 <li class="spacer">
40 <a href="index.html" class="current">GNU/리눅스</a>
41 </li>
42 <li>
43 <a href="mac.html">맥 OS</a>
44 </li>
45 <li>
46 <a href="windows.html">윈도우즈</a>
47 </li>
48 <li class="spacer">
49 <a href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email encryption for everyone via %40fsf">
50 #EmailSelfDefense
51 </a>
52 </li>
53 </ul>
54
55 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
56 <div id="fsf-intro">
57 <h3>
58 <a href="http://u.fsf.org/ys">
59 <img alt="Free Software Foundation"
60 src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png">
61 </a>
62 </h3>
63 <div class="fsf-emphasis">
64 <p>
65 자유 소프트웨어 재단은 컴퓨터 사용자들의 권리를 위해 싸우며, 자유 소프트웨어의 개발을 지원합니다. 정부 감시에 저항하는 것은 자유 소프트웨어 재단에 있어 매우 중요한 일입니다.
66 </p>
67 <p>
68 <strong>
69 자유 소프트웨어 재단은 많은 사람들이 자신의 개인정보를 보호하기 위해 첫 발을 떼는 것을 돕기 위해 이러한 일대일 혹은 온라인 도구를 지원하고자 합니다. 약간의 기부 혹은 회원이 되는 것으로써 저희를 도와 주시겠습니까?
70 </strong>
71 </p>
72 </div>
73
74 <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=esd&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>
75
76 </div><!-- End #fsf-intro -->
77
78 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
79 <div class="intro">
80 <p>
81 <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>
82 대량 감시는 우리의 근본적인 권리를 침해하며 자유로운 발언을 할 권리를 위협합니다. 이 가이드는 간단한 감시로부터의 자가 보호 기술인 이메일 암호화를 안내할 것입니다. 이 가이드를 끝내면 당신은 암호화된 이메일을 통해 정보기관과 당신의 이메일을 읽으려는 도둑으로부터 자신을 보호할 수 있을 것입니다. 필요한 것은 인터넷이 연결된 컴퓨터와 이메일 계정, 30분 정도의 시간입니다. </p>
83
84 <p>비록 당신이 숨길 것이 없더라도, 암호화는 감시 시스템의 감시를 어렵게 하고, 자신과 상대방의 개인정보를 보호합니다. 만약 중요한 내용이 있어 그것을 숨겨야 한다면, 좋은 선택입니다; 이 툴은 에드워드 스노든이 그의 유명한 비밀을 NSA로부터 숨기는 데 사용한 도구입니다.</p>
85
86 <p>암호화 도구의 사용과 더불어, 감시에 저항하는 것은 <a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">수집하는 개인정보의 수를 줄이는 것</a>과 같은 정치적인 투쟁이 필요하지만, 기본적인 첫 번째 절차는 스스로를 보호하고 당신의 의사소통을 감시하기 어렵게 하는 것입니다. 시작해 봅시다!</p>
87
88 </div>
89
90 </div>
91 </header><!-- End #header -->
92
93 <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
94 <section class="row" id="section1">
95 <div>
96 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
97 <div class="section-intro">
98 <h2><em>#1</em> 프로그램 얻기</h2>
99 <p class="notes">이 가이드는 자유롭게 이용허락된 몇 가지의 소프트웨어에 의존합니다; 이 소프트웨어들은 완전히 투명하며 누구나 소스 코드를 복제하여 자신만의 버전을 만들 수 있습니다. 이러한 자유는 (윈도우즈와 같은) 상용 소프트웨어와 다르게 감시에서 더욱 안전하게 합니다. 자유 소프트웨어에 대한 더 많은 정보를 <a href="https://u.fsf.org/ys">fsf.org</a>에서 알아보세요.</p>
100
101 <p>대부분의 GNU/리눅스 운영체제는 GnuPG가 설치된 상태로 출시되기 때문에 별도로 설치할 필요가 없습니다. 하지만 GnuPG를 설정하기 전에, 컴퓨터에 이메일 프로그램을 설치한 상태여야 합니다. 대부분의 GNU/리눅스 배포판은 Thunderbird 이메일 프로그램을 설치할 수 있는 방법을 가지고 있습니다. 이메일 프로그램은 G메일 같은 브라우저 기반 이메일과 완전히 같지만, 몇가지의 기능을 더 제공합니다.</p>
102 <p>이미 이 프로그램들을 가지고 있다면, <a href="#step-1b">순서 1.b</a>로 넘어갈 수 있습니다.</p>
103 </div><!-- End .section-intro -->
104
105 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
106 <div id="step-1a" class="step">
107 <div class="sidebar">
108 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>
109 </div><!-- /.sidebar -->
110 <div class="main">
111 <h3><em>순서 1.a</em> (이미 하지 않았다면) 이메일 프로그램을 이메일 계정과 설정하기</h3>
112 <p>이메일 프로그램을 열고 이메일 계정을 설정하는 마법사를 따르세요.</p>
113
114 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
115 <div class="troubleshooting">
116 <h4>문제해결</h4>
117 <dl>
118 <dt>마법사가 무엇인가요?</dt>
119 <dd>마법사는 컴퓨터에서 사용자가 설치 같은 작업을 쉽게 할 수 있도록 돕기 위해 띄워지는 팝업창입니다. 버튼을 클릭하고, 옵션을 선택하며 진행합니다.</dd>
120 <dt>내 이메일 프로그램이 계정을 찾지 못하거나 내 메일을 다운로드하지 않아요</dt>
121 <dd>인터넷을 검색하기 전에, 정확한 이메일 설정을 알아보기 위해 같은 이메일 설정을 사용하는 다른 사람에 물어볼 것을 추천합니다.</dd>
122 <dt class="feedback">당신의 문제에 대한 해결책이 없나요?</dt>
123 <dd class="feedback"><a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">피드백 문서</a>에 글을 남겨 주세요.</dd>
124 </dl>
125 </div><!-- /.troubleshooting -->
126
127 </div><!-- End .main -->
128 </div><!-- End #step1-a .step -->
129
130 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
131 <div id="step-1b" class="step">
132 <div class="sidebar">
133 <ul class="images">
134 <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>
135 <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-02-search.png" alt="Step 1.B: Search Add-ons" /></li>
136 <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-03-install.png" alt="Step 1.B: Install Add-ons" /></li>
137 </ul>
138 </div><!-- /.sidebar -->
139 <div class="main">
140 <h3><em>순서 1.b</em> 이메일 프로그램에 Enigmail 플러그인 설치하기</h3>
141 <p>이메일 프로그램의 메뉴에 부가 기능 버튼을 선택하세요 (도구 부분에 있을 수 있습니다). 확장 기능이 왼쪽에 선택되어 있는지 확인하세요. Enigmail이 보이나요? 보인다면 이 순서를 생략하세요.</p>
142 <p>안 보인다면, 우측 상단의 검색창에 "Enigmail"을 검색하세요. 이제 다운로드할 수 있습니다. 완료했을 때 이메일 프로그램을 재시작하세요.</p>
143 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
144 <div class="troubleshooting">
145 <h4>문제 해결</h4>
146 <dl>
147 <dt>메뉴를 찾을 수 없어요.</dt>
148 <dd>대부분의 이메일 프로그램에서, 메인 메뉴는 세 줄의 수평선으로 표시됩니다.</dd>
149
150 <dt class="feedback">당신의 문제에 대한 해결책이 없나요?</dt>
151 <dd class="feedback"><a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">피드백 문서</a>에 글을 남겨 주세요.</dd>
152 </dl>
153 </div><!-- /.troubleshooting -->
154 </div><!-- End .main -->
155 </div><!-- End #step-1b .step -->
156 </div>
157 </section><!-- End #section1 -->
158
159 <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
160 <section class="row" id="section2">
161 <div>
162 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
163 <div class="section-intro">
164 <h2><em>#2</em> Make your keys</h2>
165 <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>
166
167 <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>
168
169 <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>
170 </div><!-- End .section-intro -->
171
172 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
173 <div id="step-2a" class="step">
174 <div class="sidebar">
175 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>
176 </div><!-- /.sidebar -->
177 <div class="main">
178 <h3><em>Step 2.a</em> Make a keypair</h3>
179 <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>
180 <p>On the second screen, titled "Signing," select "No, I want to create per-recipient rules for emails that need to be signed."</p>
181 <p>Use the default options until you reach the screen titled "Create Key".</p>
182 <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>
183 <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>
184 <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>
185
186 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
187 <div class="troubleshooting">
188 <h4>Troubleshooting</h4>
189 <dl>
190 <dt>I can't find the OpenPGP menu.</dt>
191 <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>
192 <dt>The wizard says that it cannot find GnuPG.</dt>
193
194 <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>
195
196 <dt class="feedback">Don't see a solution to your problem?</dt>
197 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
198 </dl>
199 </div><!-- /.troubleshooting -->
200 </div><!-- End .main -->
201 </div><!-- End #step-2a .step -->
202
203 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
204 <div id="step-2b" class="step">
205 <div class="main">
206 <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
207 <p>In your email program's menu, select OpenPGP &rarr; Key Management.</p>
208 <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
209 <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>
210 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
211 <div class="troubleshooting">
212 <h4>Troubleshooting</h4>
213 <dl>
214 <dt>The progress bar never finishes</dt>
215 <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>
216 <dt>My key doesnt appear in the list</dt>
217 <dd>Try checking Show Default Keys.</dd>
218
219 <dt class="feedback">Don't see a solution to your problem?</dt>
220 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
221
222 </dl>
223 </div><!-- /.troubleshooting -->
224 </div><!-- End .main -->
225 </div><!-- End #step-2a .step -->
226 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
227 <div id="terminology" class="step">
228 <div class="main">
229 <h3>GnuPG, OpenPGP, what?</h3>
230 <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>
231 </div><!-- End .main -->
232 </div><!-- End #terminology.step-->
233
234
235 </div>
236 </section><!-- End #section2 -->
237
238 <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
239 <section class="row" id="section3">
240 <div>
241 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
242 <div class="section-intro">
243 <h2><em>#3</em> Try it out!</h2>
244 <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>
245 </div><!-- End .section-intro -->
246
247 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
248 <div id="step-3a" class="step">
249 <div class="sidebar">
250 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
251 </div><!-- /.sidebar -->
252 <div class="main">
253 <h3><em>Step 3.a</em> Send Adele your public key</h3>
254 <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>
255
256 <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>
257
258 <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>
259 </div><!-- End .main -->
260 </div><!-- End #step-3b .step -->
261
262 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
263 <div id="step-3b" class="step">
264 <div class="main">
265 <h3><em>Step 3.b</em> Send a test encrypted email</h3>
266 <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>
267 <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>
268 <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>
269 <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
270
271 <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>
272
273 <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>
274 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
275 <div class="troubleshooting">
276 <h4>Troubleshooting</h4>
277 <dl>
278 <dt>Enigmail can't find Adele's key</dt>
279 <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>
280 <dt class="feedback">Don't see a solution to your problem?</dt>
281 <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
282 </dl>
283 </div><!-- /.troubleshooting -->
284 </div><!-- End .main -->
285 </div><!-- End #step-3b .step -->
286
287 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
288 <div id="step-headers_unencrypted" class="step">
289 <div class="main">
290 <h3><em>Important:</em> Security tips</h3>
291 <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>
292 <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>
293 </div><!-- End .main -->
294 </div><!-- End #step-headers_unencrypted .step-->
295
296
297 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
298 <div id="step-3c" class="step">
299 <div class="main">
300 <h3><em>Step 3.c</em> Receive a response</h3>
301 <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>
302 <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>
303 <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>
304 <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>
305 <p>Notice the bar that Enigmail shows you above the message, with information about the status of Adele's key.</p>
306 </div><!-- End .main -->
307 </div><!-- End #step-3c .step -->
308
309 <!-- STEP 3D IS COMMENTED OUT UNTIL WE FIND A WAY TO VALIDATE SIGNATURES
310 <div id="step-3d" class="step">
311 <div class="main">
312 <h3><em>Step 3.d</em> Send a test signed email to a friend</h3>
313 <p>Write a new email in your email program, addressed to a friend. If you want, tell them about this guide!</p>
314 <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>
315 <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>
316 </div>
317 </div>-->
318 </div>
319 </section><!-- End #section3 -->
320
321
322 <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
323 <section class="row" id="section4">
324 <div>
325 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
326 <div class="section-intro">
327 <h2><em>#4</em> Learn the Web of Trust</h2>
328 <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>
329
330 <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>
331
332 <p>People's public keys are usually identified by their key fingerprint, which is a string of digits like DD878C06E8C2BEDDD4A440D3E573346992AB3FF7 (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>
333
334 <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 92AB3FF7 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>
335
336
337 </div><!-- End .section-intro -->
338
339 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
340 <div id="step-4a" class="step">
341 <div class="sidebar">
342 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
343 </div><!-- /.sidebar -->
344 <div class="main">
345 <h3><em>Step 4.a</em> Sign a key</h3>
346 <p>In your email program's menu, go to OpenPGP &rarr; Key Management.</p>
347 <p>Right click on Adele's public key and select Sign Key from the context menu.</p>
348 <p>In the window that pops up, select "I will not answer" and click OK.</p>
349 <p>In your email program's menu, go to OpenPGP &rarr; Key Management &rarr; Keyserver &rarr; Upload Public Keys and hit OK.</p>
350 <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>
351
352
353 <!--<div id="pgp-pathfinder">
354 <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
355 <p><strong>From:</strong> <input type="text" placeholder="xD41A008" name="FROM"></p>
356 <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
357 <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
358 </form>
359 </div><!-- End #pgp-pathfinder -->
360
361 </div><!-- End .main -->
362 </div><!-- End #step-4a .step -->
363 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
364 <div id="step-sign_real_keys" class="step">
365 <div class="main">
366 <h3><em>Important:</em> check people's identification before signing their keys</h3>
367 <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>
368 </div><!-- End .main -->
369 </div><!-- End #step-sign_real_keys .step-->
370
371
372
373 </div>
374 </section><!-- End #section4 -->
375
376 <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
377 <section id="section5" class="row">
378 <div>
379 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
380 <div class="section-intro">
381 <h2><em>#5</em> Use it well</h2>
382 <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>
383 </div><!-- End .section-intro -->
384
385 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
386 <div id="step-5a" class="step">
387 <div class="sidebar">
388 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well" /></p>
389 </div><!-- /.sidebar -->
390 <div class="main">
391 <h3>When should I encrypt?</h3>
392
393 <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>
394
395 <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>
396
397 </div><!-- End .main -->
398 </div><!-- End #step-5a .step -->
399
400 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
401 <div id="step-5b" class="step">
402 <div class="sidebar">
403 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
404 </div><!-- /.sidebar -->
405 <div class="main">
406 <h3><em>Important:</em> Be wary of invalid keys</h3>
407 <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>
408 <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>
409 <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>
410 </div><!-- End .main -->
411 </div><!-- End #step-5b .step -->
412
413 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
414 <div id="step-5c" class="step">
415 <div class="main">
416 <h3>Copy your revocation certificate to somewhere safe</h3>
417 <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>
418 <p>If your private key ever gets lost or stolen, you'll need this certificate file.</p>
419 </div><!-- End .main -->
420 </div><!-- End #step-5c .step -->
421
422 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
423 <div id="step-lost_key" class="step">
424 <div class="main">
425 <h3><em>Important:</em> act swiftly if someone gets your private key</h3>
426 <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>
427 </div><!-- End .main -->
428 </div><!-- End #step-lost_key .step-->
429
430 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
431 <div id="step-5d" class="step">
432 <div class="main">
433 <h3>Make your public key part of your online identity</h3>
434 <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>
435
436 <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>
437 </div><!-- End .main
438 </div> End #step-5d .step-->
439
440
441 </div>
442 </section><!-- End #section5 -->
443
444
445
446 <!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
447 <section class="row" id="section6">
448 <div id="step-click_here" class="step">
449 <div class="main">
450 <h2><a href="next_steps.html">Click here when you're done</a></h2>
451
452 </div><!-- End .main -->
453 </div><!-- End #step-click_here .step-->
454
455 </section><!-- End #section6 -->
456
457 <!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
458 <!-- When un-commenting this section go to main.css and search
459 for /* Guide Sections Background */ then add #faq to the desired color
460
461 <section class="row" id="faq">
462 <div>
463 <div class="sidebar">
464 <h2>FAQ</h2>
465 </div>
466
467 <div class="main">
468 <dl>
469 <dt>My key expired</dt>
470 <dd>Answer coming soon.</dd>
471
472 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
473 <dd>Answer coming soon.</dd>
474
475 <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>
476 <dd>Answer coming soon.</dd>
477 </dl>
478 </div>
479 </div>
480 </section> --><!-- End #faq -->
481
482 <!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
483 <footer class="row" id="footer">
484 <div>
485 <div id="copyright">
486 <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>
487 <p>저작권 &copy; 2014 <a href="https://u.fsf.org/ys">자유 소프트웨어 재단</a> <a href="https://my.fsf.org/donate/privacypolicy.html">개인정보 정책</a>. <a href="https://u.fsf.org/yr">가입하기.</a></p>
488 <p><em>버전 2.0, 2014618일 공개 한국어 번역 홍용민 </em></p>
489 <p>이 문서의 이미지는 <a href="https://creativecommons.org/licenses/by/4.0/deed.ko">크리에이티브 커먼즈 저작자표시 4.0 (혹은 이후 버전)으로</a>, 그리고 나머지 내용은 <a href="https://creativecommons.org/licenses/by-sa/4.0/deed.ko">크리에이티브 커먼즈 저작자표시-동일조건변경허락 4.0 (혹은 이후 버전)</a>으로 배포됩니다. &mdash; <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">왜 이런 라이선스인가요?</a></p>
490 <p><a href="gnupg-guide.zip">이 가이드</a><a href="gnupg-infographic.zip">인포그래픽</a>의 소스 패키지를 다운로드 받으세요. 이 가이드에 사용된 폰트&amp; 인포그래픽: <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>
491 <p>
492 <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
493 rel="jslicense">
494 자바스크립트 라이선스 정보
495 </a>
496 </p>
497 </div><!-- /#copyright -->
498 <p class="credits">
499 인포그래픽과 가이드 디자인은 <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong>에서 제공합니다. <img src="//static.fsf.org/nosvn/enc-dev0n/img/jplusplus.png" alt="Journalism++" /></a>
500 </p><!-- /.credits -->
501 </div>
502 </footer><!-- End #footer -->
503
504 <script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
505 <script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
506
507 <!-- Piwik -->
508 <script type="text/javascript">
509 /*
510 @licstart The following is the entire license notice for the
511 JavaScript code in this page.
512
513 Copyright 2014 Matthieu Aubry
514
515 This program is free software: you can redistribute it and/or modify
516 it under the terms of the GNU General Public License as published by
517 the Free Software Foundation, either version 3 of the License, or
518 (at your option) any later version.
519
520 This program is distributed in the hope that it will be useful,
521 but WITHOUT ANY WARRANTY; without even the implied warranty of
522 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
523 GNU General Public License for more details.
524
525 You should have received a copy of the GNU General Public License
526 along with this program. If not, see http://www.gnu.org/licenses/.
527
528 @licend The above is the entire license notice
529 for the JavaScript code in this page.
530 */
531 var _paq = _paq || [];
532 _paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
533 _paq.push(["setCookieDomain", "*.www.fsf.org"]);
534 _paq.push(["setDomains", ["*.www.fsf.org","*.www.fsf.org"]]);
535 _paq.push(["trackPageView"]);
536 _paq.push(["enableLinkTracking"]);
537
538 (function() {
539 var u=(("https:" == document.location.protocol) ? "https" : "http") + "://piwik.fsf.org/";
540 _paq.push(["setTrackerUrl", u+"piwik.php"]);
541 _paq.push(["setSiteId", "5"]);
542 var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
543 g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
544 })();
545 </script>
546 <!-- End Piwik Code -->
547 </body>
548 </html>