Fixed extra comments
[enc-live.git] / ko / index.html
index 6eedeac978c54ef7fab6c440cbcf483304c12762..9f43a6b0daf5d87554d708656a979e3e8ec749a1 100644 (file)
@@ -5,7 +5,7 @@
 
                        <title>스스로 이메일 보호하기 - GnuPG 암호화를 이용한 감시 방어 가이드</title>
                        <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail" />
-      <meta name="description" content="Email surveillance violates our fundamental rights and makes free speech risky. This guide will teach you email self-defense in 30 minutes with GnuPG.">
+       <meta name="description" content="이메일 감시는 우리의 기본적인 권리를 침해하고 자유로운 발언을 할 권리를 위협합니다. 이 가이드는 30분 안에 GnuPG를 이용해 이메일을 스스로 보호하는 법에 대해 알려줍니다. ">
 
       <meta name="viewport" content="width=device-width, initial-scale=1">
                        <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css">
 
                           <!-- Language list for browsers that do not have JS enabled -->
                           <ul id="languages" class="os">
-                            <li><a class="current" href="/en">한국어</a></li>
-                            <li><a href="/es">español</a></li>
+                            <li><a href="/en">English</a></li>
+                            <!--<li><a href="/es">español</a></li>-->
                             <li><a href="/fr">français</a></li>
                             <li><a href="/de">deutsch</a></li>
                             <li><a href="/pt-br">português do Brasil</a></li>
                             <li><a href="/tr">türkçe</a></li>
-                            <li><a href="/ro">română</a></li>
+                            <!--<li><a href="/ro">română</a></li>-->
                             <li><a href="/ru">русский</a></li>
-                            <li><a href="/ml">മലയാളം</a></li>
-                            <li><a href="/ko">한국어</a></li>
+                            <!--<li><a href="/ml">മലയാളം</a></li>-->
+                            <!--<li><a class="current" href="/ko">한국어</a></li>-->
                             <li><a href="/ja">日本語</a></li>
+                            <!--<li><a href="/el">ελληνικά</a></li>-->
                           </ul>
 
                           <ul id="menu" class="os">
@@ -79,9 +80,9 @@
                                <div class="intro">
                                        <p>
                                                <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>
-                                       대량 감시는 우리의 근본적인 권리를 침해하며 자유로운 발언을 할 권리를 위협합니다. 이 가이드는 간단한 감시로부터의 자가 보호 기술인 이메일 암호화를 안내할 것입니다. 이 가이드를 끝내면 당신은 암호화된 이메일을 통해 정보기관과 당신의 이메일을 읽으려는 도둑으로부터 자신을 보호할 수 있을 것입니다. 필요한 것은 인터넷이 연결된 컴퓨터와 이메일 계정, 30분 정도의 시간입니다. </p>
+                                       대량 감시는 우리의 근본적인 권리를 침해하며 자유로운 발언을 할 권리를 위협합니다. 이 가이드는 간단한 감시로부터의 자가 보호 기술인 이메일 암호화를 안내할 것입니다. 이 가이드를 끝내면 당신은 암호화된 이메일을 통해 정보기관과 당신의 이메일을 읽으려는 도둑으로부터 자신을 보호할 수 있을 것입니다. 인터넷이 연결된 컴퓨터와 이메일 계정, 30분 정도의 시간이 필요합니다.</p>
 
-<p>비록 당신이 숨길 것이 없더라도, 암호화는 감시 시스템의 감시를 어렵게 하고, 자신과 상대방의 개인정보를 보호합니다. 만약 중요한 내용이 있어 그것을 숨겨야 한다면, 좋은 선택입니다; 이 툴은 에드워드 스노든이 그의 유명한 비밀을 NSA로부터 숨기는 데 사용한 도구입니다.</p>
+<p>비록 당신이 숨길 것이 없더라도, 암호화는 감시 시스템의 감시를 어렵게 하고, 자신과 상대방의 개인정보를 보호합니다. 만약 중요한 내용이 있어 그것을 숨겨야 한다면, GnuPG를 사용하는 것이 현명한 선택입니다; 이 툴은 에드워드 스노든이 그의 유명한 비밀을 NSA로부터 숨기는 데 사용한 도구입니다.</p>
 
 <p>암호화 도구의 사용과 더불어, 감시에 저항하는 것은 <a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">수집하는 개인정보의 수를 줄이는 것</a>과 같은 정치적인 투쟁이 필요하지만, 기본적인 첫 번째 절차는 스스로를 보호하고 당신의 의사소통을 감시하기 어렵게 하는 것입니다. 시작해 봅시다!</p>
 
                                                <p>"키 생성" 제목이 나올 때까지 기본 옵션을 사용하세요.</p>
                                                <p>"키 생성" 창에서, 강한 패스프레이즈를 사용하세요! 당신의 비밀번호는 최소한 12자가 되어야 하며 한 개의 소문자와 대문자, 숫자와 특수기호를 포함해야 합니다. 패스프레이즈를 잊어버린다면, 이 모든 일들은 시간 낭비가 될 것입니다!</p>
                                        <p class="notes">프로그램은 다음 순서에서 "키 생성" 스크린을 완료하는 데 약간의 시간이 소요됩니다. 컴퓨터로 영화를 본다거나 인터넷 검색을 한다던지 등의 다른 작업을 하세요. 컴퓨터를 더 많이 사용하면 할수록, 키 생성에 걸리는 시간이 짧아집니다.</p>
