ja/index.html

   1 <!DOCTYPE html>
   2 <html>
   3         <head>
   4                         <meta charset="utf-8">
   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" />
   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>Email Self-Defense</h1>
  22
  23                           <!-- Language list for browsers that do not have JS enabled -->
  24                           <ul id="languages" class="os">
  25                             <li><a 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 class="current" href="/ja">日本語</a></li>
  36                             <li><a href="/el">ελληνικά</a></li>
  37                           </ul>
  38
  39                           <ul id="menu" class="os">
  40                             <li class="spacer">
  41                               <a href="index.html" class="current">GNU/Linux</a>
  42                             </li>
  43                             <li>
  44                               <a href="mac.html">Mac OS</a>
  45                             </li>
  46                             <li>
  47                               <a href="windows.html">Windows</a>
  48                             </li>
  49                             <li class="spacer">
  50                               <a href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email encryption for everyone via %40fsf">
  51                                 #EmailSelfDefense
  52                               </a>
  53                             </li>
  54                           </ul>
  55
  56                                 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
  57                                 <div id="fsf-intro">
  58                                   <h3>
  59                                     <a href="http://u.fsf.org/ys">
  60                                       <img alt="Free Software Foundation"
  61                                            src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png">
  62                                     </a>
  63                                   </h3>
  64                                   <div class="fsf-emphasis">
  65                                     <p>
  66                                                                                                                                                         Free Software Foundationはパソコンのユーザの権利のために戦って、（自由の）のフリーソフトウェアの開発を促進します。無差別な監視に抵抗するのは我々にとって非常に大切なことです。
  67                                     </p>
  68                                     <p>
  69                                       <strong>
  70                                                                                                                                                                         Free Software Foundationはこのようなツールをオンラインでもオフラインでも活躍的に促進して、自分のプライバシーを守るためにできるだけ多くの人のフリーソフトウェアへのフリーソフトウェアの使用の第一歩を支援しようと思っています。どうぞFree Software Foundationを支援して、会員になってください。
  71                                       </strong>
  72                                     </p>
  73                                   </div>
  74
  75                                         <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>
  76
  77                                 </div><!-- End #fsf-intro -->
  78
  79                                 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
  80                                 <div class="intro">
  81                                         <p>
  82                                                 <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png" alt="View &amp; share our infographic &rarr;" /></a>
  83                                 無差別な監視は人権の侵害であり、言論の自由と対立するものです。このガイドでは、このような監視に対する自衛手段としてメールの暗号化を説明します。このガイドを読み終えれば、監視エージェントやデータ泥棒には読めないメールを送受信することができるようになります。必要なのはインターネットに接続できるパソコンとメールアカウントの他には、ほんの30分ほどです。
  84                                         </p>
  85
  86
  87 <p>何も隠そうと思うものがなくても、暗号化技術を使えば相手のプライバシーを守り、無差別監視システムによる侵害を困難にします。もし大事で隠すべき何かをお持ちなら、頼りになるツールがすでにあります。このツールはエドワード・スノーデンが貴重な秘密情報を報道機関に送るためにも使ったものです。</p>
  88
  89 <p>監視に抵抗するには暗号化の他にも政治的な行動によって<a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">我々について収集されるデータ減らす必要</a>があります。その重要な第一歩としてまずあなた自身を守り、あなたを監視されにくくするのです。では始めましょう！</p>
  90
  91                                 </div>
  92
  93                         </div>
  94                 </header><!-- End #header -->
  95
  96 <!-- ~~~~~~~~~ Section 1: Get the pieces  ~~~~~~~~~ -->
  97                 <section class="row" id="section1">
  98                         <div>
  99                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 100                                 <div class="section-intro">
 101                                                 <h2><em>#1</em> 必要な部品を集めよう</h2>
 102 <p class="notes">このガイドで登場するソフトウェアは自由なソフトウェアライセンスに基づいています。そのようなソフトは完全な透明性があり、誰でもコピーができ、自分だけのバーションを作ることもできます。そういう特徴があるため、フリーソフトウェアライセンスのソフト（短くフリーソフト）は（Windowsのような）プロプライエタリソフト、つまりは売っている会社だけが中身を知っているようなソフトよりよほど監視しにくいのです。詳しくは<a href="https://u.fsf.org/ys">fsf.org</a>をご覧ください。</p>
 103
 104 <p>GNU/LinuxのオペレーティングシステムはほとんどにあらかじめGnuPGがインストールされているので、ダウンロードする必要はありません。でもGnuPGを設定する前に、デスクトップ用のメールプログラムをインストールしなければならないのです。うまい具合にほとんどのGnu/LinuxのディストリビューションではフリーソフトのThunderbirdというメールプログラムをインストールできます。ブラウザーを使ってもGmailのようなメールアカウントをアクセスできますが、Thunderbirdを始めとするメールプログラムはブラウザーよりも多機能です。</p>
 105
 106                         <p>そういうメールプログラムがもうパソコンにインストールされているなら、<a href="#step-1b">1.B</a>に進んでください。</p>
 107                                 </div><!-- End .section-intro -->
 108
 109                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 110                                 <div id="step-1a" class="step">
 111                                         <div class="sidebar">
 112                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>
 113                                         </div><!-- /.sidebar -->
 114                                         <div class="main">
 115                                                 <h3><em>1.A</em> メールプログラムに自分のメールアカウントを設定する（まだ設定済でない場合）</h3>
 116                                                 <p>メールプログラムを起動し、ウィザードの指示に従ってメールアカウントを設定してください。</p>
 117
 118                                                 <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 119                                                 <div class="troubleshooting">
 120                                                         <h4>トラブル・シューティング</h4>
 121                                                         <dl>
 122                                                                 <dt>ウィザードとは何ですか？</dt>
 123                                                                         <dd>ウィザードとは、パソコンで何かを設定するとかインストールするためのウィンドウが順番に表れるようになっているものす。「次へ」のボタンをクリックして、設定をしていきます。</dd>
 124                                                                 <dt>私のメールプログラムではメールアカウントが見つからない、またはメールがダウンロードされません</dt>
 125                                                                         <dd>インターネットを検索する前に、同じメールプログラムを使っている人に正しい設定方法をたずねることをお勧めします。</dd>
 126                                                                 <dt class="feedback">問題が解決しませんでしたか？>
 127                                                                 <dd class="feedback"><a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">フィードバックのページ</a>で知らせてください。</dd>
 128                                                         </dl>
 129                                                 </div><!-- /.troubleshooting -->
 130
 131                                         </div><!-- End .main -->
 132                                 </div><!-- End #step1-a .step -->
 133
 134                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 135                                 <div id="step-1b" class="step">
 136                                         <div class="sidebar">
 137                                                 <ul class="images">
 138                                                         <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>
 139                                                         <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-02-search.png" alt="Step 1.B: Search Add-ons" /></li>
 140                                                         <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-03-install.png" alt="Step 1.B: Install Add-ons" /></li>
 141                                                 </ul>
 142                                         </div><!-- /.sidebar -->
 143                                         <div class="main">
 144                                                 <h3><em>Step 1.B</em> Enigmail（エニグメール）プラグインをメールプログラムにインストール</h3>
 145                                                 <p>メールプログラムのメニューの中から「アドイン」を選択してください。これはたいてい「ツール」というメニューの下にあります。必要な拡張機能を、左側のマークで選択します。すでにEnigmailが表示されていれば、すぐ次のステップは飛ばしてください。</p>
 146                                                 <p>表示されていなければ、上の検索バーを使って Enigmailを検索して、プラグインをインストールしてください。インストールが完了したら、メールプログラムを再起動してください。</p>
 147                                                 <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 148                                                 <div class="troubleshooting">
 149                                                         <h4>トラブル・シューティング</h4>
 150                                                         <dl>
 151                                                                 <dt>メニューが見つかりません。</dt>
 152                                                                         <dd>メニューが横棒3本で表示されるメールプログラムもたくさんあります。</dd>
 153
 154                                                                 <dt class="feedback">問題が解決しませんでしたか？>
 155                                                                                 <dd class="feedback"><a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">フィードバックのページ</a>で知らせてください。</dd>
 156                                                         </dl>
 157                                                 </div><!-- /.troubleshooting -->
 158                                         </div><!-- End .main -->
 159                                 </div><!-- End #step-1b .step -->
 160                         </div>
 161                 </section><!-- End #section1 -->
 162
 163 <!-- ~~~~~~~~~ Section 2: Make your keys  ~~~~~~~~~ -->
 164                 <section class="row" id="section2">
 165                         <div>
 166                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 167                                 <div class="section-intro">
 168                                         <h2><em>#2</em> 自分だけの鍵を作る</h2>
 169                                                 <p>GnuPGシステムを使うためには、公開鍵と秘密鍵が必要です。合わせてキーペアといいます。どちらの鍵もランダムに生成された文字や数字の長い並びで、あなた専用のものです。そして公開鍵と秘密鍵とは特別な数学的な関数で関連づけられています。</p>
 170
 171 <p>公開鍵は、キーサーバーというオンラインディレクトリーに保存されていて、誰でも取り出すことができます。この点で普通の金物の鍵とはだいぶ違います。あなたに暗号メールを送ろうとする人は、まず公開鍵をダウンロードし、それとGnuPGを使ってあなたへの電子メールを暗号化し、それから送信します。そういう意味でキーサーバーは電話帳のようなものだと思っていただいてよいでしょう。あなたへ暗号化メールを送ろうとする人は、電話番号を調べる代わりにあなたの公開鍵を調べるわけです。</p>
 172
 173 <p>もう片方の秘密鍵は金物の鍵に近い働きをするので、自分のコンピューターにしっかり保存しておくべきものです。GnuPGと自分だけの秘密鍵を使って、送られてきた暗号化メールを解読できます。</p>
 174                                 </div><!-- End .section-intro -->
 175
 176                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 177                                 <div id="step-2a" class="step">
 178                                         <div class="sidebar">
 179                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>
 180                                         </div><!-- /.sidebar -->
 181                                         <div class="main">
 182                                                 <h3><em>2.A</em> 自分専用のキーペアを作る</h3>
 183                                                 <p>電子メールプログラムのメニューでOpenPGP&rarr;設定ウィザードを選択してください。ウィザードの始めの方のウィンドウに現れる説明は読まなくてもいいですが、後のウィンドウの説明は重要です。</p>
 184                                                 <p>2番目の「サインする」または「署名する」というウィンドウでは、「いいえ、むしろ宛先別のルールによって署名が必要なメールを作成する」を選択してください。</p>
 185                                                 <p>「キーを作る」という名前のウィンドウになるまでは既定（デフォルト）の設定を選んでください。</p>
 186                                                 <p>「キーを作る」という名前のウィンドウでは、なるべく強いパスワードを入力してください。つまり、長さが12文字以上で、数字や句読点や大文字・小文字のどれもが1個以上は使われるのがよいパスワードです。パスワードは忘れないでください。ここでの努力がみんな無駄になってしまいますから。</p>
 187                                         <p class="notes">次の「キーを作る」というウィンドウでは計算が終わるまでちょっと時間がかかります。計算をしている間は映画を見るとかウェブを見るとか、とにかくパソコンを使うほどキーの生成が速く進みます。</p>
 188                                                 <p>「OpenPGP完成」というウィンドウが現れたら「電子証明書作成」を選択して、パソコン内の確実なフォルダに保存してください。それにはホームに「鍵撤回証明書」といったフォルダを作ってそこへ保存することをおすすめします。電子証明書作成でもっと詳しいことに興味があれば<a href="#section5">５章</a>を参照してください。ウィザードには鍵撤回証明書を外付けのデバイスに保存するように表示が出されますが、その作業はあとにしましょう。</p>
 189
 190                                                 <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 191                                                 <div class="troubleshooting">
 192                                                         <h4>トラブル・シューティング</h4>
 193                                                         <dl>
 194                                                                 <dt>OpenPGPメニューが見つかりません。</dt>
 195                                                                         <dd>メニューが横棒3本で表示されメールプログラムもたくさんあります。OpenPGPが「ツール」というメニューの中に入っていることもあります。</dd>
 196     <dt>ウィザードに「GnuPGが見つからない」と表示されました。</dt>
 197                                          <dd>いつもインストールに使うプログラムを起動して、GnuPGを検索して、インストールしてください。インストールしたらOpenPGP&rarr;設定ウィザードを選択して、Enigmailの設定ウィザードを再起動してください。</dd>
 198
 199                                                                 <dt class="feedback">問題が解決しませんでしたか？>
 200                                                                                 <dd class="feedback"><a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">フィードバックのページ</a>で知らせてください。</dd>
 201                                                         </dl>
 202                                                 </div><!-- /.troubleshooting -->
 203                                         </div><!-- End .main -->
 204                                 </div><!-- End #step-2a .step  -->
 205
 206                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 207                                 <div id="step-2b" class="step">
 208                                         <div class="main">
 209                                                 <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
 210                                                 <p>In your email program's menu, select OpenPGP &rarr; Key Management.</p>
 211 <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
 212 <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>
 213                                                 <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 214                                                 <div class="troubleshooting">
 215                                                         <h4>Troubleshooting</h4>
 216                                                         <dl>
 217                                                                 <dt>The progress bar never finishes</dt>
 218                                                                                 <dd>Close the upload popup, make sure you are connected to the Internet, and try again. If that doesn't work, try again, selecting a different keyserver.</dd>
 219 <dt>My key doesnt appear in the list</dt>
 220                                                                                 <dd>Try checking Show Default Keys.</dd>
 221
 222                                                                 <dt class="feedback">Don't see a solution to your problem?</dt>
 223                                                                         <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
 224
 225                                                         </dl>
 226                                                 </div><!-- /.troubleshooting -->
 227                                         </div><!-- End .main -->
 228                                 </div><!-- End #step-2a .step  -->
 229                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 230                                 <div id="terminology" class="step">
 231                                         <div class="main">
 232                                                 <h3>GnuPG, OpenPGP, what?</h3>
 233                                                 <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>
 234                                         </div><!-- End .main -->
 235                                 </div><!-- End #terminology.step-->
 236
 237
 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, unique 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
 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 9), then select ok. Select ok in the next pop-up.</p>
 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, forming 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
 335 <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>
 336
 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 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 whom are trying to communicate to verify which one to use.</p>
 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>
 362                                                 </div><!-- End #pgp-pathfinder -->
 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. 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 to let people know that you are no longer using that keypair.</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>
 440                                         </div><!-- End .main
 441                                 </div> End #step-5d .step-->
 442
 443
 444                         </div>
 445                 </section><!-- End #section5 -->
 446
 447
 448
 449 <!-- ~~~~~~~~~ Section 6: Next steps  ~~~~~~~~~ -->
 450                 <section class="row" id="section6">
 451                         <div id="step-click_here" class="step">
 452                                         <div class="main">
 453                                           <h2><a href="next_steps.html">Click here when you're done</a></h2>
 454
 455                                         </div><!-- End .main -->
 456                                 </div><!-- End #step-click_here .step-->
 457
 458                 </section><!-- End #section6 -->
 459
 460 <!-- ~~~~~~~~~ FAQ  ~~~~~~~~~ -->
 461 <!-- When un-commenting this section go to main.css and search
 462                 for /* Guide Sections Background */ then add #faq to the desired color
 463
 464                 <section class="row" id="faq">
 465                         <div>
 466                                 <div class="sidebar">
 467                                         <h2>FAQ</h2>
 468                                 </div>
 469
 470                                 <div class="main">
 471                                         <dl>
 472                                                 <dt>My key expired</dt>
 473                                                         <dd>Answer coming soon.</dd>
 474
 475                                                 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
 476                                                         <dd>Answer coming soon.</dd>
 477
 478                                                 <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>
 479                                                         <dd>Answer coming soon.</dd>
 480                                         </dl>
 481                                 </div>
 482                         </div>
 483                 </section> --><!-- End #faq -->
 484
 485 <!-- ~~~~~~~~~ Footer  ~~~~~~~~~ -->
 486                 <footer class="row" id="footer">
 487                         <div>
 488                                 <div id="copyright">
 489                                         <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>
 490                                         <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>
 491                                         <p><em>Version 2.0. <!--LANGUAGE translation by NAME, NAME and NAME.--> <!--Source code of Edward reply bot by PROGRAMMERNAME, available under the GNU General Public License.--></em></p>
 492 <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>
 493                                         <p>Download the source package for <a href="emailselfdefense_source.zip">this guide</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>
 494                                         <p>
 495                                           <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
 496                                              rel="jslicense">
 497                                             JavaScript license information
 498                                           </a>
 499                                         </p>
 500                                 </div><!-- /#copyright -->
 501                                 <p class="credits">
 502                                         Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0n/img/jplusplus.png" alt="Journalism++" /></a>
 503                                 </p><!-- /.credits -->
 504                         </div>
 505                 </footer><!-- End #footer -->
 506
 507                 <script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
 508                 <script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
 509
 510                 <!-- Piwik -->
 511                 <script type="text/javascript">
 512                  /*
 513                  @licstart The following is the entire license notice for the
 514                     JavaScript code in this page.
 515
 516                  Copyright 2014 Matthieu Aubry
 517
 518                   This program is free software: you can redistribute it and/or modify
 519                  it under the terms of the GNU General Public License as published by
 520                  the Free Software Foundation, either version 3 of the License, or
 521                  (at your option) any later version.
 522
 523                   This program is distributed in the hope that it will be useful,
 524                  but WITHOUT ANY WARRANTY; without even the implied warranty of
 525                  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 526                  GNU General Public License for more details.
 527
 528                   You should have received a copy of the GNU General Public License
 529                  along with this program.  If not, see http://www.gnu.org/licenses/.
 530
 531                   @licend The above is the entire license notice
 532                      for the JavaScript code in this page.
 533                  */
 534                  var _paq = _paq || [];
 535                  _paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
 536                  _paq.push(["setCookieDomain", "*.www.fsf.org"]);
 537                  _paq.push(["setDomains", ["*.www.fsf.org","*.www.fsf.org"]]);
 538                  _paq.push(["trackPageView"]);
 539                  _paq.push(["enableLinkTracking"]);
 540
 541                  (function() {
 542                    var u=(("https:" == document.location.protocol) ? "https" : "http") + "://piwik.fsf.org/";
 543                    _paq.push(["setTrackerUrl", u+"piwik.php"]);
 544                    _paq.push(["setSiteId", "5"]);
 545                    var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
 546                    g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
 547                  })();
 548                 </script>
 549                 <!-- End Piwik Code -->
 550         </body>
 551 </html>