-                                               <p>OpenPGP 확인 창이 뜨면, 인증서 생성 을 누르고 컴퓨터의 안전한 곳에 보관하기를 선택합니다. ("폐기 인증서"라는 별도의 창을 만들고 그곳에 저장하기를 권합니다. 폐기 저장소가 무엇인지에 대해서는 <a href="#section5">문단 5</a>에서 알아볼 수 있습니다. 설정 마법사는 폐기 인증서를 별도의 기기에 저장할 것을 권하지만, 현재로선 그럴 필요는 없습니다. The setup wizard will ask you to move it onto an external device, but that isn't necessary at this moment.</p>
+                                               <p>OpenPGP 확인 창이 뜨면, 인증서 생성 을 누르고 컴퓨터의 안전한 곳에 보관하기를 선택합니다. ("폐기 인증서"라는 별도의 창을 만들고 그곳에 저장하기를 권합니다. 폐기 저장소가 무엇인지에 대해서는 <a href="#section5">문단 5</a>에서 알아볼 수 있습니다. 설정 마법사는 폐기 인증서를 별도의 기기에 저장할 것을 권하지만, 현재로선 그럴 필요는 없습니다. </p>
 
                                                <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
                                                <div class="troubleshooting">
                                <div id="step-3b" class="step">
                                        <div class="main">
                                                        <h3><em>순서 3.b</em> 테스트 암호화 메일 보내기</h3>
-                                                       <p>이메일 프로그램에서 받는이가 edward-ko@fsf.org 인 새 이메일을 작성하세요. 제목을 "암호화 테스트"혹은 비슷한 내용으로 하고, 아무 내용이나 쓰세요. 아직 이메일을 보내지는 마세요.</p>
+                                                       <p>이메일 프로그램에서 받는 이가 edward-ko@fsf.org 인 새 이메일을 작성하세요. 제목을 "암호화 테스트"혹은 비슷한 내용으로 하고, 아무 내용이나 쓰세요. 아직 이메일을 보내지는 마세요.</p>
                                                        <p>보내는 창의 아래의 키 아이콘을 누릅니다. (노랗게 변할 것입니다!) 이렇게 하면 Enigmail이 당신이 이전 순서에서 다운로드받은 키로 암호화하게 됩니다.</p>
                                                        <p class="notes">키 옆에 연필이 있습니다. 이 버튼을 클릭하면, Enigmail은 당신의 비밀키로 생성한 특별하고 고유한 서명을 메시지에 추가합니다. 이 기능은 암호화와는 다른 기능이므로, 이 가이드에서는 사용하지 않습니다.</p>
-                                                       <p>보내기 를 누르세요. Enigmail은 "받는이가 존재하지 않거나, 신뢰되지 않거나, 찾을 수 없습니다"라는 팝업을 보여 줄 것입니다.</p>
+                                                       <p>보내기 를 누르세요. Enigmail은 "받는 이가 존재하지 않거나, 신뢰되지 않거나, 찾을 수 없습니다"라는 팝업을 보여 줄 것입니다.</p>
 
                                                        <p>Edward에게 암호화하고 이메일을 보내려면, 그의 공개키가 필요하기 때문에, Enigmail에게 공개키를 다운로드 하게 해야 합니다. 없는 키 다운로드를 클릭한 후, 기본 키서버를 이용합니다. 키를 찾으면, 첫번째 키를 선택하고, 완료 를 누릅니다. 다음 팝업에서도 완료 를 누릅니다.</p>
 
-                                                       <p>이제 다시 "받는이가 존재하지 않거나, 신뢰되지 않거나, 찾을 수 없습니다" 창으로 돌아왔습니다. Edward의 키를 리스트에서 클릭하고 완료를 누릅니다. 메시지가 자동으로 보내지지 않는다면, 발송을 누르세요.</p>
+                                                       <p>이제 다시 "받는 이가 존재하지 않거나, 신뢰되지 않거나, 찾을 수 없습니다" 창으로 돌아왔습니다. Edward의 키를 리스트에서 클릭하고 완료를 누릅니다. 메시지가 자동으로 보내지지 않는다면, 발송을 누르세요.</p>
                                        <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
                                                        <div class="troubleshooting">
                                                                <h4>문제 해결</h4>
                                <div id="step-headers_unencrypted" class="step">
                                        <div class="main">
                                                <h3><em>중요:</em>보안 팁</h3>
-                                               <p>당신이 당신의 이메일을 암호화해도, 제목은 암호화되지 않으므로 제목에 개인정보를 넣지 마세요. 보낸 이와 받는이의 주소도 암호화되지 않으므로, 이러한 정보는 감시 시스템이 읽을 수 있습니다. 첨부 파일이 있다면, 메일을 보낼 떄 Enigmail은 첨부 파일을 암호화할 것인지 물을 것입니다.</p>
+                                               <p>당신이 당신의 이메일을 암호화해도, 제목은 암호화되지 않으므로 제목에 개인정보를 넣지 마세요. 보낸 이와 받는 이의 주소도 암호화되지 않으므로, 이러한 정보는 감시 시스템이 읽을 수 있습니다. 첨부 파일이 있다면, 메일을 보낼 떄 Enigmail은 첨부 파일을 암호화할 것인지 물을 것입니다.</p>
 <p>키 아이콘을 이메일 작성 <strong>전</strong>에 클릭하는 것도 좋은 생각입니다. 그렇지 않다면, 암호화되지 않은 초안이 이메일 서버로 전송되며, 이 초안은 스누핑의 타겟이 될 수 있습니다.</p>
                                        </div><!-- End .main -->
                                </div><!-- End #step-headers_unencrypted .step-->
                        <div>
                                        <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
                                <div class="section-intro">
-                                               <h2><em>#5</em> Use it well</h2>
-<p>Everyone uses GnuPG a little differently, but it's important to follow some basic practices to keep your email secure. Not following them, you risk the privacy of the people you communicate with, as well as your own, and damage the Web of Trust.</p>
+                                               <h2><em>#5</em> 잘 사용하기</h2>
+<p>사람마다 GnuPG를 약간씩 다르게 사용하지만, 이메일을 안전하게 보호하기 위해 몇가지의 습관을 들이는 것이 중요합니다. 이를 따르지 않으면, 당신과 통신하는 사람과의 보안을 위협할 뿐만 아니라, 신뢰의 웹을 손상시킵니다.</p>
                                </div><!-- End .section-intro -->
 
                                <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
                                                <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well" /></p>
                                        </div><!-- /.sidebar -->
                                        <div class="main">
-                                               <h3>When should I encrypt?</h3>
+                                               <h3>언제 암호화를 해야 하죠?</h3>
 
-                                               <p>The more you can encrypt your messages, the better. This is because, if you only encrypt emails occasionally, each encrypted message could raise a red flag for surveillance systems. If all or most of your email is encrypted, people doing surveillance won't know where to start.</p>
+                                               <p>더 많은 메시지를 암호화할수록 좋습니다! 왜냐하면, 만약 당신이 가끔 암호화를 하면 암호화된 메시지를 보낼 때 감시 시스템이 경보를 보낼 수 있지만, 대부분의 이메일, 혹은 모든 이메일, 이 암호화되면, 정보기관에서는 어디서부터 시작해야 할 지 모르게 되기 때문입니다.</p>
 
-<p>That's not to say that only encrypting some of your email isn't helpful -- it's a great start and it makes bulk surveillance more difficult.</p>
+<p>일부분의 이메일을 암호화하는 것이 나쁘다는 것은 아닙니다 -- 일부분의 암호화도 좋은 시작이며, 감시 시스템의 작동을 어렵게 합니다.</p>
 
                                        </div><!-- End .main -->
                                </div><!-- End #step-5a .step -->
                                                <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
                                        </div><!-- /.sidebar -->
                                        <div class="main">
-                                               <h3><em>Important:</em> Be wary of invalid keys</h3>
-                                               <p>GnuPG makes email safer, but it's still important to watch out for invalid keys, which might have fallen into the wrong hands. Email encrypted with invalid keys might be readable by surveillance programs.</p>
-                                               <p>In your email program, go back to the second email that Adele sent you. Because Adele encrypted it with your public key, it will have a message from OpenPGP at the top, which most likely says "OpenPGP: Part of this message encrypted."</p>
-<p><b>When using GnuPG, make a habit of glancing at that bar. The program will warn you there if you get an email encrypted with a key that can't be trusted.</b></p>
+                                               <h3><em>중요:</em>폐기된 키를 경계하세요</h3>
+                                               <p>GnuPG는 이메일을 안전하게 만들지만, 폐기된 키를 조심하는 것 또한 조심합니다. 이러한 키는 다른 사람에게 넘어갔을 수 있습니다. 폐기된 키로 암호화된 내용은 감시 시스템에서 읽을 수 있을 수 있습니다.</p>
+                                               <p>이메일 프로그램에서, Edward가 보낸 두번째 이메일로 돌아가세요. Edward가 당신의 공개키로 이메일을 암호화했기 때문에, OpenPGP가 "OpenPGP:암호화됨 메시지의 일부분"이라는 메시지를 갖고 있을 것입니다.</p>
+<p><b>GnuPG를 사용할 때, 그 부분을 주의깊게 보는 습관을 들이세요. 프로그램은 신뢰할 수 없는 키로 암호화된 이메일에 대해 경고할 것입니다.</b></p>
                                        </div><!-- End .main -->
                                </div><!-- End #step-5b .step -->
 
                                <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
                                <div id="step-5c" class="step">
                                        <div class="main">
-                                               <h3>Copy your revocation certificate to somewhere safe</h3>
-                                               <p>Remember when you created your keys and saved the revocation certificate that GnuPG made? It's time to copy that certificate onto the safest digital storage that you have -- the ideal thing is a flash drive, disk or hard drive stored in a safe place in your home.</p>
-<p>If your private key ever gets lost or stolen, you'll need this certificate file.</p>
+                                               <h3>폐기 인증서를 안전한 다른 곳에 저장하세요</h3>
+                                               <p>키를 만들 때 폐기 인증서를 생성하고 다른 곳에 저장헀던 것을 기억하시나요? 이제 이 인증서를 당신이 가진 가장 안전한 저장소로 옮길 때입니다 -- 이상적인 장소는 집에 있는 플래시 드라이브, CD, 혹은 안전한 장소에 있는 하드 디스크입니다.</p>
+<p>만약 당신이 당신의 개인키를 잃었거나 도둑맞았다면, 이 폐기 인증서가 필요할 것입니다.</p>
                                        </div><!-- End .main -->
                                </div><!-- End #step-5c .step -->
 
                                <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
                                <div id="step-lost_key" class="step">
                                        <div class="main">
-                                               <h3><em>Important:</em> act swiftly if someone gets your private key</h3>
-                                               <p>If you lose your private key or someone else gets ahold of it (say, by stealing or cracking your computer), it's important to revoke it immediately before someone else uses it to read your encrypted email. This guide doesn't cover how to revoke a key, but you can follow the <a href="https://www.gnupg.org/gph/en/manual.html#AEN305">instructions on the GnuPG site</a>. After you're done revoking, send an email to everyone with whom you usually use your key to make sure they know.</p>
+                                               <h3><em>중요:</em> 다른 사람이 개인키를 얻었을 때 빠르게 행동하세요</h3>
+                                               <p>당신이 개인키를 잃었거나 다른 사람이 개인키를 얻었다면 (컴퓨터를 훔치거나 크래킹을 통해서) 다른 사람이 그 키로 암호화된 이메일을 읽기 전에 폐기하는 것이 중요합니다. 이 가이드에서는 그러한 방법을 다루고 있지는 않지만, <a href="https://www.gnupg.org/gph/en/manual.html#AEN305">GnuPG 사이트의 정보 (영어)</a>가 도움이 될 것입니다. 폐기를 한 후에, 당신의 키를 자주 사용하는 사람에게 당신의 키를 폐기했다는 사실을 알리세요.</p>
                                        </div><!-- End .main -->
                                </div><!-- End #step-lost_key .step-->
 
                <section class="row" id="section6">
                        <div id="step-click_here" class="step">
                                        <div class="main">
-                                         <h2><a href="next_steps.html">Click here when you're done</a></h2>
+                                         <h2><a href="next_steps.html">완료했으면 여기를 클릭하세요</a></h2>
 
                                        </div><!-- End .main -->
                                </div><!-- End #step-click_here .step-->
                        </div>
                </section> --><!-- End #faq -->
 
+
 <!-- ~~~~~~~~~ Footer  ~~~~~~~~~ -->
                <footer class="row" id="footer">
                        <div>
                                <div id="copyright">
                                        <h4><a href="https://u.fsf.org/ys"><img alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png"></a></h4>
                                        <p>저작권 &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>
-                                        <p><em>버전 2.0, 2014년 6월 18일 공개 한국어 번역 홍용민 </em></p>
+                                        <p><em>버전 2.0, 한국어 번역 홍용민</em><a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">에드워드 답변 봇, PROGRAMMERNAME (WARNING: NOTIFY ME WHEN MODIFYING PROGRAMMERNAME! KOREAN HAS SPECIAL GRAMMER OPTION SHOULD BE REVIEWED. ) 이/가 제작함, GNU 일반 공중 이용 허가서 (VERSION)으로 배포됨.</a></p>
 <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>
                                        <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>
                                         <p>