-<!DOCTYPE html>\r
-<html lang="zh-Hans">\r
-<head>\r
- <meta http-equiv="content-type" content="text/html; charset=utf-8" />\r
-\r
- <title>电子邮件加密傻瓜指南</title>\r
- <meta name="keywords" content="GnuPG, GPG, openpgp, 监控, 隐私, 电子邮件, Enigmail" />\r
- <meta name="description" content="电子邮件监控侵犯了我们的基本权利，并危及了言论自由。本指南将在40分钟里教会你如何通过GnuPG加密邮件。 " />\r
-\r
- <meta name="viewport" content="width=device-width, initial-scale=1" />\r
- <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />\r
- <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />\r
-\r
-</head>\r
-<body>\r
-\r
-<h3 class="wip">Translation in Progress</h3>\r
-<p class="wip">The <a href="/esd-zh-hans.po">PO file</a> is where work is being done. Please help us if you can. Thanks!</p>\r
-\r
- <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->\r
-\r
- <header class="row" id="header">\r
- <div>\r
- <h1>电子邮件加密傻瓜指南</h1>\r
-\r
- <!-- Language list for browsers that do not have JS enabled -->\r
- <ul id="languages" class="os">\r
-<li><a href="/en">English - v4.0</a></li>\r
-<li><a href="/ar">العربية <span class="tip">tip</span></a></li>\r
-<li><a href="/cs">Čeština - v4.0</a></li>\r
-<li><a href="/de">Deutsch - v3.0</a></li>\r
-<li><a href="/el">ελληνικά - v3.0</a></li>\r
-<li><a href="/es">español - v4.0</a></li>\r
-<li><a href="/fa">فارسی - v4.0</a></li>\r
-<li><a href="/fr">français - v4.0</a></li>\r
-<li><a href="/it">italiano - v3.0</a></li>\r
-<li><a href="/ja">日本語 - v4.0</a></li>\r
-<li><a href="/ko">한국어 <span class="tip">tip</span></a></li>\r
-<li><a href="/ml">മലയാളം <span class="tip">tip</span></a></li>\r
-<li><a href="/pt-br">português do Brasil - v3.0</a></li>\r
-<li><a href="/ro">română - v3.0</a></li>\r
-<li><a href="/ru">русский - v4.0</a></li>\r
-<li><a href="/sq">Shqip - v4.0</a></li>\r
-<li><a href="/sv">svenska - v4.0</a></li>\r
-<li><a href="/tr">Türkçe - v4.0</a></li>\r
-<li><a class="current" href="/zh-hans">简体中文 <span class="tip">tip</span></a></li>\r
-<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide"><strong><span style="color: #2F5FAA;">帮助翻译</span></strong></a></li>\r
- </ul>\r
-\r
- <ul id="menu" class="os">\r
- <li class="spacer">\r
- <a href="index.html" class="current">GNU/Linux</a>\r
- </li>\r
- <li>\r
- <a href="mac.html">Mac OS</a>\r
- </li>\r
- <li>\r
- <a href="windows.html">Windows</a>\r
- </li>\r
- <li class="spacer"><a href="workshops.html">研讨会</a></li>\r
- <li class="spacer">\r
- <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">\r
- 分享 \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"\r
- class="share-logo" alt="[GNU Social]" /> \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"\r
- class="share-logo" alt="[Pump.io]" /> \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"\r
- class="share-logo" alt="[Reddit]" /> \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png"\r
- class="share-logo" alt="[Hacker News]" />\r
- </a>\r
- </li>\r
- </ul>\r
-\r
- <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->\r
- <div id="fsf-intro">\r
- <h3>\r
- <a href="http://u.fsf.org/ys">\r
- <img alt="Free Software Foundation"\r
- src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />\r
- </a>\r
- </h3>\r
- <div class="fsf-emphasis">\r
- <p>\r
- 我们为计算机用户的权利而战，并促进自由软件的开发，对抗大规模监控对我们至关重要。\r
- </p>\r
- <p>\r
- <strong>\r
- 请捐款以支持电子邮件加密指南。我们会一直改进它，使其充实，for the benefit of people around the world taking the first step towards protecting their privacy.\r
- </strong>\r
- </p>\r
- </div>\r
-\r
- <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a> </p>\r
-\r
- </div><!-- End #fsf-intro -->\r
-\r
- <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->\r
- <div class="intro">\r
- <p>\r
- <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png" alt="View & share our infographic →" /></a>大规模监控侵犯了我们的基本权利，并危及了言论自由。本指南将会教授你一个基本的监控自我保护技巧：加密电子邮件。一旦你学会了，你将能够收发其他人无法阅读的电子邮件，包括那些拦截你邮件的监控代理或窃贼。你需要的是一台带网络连接的计算机，一个电子邮箱账号，和大约四十分钟时间。</p>\r
-\r
- <p>即使你没有什么见不得人的事情，通过加密可以保护通信对方的隐私，并使大规模监控变得困难。如果你确实有重要的东西需要隐藏，那么你并不孤独；告密者们在揭发人权侵犯、腐败以及其他犯罪问题时，也是使用同样的工具保护他们身份的。</p>\r
-\r
- <p>除了使用加密技术，我们还需要坚持不懈地与监控作政治斗争，以减少政府<a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">对我们的大量数据收集</a>。但重中之重是保护好你自己，使得监控你的通讯尽可能的困难。本指南将帮助你做到。它是为初学者设计的，但如果你已经掌握了 GnuPG 的基本知识，或你是一位资深自由软件用户，你会喜欢进阶提示与<a href="workshops.html">加密探讨会指南</a>。</p>\r
-\r
- </div><!-- End .intro -->\r
-\r
- </div>\r
- </header><!-- End #header -->\r
-\r
- <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->\r
- <section class="row" id="section1">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#1</em> 获取部件</h2>\r
- <p class="notes">本指南需要安装<a href="https://www.gnu.org/philosophy/free-sw.html">自由许可的</a>软件；它是完全透明的，任何人都可以复制它，并生成自己的版本。这使得它比专有软件（比如 Windows）更难受到监控。你可以在 <a href="https://u.fsf.org/ys">fsf.org</a> 上了解更多关于自由软件的信息。</p>\r
-\r
- <p>大多数 GNU/Linux 操作系统自带 GnuPG，所以你不必下载它。在配置 GnuPG 前，你需要安装 IceDove 电子邮件客户端。大多数 GNU/Linux 发行版已经安装好 IceDove 了，它可能是以别名 Thunderbird 出现在你的计算机中。电子邮件程序是另一种访问邮箱账号的途径（你也可以像 Gmail 那样通过浏览器访问），但它提供了更多的功能。</p>\r
- <p>如果你已经安装好了电子邮件程序，请跳至 <a href="#step-1b">Step 1.b</a>。</p>\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-1a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 1.a</em> 设置邮箱账号</h3>\r
- <p>打开你的邮件程序，按照向导程序的提示逐步设置好你的邮箱账号。</p>\r
- <p>在设置你的账号时，留意服务器右侧的 SSL, TLS 或 STARTTLS 字样。如果你没有看到他们，你仍将有能力使用加密，但这意味着运行邮件系统的人以低于行业标准的规范保护着你的安全与隐私。我们建议你，向他们发送一份友好的邮件，要求他们为邮件服务器启用 SSL, TLS 或 STARTTLS。他们会知道你说的是什么，如果你不是系统安全的专家，这是一个值得的要求。</p>\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>The wizard doesn't launch</dt>\r
- <dd>You can launch the wizard yourself, but the menu option for doing so is named differently in each email program. The button to launch it will be in the program's main menu, under "New" or something similar, titled something like "Add account" or "New/Existing email account."</dd>\r
- <dt>The wizard can't find my account or isn't downloading my mail</dt>\r
- <dd>Before searching the Web, we recommend you start by asking other people who use your email system, to figure out the correct settings.</dd>\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step1-a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-1b" class="step">\r
- <div class="sidebar">\r
- <ul class="images">\r
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>\r
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png" alt="Step 1.B: Search Add-ons" /></li>\r
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png" alt="Step 1.B: Install Add-ons" /></li>\r
- </ul>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 1.b</em> 安装 ENIGMAIL 插件</h3>\r
- <p>在邮件程序的菜单栏里，选择“附加组件”（Add-ons，它可能在工具选项里）。确认选上了左侧的“扩展”（Extensions）。看到了 Enigmail 吗？如果是，请跳过此步。</p>\r
- <p>如果没有，在右上方的搜索框里搜索“Enigmail”。你可以在这里获取到它。安装完成后重启邮件客户端。</p>\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
-\r
- <dt>I can't find the menu.</dt>\r
- <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars.</dd>\r
- <dt>My email looks weird</dt>\r
- <dd>Enigmail doesn't tend to play nice with HTML, which is used to format emails, so it may disable your HTML formatting automatically. To send an HTML-formatted email without encryption or a signature, hold down the Shift key when you select compose. You can then write an email as if Enigmail wasn't there.</dd>\r
-\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
- </div><!-- End #step-1b .step -->\r
-\r
- </div>\r
- </section><!-- End #section1 -->\r
-\r
- <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->\r
- <section class="row" id="section2">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#2</em> 生成密钥</h2>\r
- <p>要使用 GnuPG 体系，你将会用到一把公钥（public key）和一把私钥（private key），他们合称为密钥对（keypair）。每一把都是随机生成的一长串数字和字母的值，它是独一无二的。你的公钥和私钥由一种特殊的数学函数联系在一起。</p>\r
-\r
- <p>你的公钥不太像现实中的钥匙，它公开储存在被称之为密钥服务器（keyserver）的在线目录上。人们可以下载使用它，借助 GnuPG，人们向你发送加密邮件。你可以把密钥服务器想象成一本电话簿；想要给你发送加密邮件的人能够找到你的公钥。</p>\r
-\r
- <p>你的私钥更像是现实中的钥匙，你需要自行保管它（在你的计算机中）。你可以使用 GnuPG 和你的私钥来解密他人发给你的加密邮件。<span style="font-weight: bold;">无论如何，你都不应该改向他人分享你的私钥。</span></p>\r
- <p>除了加密和解密，你可以使用这些密钥对消息进行签名，并检查其他人签名的真实性。我们将在下一节里详细探讨它。</p>\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-2a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 2.a</em> 生成密钥对</h3>\r
- <p>Enigmail 安装向导可能会自动运行。如果没有，在你的邮件程序你选择 Enigmail → Setup Wizard。如果你不愿意，你不必去阅读弹出窗口中的文字，但读一读总归是好的。点击下一步而不对默认选项作修改，但除了下列情况以外：</p>\r
- <ul>\r
- <li>在“加密”（Encryption）界面，选中“默认加密所有我的消息，因为隐私对我很重要”（Encrypt all of my messages by default, because privacy is critical to me）。</li>\r
- <li>在“签名”（Signing）界面，选中“默认不对我的消息签名”（Don't sign my messages by default）。</li>\r
- <li>在“密钥选择”（Key Selection）界面，选择“我想为数字签名和加密邮件创建新密钥对”（I want to create a new key pair for signing and encrypting my email）。</li>\r
- <li>在“创建密钥”（Create Key）界面。取一个强壮的密码吧！你可以自行取密码，也可以使用 Diceware 模式。自己取密码虽然快速，但不安全。使用 Diceware 需要更长时间 and requires dice,但能生成攻击者难以辨识出的密码。要使用它，请阅读 Micah Lee 写的<a href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">这篇文章</a>的 Make a secure passphrase with Diceware 一节。</li>\r
- </ul>\r
-\r
- <p>如果你喜欢自己取密码，想一个你记得起的至少十二字符长的东西，至少包含一个小写和大写字母，和一个数字或标点符号。永远不要使用你其他地方使用过的密码。不用使用任何可辨识的模式，诸如生日、电话号码、宠物名字、歌词或书中的引言。</p>\r
-\r
- <p class="notes">在“生成密钥”（Key Creation）界面，程序需要花费小会儿完成下一步。等待时，你可以在计算机上做一些其他事情，比如看电影或浏览网页。此时你计算机使用的越频繁，密钥生成的速度越快。</p>\r
- <p><span style="font-weight: bold;">当 "Key Generation Completed" （密钥已生成）窗口弹出，选中 Generate Certificate （生成证书）并选择把它储存在计算机上安全的地方（我们推荐新建一个名为 Revocation Certificate [吊销证书]的文件夹在你的家目录下，并把它保存在那里）。这是本指南重要的一步，你将会在 <a href="#section5">Section 5</a> 了解到更多信息。</span></p>\r
-\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>I can't find the Enigmail menu.</dt>\r
- <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars. Enigmail may be inside a section called Tools.</dd>\r
-\r
- <dt>The wizard says that it cannot find GnuPG.</dt>\r
- <dd>Open whatever program you usually use for installing software, and search for GnuPG, then install it. Then restart the Enigmail setup wizard by going to Enigmail → Setup Wizard.</dd>\r
-\r
- <dt>My email looks weird</dt>\r
- <dd>Enigmail doesn't tend to play nice with HTML, which is used to format emails, so it may disable your HTML formatting automatically. To send an HTML-formatted email without encryption or a signature, hold down the Shift key when you select compose. You can then write an email as if Enigmail wasn't there.</dd>\r
-\r
- <dt>More resources</dt>\r
- <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Key_Management#Generating_your_own_key_pair">Enigmail's wiki instructions for key generation</a>.</dd>\r
-\r
-\r
-\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
-\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
-\r
-\r
- <dt>Command line key generation</dt>\r
- <dd>If you prefer using the command line for a higher degree of control, you can follow the documentation from <a href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy Handbook</a>. Make sure you stick with "RSA and RSA" (the default), because it's newer and more secure than the algorithms the documentation recommends. Also make sure your key is at least 2048 bits, or 4096 if you want to be extra secure.</dd>\r
-\r
- <dt>Advanced key pairs</dt>\r
- <dd>When GnuPG creates a new keypair, it compartmentalizes the encryption function from the signing function through <a href="https://wiki.debian.org/Subkeys">subkeys</a>. If you use subkeys carefully, you can keep your GnuPG identity much more secure and recover from a compromised key much more quickly. <a href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal</a> and <a href="http://keyring.debian.org/creating-key.html">the Debian wiki</a> provide good guides for setting up a secure subkey configuration.</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
- </div><!-- End #step-2a .step -->\r
-\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-2b" class="step">\r
- <div class="main">\r
- <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>\r
- <p>In your email program's menu, select Enigmail → Key Management.</p>\r
- <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>\r
- <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>\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>The progress bar never finishes</dt>\r
- <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>\r
- <dt>My key doesn't appear in the list</dt>\r
- <dd>Try checking "Display All Keys by Default."</dd>\r
- <dt>More documentation</dt>\r
- <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://www.enigmail.net/documentation/quickstart-ch2.php#id2533620">Enigmail's documentation</a>.</dd>\r
-\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
-\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
- <dt>Uploading a key from the command line</dt>\r
- <dd>You can also upload your keys to a keyserver through the <a href="https://www.gnupg.org/gph/en/manual/x457.html">command line</a>. <a href="https://sks-keyservers.net/overview-of-pools.php">The sks Web site</a> maintains a list of highly interconnected keyservers. You can also <a href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export your key</a> as a file on your computer.</dd>\r
-\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
- </div><!-- End #step-2b .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="terminology" class="step">\r
- <div class="main">\r
- <h3>GnuPG, OpenPGP, what?</h3>\r
- <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG) is the program that implements the standard. Enigmail is a plug-in program for your email program that provides an interface for GnuPG.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #terminology.step-->\r
-\r
-\r
- </div>\r
- </section><!-- End #section2 -->\r
-\r
- <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->\r
- <section class="row" id="section3">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#3</em> Try it out!</h2>\r
- <p>Now you'll try a test correspondence with a computer program named Edward, who knows how to use encryption. Except where noted, these are the same steps you'd follow when corresponding with a real, live person.</p>\r
-\r
- <!-- <p>NOTE: Edward is currently having some technical difficulties, so he may take a long time to respond, or not respond at all. We're sorry about this and we're working hard to fix it. Your key will still work even without testing with Edward.</p> -->\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png" alt="Try it out." /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 3.a</em> Send Edward your public key</h3>\r
- <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 Enigmail → 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>\r
-\r
- <p>Address the message to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Put at least one word (whatever you want) in the subject and body of the email. Don't send yet.</p>\r
-\r
- <p>The lock icon in the top left should be yellow, meaning encryption is\r
- turned on. We want this first special message to be unencrypted, so\r
- click the icon once to turn it off. The lock should become grey, with a\r
- blue dot on it (to alert you that the setting has been changed from the\r
- default). Once encryption is off, hit Send.</p>\r
-\r
- <p class="notes">It may take two or three minutes for Edward 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 he'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>\r
-\r
- <p>When you open Edward's reply, GnuPG may prompt you for your password before using your private key to decrypt it.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3b" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.b</em> Send a test encrypted email</h3>\r
- <p>Write a new email in your email program, addressed to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Make the subject "Encryption test" or something similar and write something in the body.</p>\r
- <p>The lock icon in the top left of the window should be yellow, meaning encryption is on. This will be your default from now on.</p>\r
- <p class="notes">Next to the lock, you'll notice an icon of a pencil. We'll get to this in a moment.</p>\r
- <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>\r
-\r
- <p>To encrypt an email to Edward, you need his public key, so now you'll have Enigmail download it from a keyserver. Click Download Missing Keys and use the default in the pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key ID starting with C), then select ok. Select ok in the next pop-up.</p>\r
-\r
- <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Check the box in front of Edward's key and click Send.</p>\r
-\r
- <p class="notes">Since you encrypted this email with Edward's public key, Edward's private key is required to decrypt it. Edward is the only one with his private key, so no one except him can decrypt it.</p>\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>Enigmail can't find Edward's key</dt>\r
- <dd>Close the pop-ups that have appeared since you clicked Send. 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>\r
- <dt>Unscrambled messages in the Sent folder</dt>\r
- <dd>Even though you can't decrypt messages encrypted to someone else's key, your email program will automatically save a copy encrypted to your public key, which you'll be able to view from the Sent folder like a normal email. This is normal, and it doesn't mean that your email was not sent encrypted.</dd>\r
- <dt>More resources</dt>\r
- <dd>If you're still having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Signature_and_Encryption#Encrypting_a_message">Enigmail's wiki</a>.</dd>\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
- <dt>Encrypt messages from the command line</dt>\r
- <dd>You can also encrypt and decrypt messages and files from the <a href="https://www.gnupg.org/gph/en/manual/x110.html">command line</a>, if that's your preference. The option --armor makes the encrypted output appear in the regular character set.</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3b .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-headers_unencrypted" class="step">\r
- <div class="main">\r
- <h3><em>Important:</em> Security tips</h3>\r
- <p>Even if you encrypt 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 a surveillance system can still figure out who you're communicating with. Also, surveillance agents will know that you're using GnuPG, even if they can't figure out what you're saying. When you send attachments, Enigmail will give you the choice to encrypt them or not, independent of the actual email.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-headers_unencrypted .step-->\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3c" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.c</em> Receive a response</h3>\r
- <p>When Edward receives your email, he will use his private key to decrypt it, then use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to encrypt his reply to you.</p>\r
-\r
- <p class="notes">It may take two or three minutes for Edward 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>\r
- <p>When you receive Edward'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>\r
- <p>Notice the bar that Enigmail shows you above the message, with information about the status of Edward's key.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3c .step -->\r
-\r
-\r
- <div id="step-3d" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.d</em> Send a test signed email</h3>\r
- <p>GnuPG includes a way for you to sign messages and files, verifying that they came from you and that they weren't tampered with along the way. These signatures are stronger than their pen-and-paper cousins -- they're impossible to forge, because they're impossible to create without your private key (another reason to keep your private key safe).</p>\r
-\r
- <p>You can sign messages to anyone, so it's a great way to make people aware that you use GnuPG and that they can communicate with you securely. If they don't have GnuPG, they will be able to read your message and see your signature. If they do have GnuPG, they'll also be able to verify that your signature is authentic.</p>\r
-\r
- <p>To sign an email to Edward, compose any message to him and click the pencil icon next to the lock icon so that it turns gold. If you sign a message, GnuPG may ask you for your password before it sends the message, because it needs to unlock your private key for signing.</p>\r
-\r
- <p>With the lock and pencil icons, you can choose whether each message will be encrypted, signed, both, or neither.</p>\r
- </div>\r
- </div>\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3e" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.e</em> Receive a response</h3>\r
- <p>When Edward receives your email, he will use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to verify that your signature is authentic and the message you sent has not been tampered with.</p>\r
-\r
- <p class="notes">It may take two or three minutes for Edward 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>\r
-\r
- <p>Edward's reply will arrive encrypted, because he prefers to use encryption whenever possible. If everything goes according to plan, it should say "Your signature was verified." If your test signed email was also encrypted, he will mention that first.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3c .step -->\r
- </div>\r
- </section>\r
-\r
-\r
- <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->\r
- <section class="row" id="section4">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#4</em> Learn the Web of Trust</h2>\r
- <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>\r
-\r
- <p>When you sign someone's key, you are publicly saying that you've verified that it belongs to them and not someone else.</p>\r
-\r
- <p>Signing keys and signing messages use the same type of mathematical operation, but they carry very different implications. It's a good practice to generally sign your email, but if you casually sign people's keys, you may accidently end up vouching for the identity of an imposter.</p>\r
-\r
- <p>People who use your public key can see who has signed it. Once you've used GnuPG for a long time, your key may have hundreds of signatures. You can consider a key to be more trustworthy if it has many signatures from people that you trust. The Web of Trust is a constellation of GnuPG users, connected to each other by chains of trust expressed through signatures.</p>\r
-\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-4a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 4.a</em> Sign a key</h3>\r
- <p>In your email program's menu, go to Enigmail → Key Management.</p>\r
- <p>Right click on Edward's public key and select Sign Key from the context menu.</p>\r
- <p>In the window that pops up, select "I will not answer" and click ok.</p>\r
- <p>Now you should be back at the Key Management menu. Select Keyserver → Upload Public Keys and hit ok.</p>\r
- <p class="notes">You've just effectively said "I trust that Edward's public key actually belongs to Edward." This doesn't mean much because Edward isn't a real person, but it's good practice.</p>\r
-\r
-\r
- <!--<div id="pgp-pathfinder">\r
- <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">\r
- <p><strong>From:</strong> <input type="text" placeholder="xD41A008" name="FROM"></p>\r
- <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>\r
- <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>\r
- </form>\r
- </div>End #pgp-pathfinder -->\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-4a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-identify_keys" class="step">\r
- <div class="main">\r
- <h3>Identifying keys: Fingerprints and IDs</h3>\r
- <p>People's public keys are usually identified by their key fingerprint, which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Edward's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to Enigmail → 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 people can double-check that they have the correct public key when they download yours from a keyserver.</p>\r
-\r
- <p class="notes">You may also see public keys referred to by their key ID, which is simply the last eight digits of the fingerprint, like C09A61E8 for Edward. 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 you are trying to communicate to verify which one to use.</p>\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-sign_real_keys .step-->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="check-ids-before-signing" class="step">\r
- <div class="main">\r
- <h3><em>Important:</em> What to consider when signing keys</h3>\r
- <p>Before signing a person's key, you need to be confident that it actually belongs to them, and that they are who they say they are. Ideally, this confidence comes from having interactions and conversations with them over time, and witnessing interactions between them and others. Whenever signing a key, ask to see the full public key fingerprint, and not just the shorter key ID. If you feel it's important to sign the key of someone you've just met, also ask them to show you their government identification, and make sure the name on the ID matches the name on the public key. 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?"\r
-</p>\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
- <dt>Master the Web of Trust</dt>\r
- <dd>Unfortunately, trust does not spread between users the way <a href="http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people think</a>. One of best ways to strengthen the GnuPG community is to deeply <a href="https://www.gnupg.org/gph/en/manual/x334.html">understand</a> the Web of Trust and to carefully sign as many people's keys as circumstances permit.</dd>\r
- <dt>Set ownertrust</dt>\r
- <dd>If you trust someone enough to validate other people's keys, you can assign them an ownertrust level through Enigmails's key management window. Right click on the other person's key, go to the "Select Owner Trust" menu option, select the trustlevel and click OK. Only do this once you feel you have a deep understanding of the Web of Trust.</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
-\r
- </div><!-- End #step-sign_real_keys .step-->\r
-\r
-\r
- </div>\r
- </section><!-- End #section4 -->\r
-\r
- <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->\r
- <section id="section5" class="row">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#5</em> Use it well</h2>\r
- <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>\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-5a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well (1)" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3>When should I encrypt? When should I sign?</h3>\r
-\r
- <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. 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>\r
- <p>Unless you don't want to reveal your own identity (which requires other protective measures), there's no reason not to sign every message, whether or not you are encrypting. In addition to allowing those with GnuPG to verify that the message came from you, signing is a non-intrusive way to remind everyone that you use GnuPG and show support for secure communication. If you often send signed messages to people that aren't familiar with GnuPG, it's nice to also include a link to this guide in your standard email signature (the text kind, not the cryptographic kind).</p>\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-5a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-5b" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well (2)" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3>Be wary of invalid keys</h3>\r
- <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>\r
- <p>In your email program, go back to the first encrypted email that Edward sent you. Because Edward encrypted it with your public key, it will have a message from Enigmail at the top, which most likely says "Enigmail: Part of this message encrypted."</p>\r
- <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>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-5b .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-5c" class="step">\r
- <div class="main">\r
- <h3>Copy your revocation certificate to somewhere safe</h3>\r
- <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, not on a device you carry with you regularly.</p>\r
- <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>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-5c .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-lost_key" class="step">\r
- <div class="main">\r
- <h3><em>Important:</em> act swiftly if someone gets your private key</h3>\r
- <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 or forge your signature. This guide doesn't cover how to revoke a key, but you can follow these <a href="https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions</a>. After you're done revoking, make a new key and send an email to everyone with whom you usually use your key to make sure they know, including a copy of your new key.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-lost_key .step-->\r
-\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <!---<div id="transfer-key" class="step">\r
- <div class="main">\r
- <h3>Transferring you key</h3>\r
- <p>You can use Enigmail's <a href="https://www.enigmail.net/documentation/keyman.php">key management window</a> to import and export keys. If you want to be able to read your encrypted email on a different computer, you will need to export your secret key from here. Be warned, if you transfer the key without <a href="https://help.ubuntu.com/community/EncryptedFilesystemsOnRemovableStorage">encrypting</a> the drive it's on the transfer will be dramatically less secure.</p>\r
- </div>--><!-- End .main -->\r
- </div><!-- End #step-lost_key .step-->\r
-\r
-\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="webmail-and-GnuPG" class="step">\r
- <div class="main">\r
- <h3>Webmail and GnuPG</h3>\r
- <p>When you use a web browser to access your email, you're using webmail, an email program stored on a distant website. Unlike webmail, your desktop email program runs on your own computer. Although webmail can't decrypt encrypted email, it will still display it in its encrypted form. If you primarily use webmail, you'll know to open your email client when you receive a scrambled email.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #webmail-and-GnuPG .step-->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~\r
- <div id="step-5d" class="step">\r
- <div class="main">\r
- <h3>Make your public key part of your online identity</h3>\r
- <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>\r
-\r
- <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>\r
- </div>--><!-- End .main\r
-</div> End #step-5d .step-->\r
-\r
-</section><!-- End #section5 -->\r
-\r
-\r
-\r
-<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->\r
-<section class="row" id="section6">\r
- <div id="step-click_here" class="step">\r
- <div class="main">\r
- <h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2>\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-click_here .step-->\r
-\r
-</section><!-- End #section6 -->\r
-\r
-<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->\r
-<!-- When un-commenting this section go to main.css and search\r
-for /* Guide Sections Background */ then add #faq to the desired color\r
-\r
-<section class="row" id="faq">\r
-<div>\r
-<div class="sidebar">\r
-<h2>FAQ</h2>\r
-</div>\r
-\r
-<div class="main">\r
-<dl>\r
-<dt>My key expired</dt>\r
-<dd>Answer coming soon.</dd>\r
-\r
-<dt>Who can read encrypted messages? Who can read signed ones?</dt>\r
-<dd>Answer coming soon.</dd>\r
-\r
-<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>\r
-<dd>Answer coming soon.</dd>\r
-</dl>\r
-</div>\r
-</div>\r
-</section> --><!-- End #faq -->\r
-\r
-<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->\r
-<footer class="row" id="footer">\r
- <div>\r
- <div id="copyright">\r
- <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>\r
- <p>Copyright © 2014-2016 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please support our work by <a href="https://u.fsf.org/yr">joining us as an associate member.</a></p>\r
-\r
- <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>. Download the <a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">source code of Edward reply bot</a> by Andrew Engelbrecht <sudoman@ninthfloor.org> and Josh Drake <zamnedix@gnu.org>, available under the GNU Affero General Public License. <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>\r
-\r
- <p>Fonts used in the guide & 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ś, <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a> by Florian Cramer.</p>\r
-\r
- <p>Download the <a href="emailselfdefense_source.zip">source package</a> for this guide, including fonts, image source files and the text of Edward's messages.</p>\r
-\r
- <p>This site uses the Weblabels standard for labeling <a href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" rel="jslicense">source code and license information</a>.</p>\r
- </div><!-- /#copyright -->\r
- <p class="credits">\r
- Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" alt="Journalism++" /></a>\r
- </p><!-- /.credits -->\r
- </div>\r
-</footer><!-- End #footer -->\r
-\r
-<script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>\r
-<script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>\r
-\r
-<!-- Piwik -->\r
-<script type="text/javascript" >\r
-// @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later\r
-var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");\r
-document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));\r
-try {\r
- var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13);\r
- piwikTracker.trackPageView();\r
- piwikTracker.enableLinkTracking();\r
-} catch( err ) {}\r
-// @license-end\r
-</script><noscript><p><img src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0" alt="" /></p></noscript>\r
-<!-- End Piwik Tracking Code -->\r
-\r
-\r
-\r
-</body>\r
-</html>\r
+<!DOCTYPE html>
+<html lang="zh-Hans">
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=utf-8" />
+
+ <title>电子邮件加密傻瓜指南</title>
+ <meta name="keywords" content="GnuPG, GPG, openpgp, 监控, 隐私, 电子邮件, Enigmail" />
+ <meta name="description" content="电子邮件监控侵犯了我们的基本权利，并危及了言论自由。本指南将在40分钟里教会你如何通过GnuPG加密邮件。 " />
+
+ <meta name="viewport" content="width=device-width, initial-scale=1" />
+ <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />
+ <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
+
+</head>
+<body>
+
+<h3 class="wip">Translation in Progress</h3>
+<p class="wip">The <a href="/esd-zh-hans.po">PO file</a> is where work is being done. Please help us if you can. Thanks!</p>
+
+ <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
+
+ <header class="row" id="header">
+ <div>
+ <h1>电子邮件加密傻瓜指南</h1>
+
+ <!-- Language list for browsers that do not have JS enabled -->
+ <ul id="languages" class="os">
+<li><a href="/en">English - v4.0</a></li>
+<li><a href="/ar">العربية <span class="tip">tip</span></a></li>
+<li><a href="/cs">Čeština - v4.0</a></li>
+<li><a href="/de">Deutsch - v3.0</a></li>
+<li><a href="/el">ελληνικά - v3.0</a></li>
+<li><a href="/es">español - v4.0</a></li>
+<li><a href="/fa">فارسی - v4.0</a></li>
+<li><a href="/fr">français - v4.0</a></li>
+<li><a href="/it">italiano - v3.0</a></li>
+<li><a href="/ja">日本語 - v4.0</a></li>
+<li><a href="/ko">한국어 <span class="tip">tip</span></a></li>
+<li><a href="/ml">മലയാളം <span class="tip">tip</span></a></li>
+<li><a href="/pt-br">português do Brasil - v3.0</a></li>
+<li><a href="/ro">română - v3.0</a></li>
+<li><a href="/ru">русский - v4.0</a></li>
+<li><a href="/sq">Shqip - v4.0</a></li>
+<li><a href="/sv">svenska - v4.0</a></li>
+<li><a href="/tr">Türkçe - v4.0</a></li>
+<li><a class="current" href="/zh-hans">简体中文 <span class="tip">tip</span></a></li>
+<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide"><strong><span style="color: #2F5FAA;">帮助翻译</span></strong></a></li>
+ </ul>
+
+ <ul id="menu" class="os">
+ <li class="spacer">
+ <a href="index.html" class="current">GNU/Linux</a>
+ </li>
+ <li>
+ <a href="mac.html">Mac OS</a>
+ </li>
+ <li>
+ <a href="windows.html">Windows</a>
+ </li>
+ <li class="spacer"><a href="workshops.html">研讨会</a></li>
+ <li class="spacer">
+ <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">
+ 分享
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"
+ class="share-logo" alt="[GNU Social]" />
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"
+ class="share-logo" alt="[Pump.io]" />
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"
+ class="share-logo" alt="[Reddit]" />
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png"
+ class="share-logo" alt="[Hacker News]" />
+ </a>
+ </li>
+ </ul>
+
+ <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
+ <div id="fsf-intro">
+ <h3>
+ <a href="http://u.fsf.org/ys">
+ <img alt="Free Software Foundation"
+ src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />
+ </a>
+ </h3>
+ <div class="fsf-emphasis">
+ <p>
+ 我们为计算机用户的权利而战，并促进自由软件的开发，对抗大规模监控对我们至关重要。
+ </p>
+ <p>
+ <strong>
+ 请捐款以支持电子邮件加密指南。我们会一直改进它，使其充实，for the benefit of people around the world taking the first step towards protecting their privacy.
+ </strong>
+ </p>
+ </div>
+
+ <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a> </p>
+
+ </div><!-- End #fsf-intro -->
+
+ <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
+ <div class="intro">
+ <p>
+ <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png" alt="View & share our infographic →" /></a>大规模监控侵犯了我们的基本权利，并危及了言论自由。本指南将会教授你一个基本的监控自我保护技巧：加密电子邮件。一旦你学会了，你将能够收发其他人无法阅读的电子邮件，包括那些拦截你邮件的监控代理或窃贼。你需要的是一台带网络连接的计算机，一个电子邮箱账号，和大约四十分钟时间。</p>
+
+ <p>即使你没有什么见不得人的事情，通过加密可以保护通信对方的隐私，并使大规模监控变得困难。如果你确实有重要的东西需要隐藏，那么你并不孤独；告密者们在揭发人权侵犯、腐败以及其他犯罪问题时，也是使用同样的工具保护他们身份的。</p>
+
+ <p>除了使用加密技术，我们还需要坚持不懈地与监控作政治斗争，以减少政府<a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">对我们的大量数据收集</a>。但重中之重是保护好你自己，使得监控你的通讯尽可能的困难。本指南将帮助你做到。它是为初学者设计的，但如果你已经掌握了 GnuPG 的基本知识，或你是一位资深自由软件用户，你会喜欢进阶提示与<a href="workshops.html">加密探讨会指南</a>。</p>
+
+ </div><!-- End .intro -->
+
+ </div>
+ </header><!-- End #header -->
+
+ <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
+ <section class="row" id="section1">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#1</em> 获取部件</h2>
+ <p class="notes">本指南需要安装<a href="https://www.gnu.org/philosophy/free-sw.html">自由许可的</a>软件；它是完全透明的，任何人都可以复制它，并生成自己的版本。这使得它比专有软件（比如 Windows）更难受到监控。你可以在 <a href="https://u.fsf.org/ys">fsf.org</a> 上了解更多关于自由软件的信息。</p>
+
+ <p>大多数 GNU/Linux 操作系统自带 GnuPG，所以你不必下载它。在配置 GnuPG 前，你需要安装 IceDove 电子邮件客户端。大多数 GNU/Linux 发行版已经安装好 IceDove 了，它可能是以别名 Thunderbird 出现在你的计算机中。电子邮件程序是另一种访问邮箱账号的途径（你也可以像 Gmail 那样通过浏览器访问），但它提供了更多的功能。</p>
+ <p>如果你已经安装好了电子邮件程序，请跳至 <a href="#step-1b">Step 1.b</a>。</p>
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-1a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 1.a</em> 设置邮箱账号</h3>
+ <p>打开你的邮件程序，按照向导程序的提示逐步设置好你的邮箱账号。</p>
+ <p>在设置你的账号时，留意服务器右侧的 SSL, TLS 或 STARTTLS 字样。如果你没有看到他们，你仍将有能力使用加密，但这意味着运行邮件系统的人以低于行业标准的规范保护着你的安全与隐私。我们建议你，向他们发送一份友好的邮件，要求他们为邮件服务器启用 SSL, TLS 或 STARTTLS。他们会知道你说的是什么，如果你不是系统安全的专家，这是一个值得的要求。</p>
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>The wizard doesn't launch</dt>
+ <dd>You can launch the wizard yourself, but the menu option for doing so is named differently in each email program. The button to launch it will be in the program's main menu, under "New" or something similar, titled something like "Add account" or "New/Existing email account."</dd>
+ <dt>The wizard can't find my account or isn't downloading my mail</dt>
+ <dd>Before searching the Web, we recommend you start by asking other people who use your email system, to figure out the correct settings.</dd>
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+ </div><!-- End .main -->
+ </div><!-- End #step1-a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-1b" class="step">
+ <div class="sidebar">
+ <ul class="images">
+ <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>
+ <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png" alt="Step 1.B: Search Add-ons" /></li>
+ <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png" alt="Step 1.B: Install Add-ons" /></li>
+ </ul>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 1.b</em> 安装 ENIGMAIL 插件</h3>
+ <p>在邮件程序的菜单栏里，选择“附加组件”（Add-ons，它可能在工具选项里）。确认选上了左侧的“扩展”（Extensions）。看到了 Enigmail 吗？如果是，请跳过此步。</p>
+ <p>如果没有，在右上方的搜索框里搜索“Enigmail”。你可以在这里获取到它。安装完成后重启邮件客户端。</p>
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+
+ <dt>I can't find the menu.</dt>
+ <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars.</dd>
+ <dt>My email looks weird</dt>
+ <dd>Enigmail doesn't tend to play nice with HTML, which is used to format emails, so it may disable your HTML formatting automatically. To send an HTML-formatted email without encryption or a signature, hold down the Shift key when you select compose. You can then write an email as if Enigmail wasn't there.</dd>
+
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+ </div><!-- End #step-1b .step -->
+
+ </div>
+ </section><!-- End #section1 -->
+
+ <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
+ <section class="row" id="section2">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#2</em> 生成密钥</h2>
+ <p>要使用 GnuPG 体系，你将会用到一把公钥（public key）和一把私钥（private key），他们合称为密钥对（keypair）。每一把都是随机生成的一长串数字和字母的值，它是独一无二的。你的公钥和私钥由一种特殊的数学函数联系在一起。</p>
+
+ <p>你的公钥不太像现实中的钥匙，它公开储存在被称之为密钥服务器（keyserver）的在线目录上。人们可以下载使用它，借助 GnuPG，人们向你发送加密邮件。你可以把密钥服务器想象成一本电话簿；想要给你发送加密邮件的人能够找到你的公钥。</p>
+
+ <p>你的私钥更像是现实中的钥匙，你需要自行保管它（在你的计算机中）。你可以使用 GnuPG 和你的私钥来解密他人发给你的加密邮件。<span style="font-weight: bold;">无论如何，你都不应该改向他人分享你的私钥。</span></p>
+ <p>除了加密和解密，你可以使用这些密钥对消息进行签名，并检查其他人签名的真实性。我们将在下一节里详细探讨它。</p>
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-2a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 2.a</em> 生成密钥对</h3>
+ <p>Enigmail 安装向导可能会自动运行。如果没有，在你的邮件程序你选择 Enigmail → Setup Wizard。如果你不愿意，你不必去阅读弹出窗口中的文字，但读一读总归是好的。点击下一步而不对默认选项作修改，但除了下列情况以外：</p>
+ <ul>
+ <li>在“加密”（Encryption）界面，选中“默认加密所有我的消息，因为隐私对我很重要”（Encrypt all of my messages by default, because privacy is critical to me）。</li>
+ <li>在“签名”（Signing）界面，选中“默认不对我的消息签名”（Don't sign my messages by default）。</li>
+ <li>在“密钥选择”（Key Selection）界面，选择“我想为数字签名和加密邮件创建新密钥对”（I want to create a new key pair for signing and encrypting my email）。</li>
+ <li>在“创建密钥”（Create Key）界面。取一个强壮的密码吧！你可以自行取密码，也可以使用 Diceware 模式。自己取密码虽然快速，但不安全。使用 Diceware 需要更长时间 and requires dice,但能生成攻击者难以辨识出的密码。要使用它，请阅读 Micah Lee 写的<a href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">这篇文章</a>的 Make a secure passphrase with Diceware 一节。</li>
+ </ul>
+
+ <p>如果你喜欢自己取密码，想一个你记得起的至少十二字符长的东西，至少包含一个小写和大写字母，和一个数字或标点符号。永远不要使用你其他地方使用过的密码。不用使用任何可辨识的模式，诸如生日、电话号码、宠物名字、歌词或书中的引言。</p>
+
+ <p class="notes">在“生成密钥”（Key Creation）界面，程序需要花费小会儿完成下一步。等待时，你可以在计算机上做一些其他事情，比如看电影或浏览网页。此时你计算机使用的越频繁，密钥生成的速度越快。</p>
+ <p><span style="font-weight: bold;">当 "Key Generation Completed" （密钥已生成）窗口弹出，选中 Generate Certificate （生成证书）并选择把它储存在计算机上安全的地方（我们推荐新建一个名为 Revocation Certificate [吊销证书]的文件夹在你的家目录下，并把它保存在那里）。这是本指南重要的一步，你将会在 <a href="#section5">Section 5</a> 了解到更多信息。</span></p>
+
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>I can't find the Enigmail menu.</dt>
+ <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars. Enigmail may be inside a section called Tools.</dd>
+
+ <dt>The wizard says that it cannot find GnuPG.</dt>
+ <dd>Open whatever program you usually use for installing software, and search for GnuPG, then install it. Then restart the Enigmail setup wizard by going to Enigmail → Setup Wizard.</dd>
+
+ <dt>My email looks weird</dt>
+ <dd>Enigmail doesn't tend to play nice with HTML, which is used to format emails, so it may disable your HTML formatting automatically. To send an HTML-formatted email without encryption or a signature, hold down the Shift key when you select compose. You can then write an email as if Enigmail wasn't there.</dd>
+
+ <dt>More resources</dt>
+ <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Key_Management#Generating_your_own_key_pair">Enigmail's wiki instructions for key generation</a>.</dd>
+
+
+
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+
+
+ <dt>Command line key generation</dt>
+ <dd>If you prefer using the command line for a higher degree of control, you can follow the documentation from <a href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy Handbook</a>. Make sure you stick with "RSA and RSA" (the default), because it's newer and more secure than the algorithms the documentation recommends. Also make sure your key is at least 2048 bits, or 4096 if you want to be extra secure.</dd>
+
+ <dt>Advanced key pairs</dt>
+ <dd>When GnuPG creates a new keypair, it compartmentalizes the encryption function from the signing function through <a href="https://wiki.debian.org/Subkeys">subkeys</a>. If you use subkeys carefully, you can keep your GnuPG identity much more secure and recover from a compromised key much more quickly. <a href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal</a> and <a href="http://keyring.debian.org/creating-key.html">the Debian wiki</a> provide good guides for setting up a secure subkey configuration.</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+ </div><!-- End #step-2a .step -->
+
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-2b" class="step">
+ <div class="main">
+ <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
+ <p>In your email program's menu, select Enigmail → Key Management.</p>
+ <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
+ <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>
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>The progress bar never finishes</dt>
+ <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>
+ <dt>My key doesn't appear in the list</dt>
+ <dd>Try checking "Display All Keys by Default."</dd>
+ <dt>More documentation</dt>
+ <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://www.enigmail.net/documentation/quickstart-ch2.php#id2533620">Enigmail's documentation</a>.</dd>
+
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+ <dt>Uploading a key from the command line</dt>
+ <dd>You can also upload your keys to a keyserver through the <a href="https://www.gnupg.org/gph/en/manual/x457.html">command line</a>. <a href="https://sks-keyservers.net/overview-of-pools.php">The sks Web site</a> maintains a list of highly interconnected keyservers. You can also <a href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export your key</a> as a file on your computer.</dd>
+
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+ </div><!-- End #step-2b .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="terminology" class="step">
+ <div class="main">
+ <h3>GnuPG, OpenPGP, what?</h3>
+ <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG) is the program that implements the standard. Enigmail is a plug-in program for your email program that provides an interface for GnuPG.</p>
+ </div><!-- End .main -->
+ </div><!-- End #terminology.step-->
+
+
+ </div>
+ </section><!-- End #section2 -->
+
+ <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
+ <section class="row" id="section3">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#3</em> Try it out!</h2>
+ <p>Now you'll try a test correspondence with a computer program named Edward, who knows how to use encryption. Except where noted, these are the same steps you'd follow when corresponding with a real, live person.</p>
+
+ <!-- <p>NOTE: Edward is currently having some technical difficulties, so he may take a long time to respond, or not respond at all. We're sorry about this and we're working hard to fix it. Your key will still work even without testing with Edward.</p> -->
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 3.a</em> Send Edward your public key</h3>
+ <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 Enigmail → 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>
+
+ <p>Address the message to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Put at least one word (whatever you want) in the subject and body of the email. Don't send yet.</p>
+
+ <p>The lock icon in the top left should be yellow, meaning encryption is
+ turned on. We want this first special message to be unencrypted, so
+ click the icon once to turn it off. The lock should become grey, with a
+ blue dot on it (to alert you that the setting has been changed from the
+ default). Once encryption is off, hit Send.</p>
+
+ <p class="notes">It may take two or three minutes for Edward 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 he'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>
+
+ <p>When you open Edward's reply, GnuPG may prompt you for your password before using your private key to decrypt it.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-3a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3b" class="step">
+ <div class="main">
+ <h3><em>Step 3.b</em> Send a test encrypted email</h3>
+ <p>Write a new email in your email program, addressed to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Make the subject "Encryption test" or something similar and write something in the body.</p>
+ <p>The lock icon in the top left of the window should be yellow, meaning encryption is on. This will be your default from now on.</p>
+ <p class="notes">Next to the lock, you'll notice an icon of a pencil. We'll get to this in a moment.</p>
+ <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
+
+ <p>To encrypt an email to Edward, you need his public key, so now you'll have Enigmail download it from a keyserver. Click Download Missing Keys and use the default in the pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key ID starting with C), then select ok. Select ok in the next pop-up.</p>
+
+ <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Check the box in front of Edward's key and click Send.</p>
+
+ <p class="notes">Since you encrypted this email with Edward's public key, Edward's private key is required to decrypt it. Edward is the only one with his private key, so no one except him can decrypt it.</p>
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>Enigmail can't find Edward's key</dt>
+ <dd>Close the pop-ups that have appeared since you clicked Send. 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>
+ <dt>Unscrambled messages in the Sent folder</dt>
+ <dd>Even though you can't decrypt messages encrypted to someone else's key, your email program will automatically save a copy encrypted to your public key, which you'll be able to view from the Sent folder like a normal email. This is normal, and it doesn't mean that your email was not sent encrypted.</dd>
+ <dt>More resources</dt>
+ <dd>If you're still having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Signature_and_Encryption#Encrypting_a_message">Enigmail's wiki</a>.</dd>
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+ <dt>Encrypt messages from the command line</dt>
+ <dd>You can also encrypt and decrypt messages and files from the <a href="https://www.gnupg.org/gph/en/manual/x110.html">command line</a>, if that's your preference. The option --armor makes the encrypted output appear in the regular character set.</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+
+ </div><!-- End .main -->
+ </div><!-- End #step-3b .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-headers_unencrypted" class="step">
+ <div class="main">
+ <h3><em>Important:</em> Security tips</h3>
+ <p>Even if you encrypt 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 a surveillance system can still figure out who you're communicating with. Also, surveillance agents will know that you're using GnuPG, even if they can't figure out what you're saying. When you send attachments, Enigmail will give you the choice to encrypt them or not, independent of the actual email.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-headers_unencrypted .step-->
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3c" class="step">
+ <div class="main">
+ <h3><em>Step 3.c</em> Receive a response</h3>
+ <p>When Edward receives your email, he will use his private key to decrypt it, then use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to encrypt his reply to you.</p>
+
+ <p class="notes">It may take two or three minutes for Edward 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>
+ <p>When you receive Edward'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>
+ <p>Notice the bar that Enigmail shows you above the message, with information about the status of Edward's key.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-3c .step -->
+
+
+ <div id="step-3d" class="step">
+ <div class="main">
+ <h3><em>Step 3.d</em> Send a test signed email</h3>
+ <p>GnuPG includes a way for you to sign messages and files, verifying that they came from you and that they weren't tampered with along the way. These signatures are stronger than their pen-and-paper cousins -- they're impossible to forge, because they're impossible to create without your private key (another reason to keep your private key safe).</p>
+
+ <p>You can sign messages to anyone, so it's a great way to make people aware that you use GnuPG and that they can communicate with you securely. If they don't have GnuPG, they will be able to read your message and see your signature. If they do have GnuPG, they'll also be able to verify that your signature is authentic.</p>
+
+ <p>To sign an email to Edward, compose any message to him and click the pencil icon next to the lock icon so that it turns gold. If you sign a message, GnuPG may ask you for your password before it sends the message, because it needs to unlock your private key for signing.</p>
+
+ <p>With the lock and pencil icons, you can choose whether each message will be encrypted, signed, both, or neither.</p>
+ </div>
+ </div>
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3e" class="step">
+ <div class="main">
+ <h3><em>Step 3.e</em> Receive a response</h3>
+ <p>When Edward receives your email, he will use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to verify that your signature is authentic and the message you sent has not been tampered with.</p>
+
+ <p class="notes">It may take two or three minutes for Edward 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>
+
+ <p>Edward's reply will arrive encrypted, because he prefers to use encryption whenever possible. If everything goes according to plan, it should say "Your signature was verified." If your test signed email was also encrypted, he will mention that first.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-3c .step -->
+ </div>
+ </section>
+
+
+ <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
+ <section class="row" id="section4">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#4</em> Learn the Web of Trust</h2>
+ <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>
+
+ <p>When you sign someone's key, you are publicly saying that you've verified that it belongs to them and not someone else.</p>
+
+ <p>Signing keys and signing messages use the same type of mathematical operation, but they carry very different implications. It's a good practice to generally sign your email, but if you casually sign people's keys, you may accidently end up vouching for the identity of an imposter.</p>
+
+ <p>People who use your public key can see who has signed it. Once you've used GnuPG for a long time, your key may have hundreds of signatures. You can consider a key to be more trustworthy if it has many signatures from people that you trust. The Web of Trust is a constellation of GnuPG users, connected to each other by chains of trust expressed through signatures.</p>
+
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-4a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 4.a</em> Sign a key</h3>
+ <p>In your email program's menu, go to Enigmail → Key Management.</p>
+ <p>Right click on Edward's public key and select Sign Key from the context menu.</p>
+ <p>In the window that pops up, select "I will not answer" and click ok.</p>
+ <p>Now you should be back at the Key Management menu. Select Keyserver → Upload Public Keys and hit ok.</p>
+ <p class="notes">You've just effectively said "I trust that Edward's public key actually belongs to Edward." This doesn't mean much because Edward isn't a real person, but it's good practice.</p>
+
+
+ <!--<div id="pgp-pathfinder">
+ <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
+ <p><strong>From:</strong> <input type="text" placeholder="xD41A008" name="FROM"></p>
+ <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
+ <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
+ </form>
+ </div>End #pgp-pathfinder -->
+
+ </div><!-- End .main -->
+ </div><!-- End #step-4a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-identify_keys" class="step">
+ <div class="main">
+ <h3>Identifying keys: Fingerprints and IDs</h3>
+ <p>People's public keys are usually identified by their key fingerprint, which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Edward's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to Enigmail → 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 people can double-check that they have the correct public key when they download yours from a keyserver.</p>
+
+ <p class="notes">You may also see public keys referred to by their key ID, which is simply the last eight digits of the fingerprint, like C09A61E8 for Edward. 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 you are trying to communicate to verify which one to use.</p>
+
+ </div><!-- End .main -->
+ </div><!-- End #step-sign_real_keys .step-->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="check-ids-before-signing" class="step">
+ <div class="main">
+ <h3><em>Important:</em> What to consider when signing keys</h3>
+ <p>Before signing a person's key, you need to be confident that it actually belongs to them, and that they are who they say they are. Ideally, this confidence comes from having interactions and conversations with them over time, and witnessing interactions between them and others. Whenever signing a key, ask to see the full public key fingerprint, and not just the shorter key ID. If you feel it's important to sign the key of someone you've just met, also ask them to show you their government identification, and make sure the name on the ID matches the name on the public key. 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>
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+ <dt>Master the Web of Trust</dt>
+ <dd>Unfortunately, trust does not spread between users the way <a href="http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people think</a>. One of best ways to strengthen the GnuPG community is to deeply <a href="https://www.gnupg.org/gph/en/manual/x334.html">understand</a> the Web of Trust and to carefully sign as many people's keys as circumstances permit.</dd>
+ <dt>Set ownertrust</dt>
+ <dd>If you trust someone enough to validate other people's keys, you can assign them an ownertrust level through Enigmails's key management window. Right click on the other person's key, go to the "Select Owner Trust" menu option, select the trustlevel and click OK. Only do this once you feel you have a deep understanding of the Web of Trust.</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+
+ </div><!-- End #step-sign_real_keys .step-->
+
+
+ </div>
+ </section><!-- End #section4 -->
+
+ <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
+ <section id="section5" class="row">
+ <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>
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-5a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well (1)" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3>When should I encrypt? When should I sign?</h3>
+
+ <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. 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>Unless you don't want to reveal your own identity (which requires other protective measures), there's no reason not to sign every message, whether or not you are encrypting. In addition to allowing those with GnuPG to verify that the message came from you, signing is a non-intrusive way to remind everyone that you use GnuPG and show support for secure communication. If you often send signed messages to people that aren't familiar with GnuPG, it's nice to also include a link to this guide in your standard email signature (the text kind, not the cryptographic kind).</p>
+
+ </div><!-- End .main -->
+ </div><!-- End #step-5a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-5b" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well (2)" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3>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 first encrypted email that Edward sent you. Because Edward encrypted it with your public key, it will have a message from Enigmail at the top, which most likely says "Enigmail: 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>
+ </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, not on a device you carry with you regularly.</p>
+ <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>
+ </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 or forge your signature. This guide doesn't cover how to revoke a key, but you can follow these <a href="https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions</a>. After you're done revoking, make a new key and send an email to everyone with whom you usually use your key to make sure they know, including a copy of your new key.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-lost_key .step-->
+
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <!---<div id="transfer-key" class="step">
+ <div class="main">
+ <h3>Transferring you key</h3>
+ <p>You can use Enigmail's <a href="https://www.enigmail.net/documentation/keyman.php">key management window</a> to import and export keys. If you want to be able to read your encrypted email on a different computer, you will need to export your secret key from here. Be warned, if you transfer the key without <a href="https://help.ubuntu.com/community/EncryptedFilesystemsOnRemovableStorage">encrypting</a> the drive it's on the transfer will be dramatically less secure.</p>
+ </div>--><!-- End .main -->
+ </div><!-- End #step-lost_key .step-->
+
+
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="webmail-and-GnuPG" class="step">
+ <div class="main">
+ <h3>Webmail and GnuPG</h3>
+ <p>When you use a web browser to access your email, you're using webmail, an email program stored on a distant website. Unlike webmail, your desktop email program runs on your own computer. Although webmail can't decrypt encrypted email, it will still display it in its encrypted form. If you primarily use webmail, you'll know to open your email client when you receive a scrambled email.</p>
+ </div><!-- End .main -->
+ </div><!-- End #webmail-and-GnuPG .step-->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
+ <div id="step-5d" class="step">
+ <div class="main">
+ <h3>Make your public key part of your online identity</h3>
+ <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>
+
+ <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>
+ </div>--><!-- End .main
+</div> End #step-5d .step-->
+
+</section><!-- End #section5 -->
+
+
+
+<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
+<section class="row" id="section6">
+ <div id="step-click_here" class="step">
+ <div class="main">
+ <h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2>
+
+ </div><!-- End .main -->
+ </div><!-- End #step-click_here .step-->
+
+</section><!-- End #section6 -->
+
+<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
+<!-- When un-commenting this section go to main.css and search
+for /* Guide Sections Background */ then add #faq to the desired color
+
+<section class="row" id="faq">
+<div>
+<div class="sidebar">
+<h2>FAQ</h2>
+</div>
+
+<div class="main">
+<dl>
+<dt>My key expired</dt>
+<dd>Answer coming soon.</dd>
+
+<dt>Who can read encrypted messages? Who can read signed ones?</dt>
+<dd>Answer coming soon.</dd>
+
+<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>
+<dd>Answer coming soon.</dd>
+</dl>
+</div>
+</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>Copyright © 2014-2016 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please support our work by <a href="https://u.fsf.org/yr">joining us as an associate member.</a></p>
+
+ <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>. Download the <a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">source code of Edward reply bot</a> by Andrew Engelbrecht <sudoman@ninthfloor.org> and Josh Drake <zamnedix@gnu.org>, available under the GNU Affero General Public License. <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
+
+ <p>Fonts used in the guide & 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ś, <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a> by Florian Cramer.</p>
+
+ <p>Download the <a href="emailselfdefense_source.zip">source package</a> for this guide, including fonts, image source files and the text of Edward's messages.</p>
+
+ <p>This site uses the Weblabels standard for labeling <a href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" rel="jslicense">source code and license information</a>.</p>
+ </div><!-- /#copyright -->
+ <p class="credits">
+ Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" alt="Journalism++" /></a>
+ </p><!-- /.credits -->
+ </div>
+</footer><!-- End #footer -->
+
+<script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
+<script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
+
+<!-- Piwik -->
+<script type="text/javascript" >
+// @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later
+var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");
+document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
+try {
+ var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13);
+ piwikTracker.trackPageView();
+ piwikTracker.enableLinkTracking();
+} catch( err ) {}
+// @license-end
+</script><noscript><p><img src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0" alt="" /></p></noscript>
+<!-- End Piwik Tracking Code -->
+
+
+
+</body>
+</html>
-<!DOCTYPE html>\r
-<html lang="zh-Hans">\r
-<head>\r
- <meta http-equiv="content-type" content="text/html; charset=utf-8" />\r
-\r
- <title>电子邮件加密傻瓜指南</title>\r
- <meta name="keywords" content="GnuPG, GPG, openpgp, 监控, 隐私, 电子邮件, Enigmail" />\r
- <meta name="description" content="电子邮件监控侵犯了我们的基本权利，并危及了言论自由。本指南将在40分钟里教会你如何通过GnuPG加密邮件。" />\r
-\r
- <meta name="viewport" content="width=device-width, initial-scale=1" />\r
- <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />\r
- <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />\r
-\r
-</head>\r
-<body>\r
-\r
-<h3 class="wip">Translation in Progress</h3>\r
-<p class="wip">The <a href="/esd-zh-hans.po">PO file</a> is where work is being done. Please help us if you can. Thanks!</p>\r
-\r
- <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->\r
-\r
- <header class="row" id="header">\r
- <div>\r
- <h1>电子邮件加密傻瓜指南</h1>\r
-\r
- <!-- Language list for browsers that do not have JS enabled -->\r
- <ul id="languages" class="os">\r
-<li><a href="/en">English - v4.0</a></li>\r
-<li><a href="/ar">العربية <span class="tip">tip</span></a></li>\r
-<li><a href="/cs">Čeština - v4.0</a></li>\r
-<li><a href="/de">Deutsch - v3.0</a></li>\r
-<li><a href="/el">ελληνικά - v3.0</a></li>\r
-<li><a href="/es">español - v4.0</a></li>\r
-<li><a href="/fa">فارسی - v4.0</a></li>\r
-<li><a href="/fr">français - v4.0</a></li>\r
-<li><a href="/it">italiano - v3.0</a></li>\r
-<li><a href="/ja">日本語 - v4.0</a></li>\r
-<li><a href="/ko">한국어 <span class="tip">tip</span></a></li>\r
-<li><a href="/ml">മലയാളം <span class="tip">tip</span></a></li>\r
-<li><a href="/pt-br">português do Brasil - v3.0</a></li>\r
-<li><a href="/ro">română - v3.0</a></li>\r
-<li><a href="/ru">русский - v4.0</a></li>\r
-<li><a href="/sq">Shqip - v4.0</a></li>\r
-<li><a href="/sv">svenska - v4.0</a></li>\r
-<li><a href="/tr">Türkçe - v4.0</a></li>\r
-<li><a class="current" href="/zh-hans">简体中文 <span class="tip">tip</span></a></li>\r
-<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide"><strong><span style="color: #2F5FAA;">帮助翻译</span></strong></a></li>\r
- </ul>\r
-\r
- <ul id="menu" class="os">\r
- <li class="spacer">\r
- <a href="index.html">GNU/Linux</a>\r
- </li>\r
- <li>\r
- <a href="mac.html" class="current">Mac OS</a>\r
- </li>\r
- <li>\r
- <a href="windows.html">Windows</a>\r
- </li>\r
- <li class="spacer"><a href="workshops.html">研讨会</a></li>\r
- <li class="spacer">\r
- <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">\r
- 分享 \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"\r
- class="share-logo" alt="[GNU Social]" /> \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"\r
- class="share-logo" alt="[Pump.io]" /> \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"\r
- class="share-logo" alt="[Reddit]" /> \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png"\r
- class="share-logo" alt="[Hacker News]" />\r
- </a>\r
- </li>\r
- </ul>\r
-\r
- <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->\r
- <div id="fsf-intro">\r
- <h3>\r
- <a href="http://u.fsf.org/ys">\r
- <img alt="Free Software Foundation"\r
- src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />\r
- </a>\r
- </h3>\r
- <div class="fsf-emphasis">\r
- <p>\r
- 我们为计算机用户的权利而战，并促进自由软件的开发，对抗大规模监控对我们至关重要。\r
- </p>\r
- <p>\r
- <strong>\r
- 请捐款以支持电子邮件加密指南。我们会一直改进它，使其充实，for the benefit of people around the world taking the first step towards protecting their privacy.\r
- </strong>\r
- </p>\r
- </div>\r
-\r
- <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a> </p>\r
-\r
- </div><!-- End #fsf-intro -->\r
-\r
- <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->\r
- <div class="intro">\r
- <p>\r
- <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png" alt="View & share our infographic →" /></a>大规模监控侵犯了我们的基本权利，并危及了言论自由。本指南将会教授你一个基本的监控自我保护技巧：加密电子邮件。一旦你学会了，你将能够收发其他人无法阅读的电子邮件，包括那些拦截你邮件的监控代理或窃贼。你需要的是一台带网络连接的计算机，一个电子邮箱账号，和大约四十分钟时间。</p>\r
-\r
- <p>即使你没有什么见不得人的事情，通过加密可以保护通信对方的隐私，并使大规模监控变得困难。如果你确实有重要的东西需要隐藏，那么你并不孤独；告密者们在揭发人权侵犯、腐败以及其他犯罪问题时，也是使用同样的工具保护他们身份的。</p>\r
-\r
- <p>除了使用加密技术，我们还需要坚持不懈地与监控作政治斗争，以政府减少<a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">对我们的大量数据收集</a>。但重中之重是保护好你自己，使得监控你的通讯尽可能的困难。本指南将帮助你做到。它是为初学者设计的，但如果你已经掌握了 GnuPG 的基本知识，或你是一位资深自由软件用户，你会喜欢进阶提示与<a href="workshops.html">加密探讨会指南</a>。</p>\r
-\r
- </div><!-- End .intro -->\r
-\r
- </div>\r
- </header><!-- End #header -->\r
-\r
- <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->\r
- <section class="row" id="section1">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#1</em> 获取部件</h2>\r
- <p class="notes">本指南需要安装<a href="https://www.gnu.org/philosophy/free-sw.html">自由许可的</a>软件；它是完全透明的，任何人都可以复制它，并生成自己的版本。这使得它比专有软件（比如 Mac OS）更难受到监控。为了你免受监控，我们推荐你换用像 GNU/Linux 这样的自由软件操作系统。你可以在 <a href="https://u.fsf.org/ys">fsf.org</a> 上了解更多有关自由软件的信息。</p>\r
- <p>在开始之前，你需要安装 IceDove 邮件程序。对于你的操作系统来说，IceDove 可能以其别名 Thunderbird 而为人所知。电子邮件程序是另一种访问邮箱账号的途径（你也可以像 Gmail 那样通过浏览器访问），但它提供了更多的功能。</p>\r
- <p>如果你已经安装好了电子邮件程序，你可以跳至 <a href="#step-1b">Step 1.b</a>。</p>\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-1a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 1.a</em> 设置邮箱账号</h3>\r
- <p>打开你的邮件程序，按照向导程序的提示逐步设置好你的邮箱账号。</p>\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>The wizard doesn't launch</dt>\r
- <dd>You can launch the wizard yourself, but the menu option for doing so is named differently in each email programs. The button to launch it will be in the program's main menu, under "New" or something similar, titled something like "Add account" or "New/Existing email account."</dd>\r
- <dt>The wizard can't find my account or isn't downloading my mail</dt>\r
- <dd>Before searching the Web, we recommend you start by asking other people who use your email system, to figure out the correct settings.</dd>\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step1-a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-1b" class="step">\r
-\r
- <div class="main">\r
- <h3><em>Step 1.b</em> 下载 GPGTools</h3>\r
- <p>GPGTools 是一个包含了 GnuPG 的软件包。<a href="https://gpgtools.org/#gpgsuite">下载</a>并安装它，选择默认选项无论提示什么。安装完成后关闭窗口。</p>\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step1-b .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-1c" class="step">\r
- <div class="sidebar">\r
- <ul class="images">\r
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png" alt="Step 1.C: Tools -> Add-ons" /></li>\r
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png" alt="Step 1.C: Search Add-ons" /></li>\r
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png" alt="Step 1.C: Install Add-ons" /></li>\r
- </ul>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 1.c</em> 安装 ENIGMAIL 插件</h3>\r
- <p>在邮件程序的菜单栏里，选择“附加组件”（Add-ons，它可能在工具选项里）。确认选上了左侧的“扩展”（Extensions）。看到了 Enigmail 吗？如果是，请跳过此步。</p>\r
- <p>如果没有，在右上方的搜索框里搜索“Enigmail”。你可以在这里获取到它。安装完成后重启邮件程序。</p>\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>I can't find the menu.</dt>\r
- <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars.</dd>\r
-\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
- </div><!-- End #step-1c .step -->\r
- </div>\r
- </section><!-- End #section1 -->\r
-\r
- <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->\r
- <section class="row" id="section2">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#2</em> 生成密钥</h2>\r
- <p>要使用 GnuPG 体系，你将会用到一把公钥（public key）和一把私钥（private key），他们合称为密钥对（keypair）。每一把都是随机生成的一长串数字和字母的值，它是独一无二的。你的公钥和私钥由一种特殊的数学函数联系在一起。</p>\r
-\r
- <p>你的公钥不太像现实中的钥匙，它公开储存在被称之为密钥服务器（keyserver）的在线目录上。人们可以下载使用它，借助 GnuPG，人们向你发送加密邮件。你可以把密钥服务器想象成一本电话簿；想要给你发送加密邮件的人能够找到你的公钥。</p>\r
-\r
- <p>你的私钥更像是现实中的钥匙，你需要自行保管它（在你的计算机中）。你可以使用 GnuPG 和你的私钥来解密他人发给你的加密邮件。<span style="font-weight: bold;">无论如何，你都不应该改向他人分享你的私钥。</span></p>\r
- <p>除了加密和解密，你可以使用这些密钥对消息进行签名，并检查其他人签名的真实性。我们将在下一节里详细探讨它。</p>\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-2a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 2.a</em> 生成密钥对</h3>\r
- <p>Enigmail 安装向导可能会自动运行。如果没有，在你的邮件程序你选择 Enigmail → Setup Wizard。如果你不愿意，你不必去阅读弹出窗口中的文字，但读一读总归是好的。点击下一步而不对默认选项作修改，但除了下列情况以外：</p>\r
- <ul>\r
- <li>在“加密”（Encryption）界面，选中“默认加密所有我的消息，因为隐私对我很重要”（Encrypt all of my messages by default, because privacy is critical to me）。</li>\r
- <li>在“签名”（Signing）界面，选中“默认不对我的消息签名”（Don't sign my messages by default）。</li>\r
- <li>在“密钥选择”（Key Selection）界面，选择“我想为数字签名和加密邮件创建新密钥对”（I want to create a new key pair for signing and encrypting my email）。</li>\r
- <li>在“创建密钥”（Create Key）界面。取一个强壮的密码吧！你可以自行取密码，也可以使用 Diceware 模式。自己取密码虽然快速，但不安全。使用 Diceware 需要更长时间 and requires dice,但能生成攻击者难以辨识出的密码。要使用它，请阅读 Micah Lee 写的<a href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">这篇文章</a>的 Make a secure passphrase with Diceware 一节。</li>\r
- </ul>\r
-\r
- <p>如果你喜欢自己取密码，想一个你记得起的至少十二字符长的东西，至少包含一个小写和大写字母，和一个数字或标点符号。永远不要使用你其他地方使用过的密码。不用使用任何可辨识的模式，诸如生日、电话号码、宠物名字、歌词或书中的引言。</p>\r
-\r
- <p class="notes">在“生成密钥”（Key Creation）界面，程序需要花费小会儿完成下一步。等待时，你可以在计算机上做一些其他事情，比如看电影或浏览网页。此时你计算机使用的越频繁，密钥生成的速度越快。</p>\r
- <p><span style="font-weight: bold;">当 "Key Generation Completed" （密钥已生成）窗口弹出，选中 Generate Certificate （生成证书）并选择把它储存在计算机上安全的地方（我们推荐新建一个名为 Revocation Certificate [吊销证书]的文件夹在你的家目录下，并把它保存在那里）。这是本指南重要的一步，你将会在 <a href="#section5">Section 5</a> 了解到更多信息。</span></p>\r
-\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>I can't find the Enigmail menu.</dt>\r
- <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars. Enigmail may be inside a section called Tools.</dd>\r
-\r
- <dt>My email looks weird</dt>\r
- <dd>Enigmail doesn't tend to play nice with HTML, which is used to format emails, so it may disable your HTML formatting automatically. To send an HTML-formatted email without encryption or a signature, hold down the Shift key when you select compose. You can then write an email as if Enigmail wasn't there.</dd>\r
-\r
- <dt>More resources</dt>\r
- <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Key_Management#Generating_your_own_key_pair">Enigmail's wiki instructions for key generation</a>.</dd>\r
-\r
-\r
-\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
-\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
-\r
-\r
- <dt>Command line key generation</dt>\r
- <dd>If you prefer using the command line for a higher degree of control, you can follow the documentation from <a href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy Handbook</a>. Make sure you stick with "RSA and RSA" (the default), because it's newer and more secure than the algorithms the documentation recommends. Also make sure your key is at least 2048 bits, or 4096 if you want to be extra secure.</dd>\r
-\r
- <dt>Advanced key pairs</dt>\r
- <dd>When GnuPG creates a new keypair, it compartmentalizes the encryption function from the signing function through <a href="https://wiki.debian.org/Subkeys">subkeys</a>. If you use subkeys carefully, you can keep your GnuPG identity much more secure and recover from a compromised key much more quickly. <a href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal</a> and <a href="http://keyring.debian.org/creating-key.html">the Debian wiki</a> provide good guides for setting up a secure subkey configuration.</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
- </div><!-- End #step-2a .step -->\r
-\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-2b" class="step">\r
- <div class="main">\r
- <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>\r
- <p>In your email program's menu, select Enigmail → Key Management.</p>\r
- <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>\r
- <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>\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>The progress bar never finishes</dt>\r
- <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>\r
- <dt>My key doesn't appear in the list</dt>\r
- <dd>Try checking "Display All Keys by Default."</dd>\r
- <dt>More documentation</dt>\r
- <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://www.enigmail.net/documentation/quickstart-ch2.php#id2533620">Enigmail's documentation</a>.</dd>\r
-\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
-\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
- <dt>Uploading a key from the command line</dt>\r
- <dd>You can also upload your keys to a keyserver through the <a href="https://www.gnupg.org/gph/en/manual/x457.html">command line</a>. <a href="https://sks-keyservers.net/overview-of-pools.php">The sks Web site</a> maintains a list of highly interconnected keyservers. You can also <a href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export your key</a> as a file on your computer.</dd>\r
-\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
- </div><!-- End #step-2b .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="terminology" class="step">\r
- <div class="main">\r
- <h3>GnuPG, OpenPGP, what?</h3>\r
- <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG) is the program that implements the standard. Enigmail is a plug-in program for your email program that provides an interface for GnuPG.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #terminology.step-->\r
-\r
-\r
- </div>\r
- </section><!-- End #section2 -->\r
-\r
- <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->\r
- <section class="row" id="section3">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#3</em> Try it out!</h2>\r
- <p>Now you'll try a test correspondence with a computer program named Edward, who knows how to use encryption. Except where noted, these are the same steps you'd follow when corresponding with a real, live person.</p>\r
-\r
- <!-- <p>NOTE: Edward is currently having some technical difficulties, so he may take a long time to respond, or not respond at all. We're sorry about this and we're working hard to fix it. Your key will still work even without testing with Edward.</p> -->\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png" alt="Try it out." /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 3.a</em> Send Edward your public key</h3>\r
- <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 Enigmail → 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>\r
-\r
- <p>Address the message to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Put at least one word (whatever you want) in the subject and body of the email. Don't send yet.</p>\r
-\r
- <p>The lock icon in the top left should be yellow, meaning encryption is\r
- turned on. We want this first special message to be unencrypted, so\r
- click the icon once to turn it off. The lock should become grey, with a\r
- blue dot on it (to alert you that the setting has been changed from the\r
- default). Once encryption is off, hit Send.</p>\r
-\r
- <p class="notes">It may take two or three minutes for Edward 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 he'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>\r
-\r
- <p>When you open Edward's reply, GnuPG may prompt you for your password before using your private key to decrypt it.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3b" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.b</em> Send a test encrypted email</h3>\r
- <p>Write a new email in your email program, addressed to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Make the subject "Encryption test" or something similar and write something in the body.</p>\r
- <p>The lock icon in the top left of the window should be yellow, meaning encryption is on. This will be your default from now on.</p>\r
- <p class="notes">Next to the lock, you'll notice an icon of a pencil. We'll get to this in a moment.</p>\r
- <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>\r
-\r
- <p>To encrypt an email to Edward, you need his public key, so now you'll have Enigmail download it from a keyserver. Click Download Missing Keys and use the default in the pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key ID starting with C), then select ok. Select ok in the next pop-up.</p>\r
-\r
- <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Check the box in front of Edward's key and click Send.</p>\r
-\r
- <p class="notes">Since you encrypted this email with Edward's public key, Edward's private key is required to decrypt it. Edward is the only one with his private key, so no one except him can decrypt it.</p>\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>Enigmail can't find Edward's key</dt>\r
- <dd>Close the pop-ups that have appeared since you clicked Send. 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>\r
- <dt>Unscrambled messages in the Sent folder</dt>\r
- <dd>Even though you can't decrypt messages encrypted to someone else's key, your email program will automatically save a copy encrypted to your public key, which you'll be able to view from the Sent folder like a normal email. This is normal, and it doesn't mean that your email was not sent encrypted.</dd>\r
- <dt>More resources</dt>\r
- <dd>If you're still having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Signature_and_Encryption#Encrypting_a_message">Enigmail's wiki</a>.</dd>\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
- <dt>Encrypt messages from the command line</dt>\r
- <dd>You can also encrypt and decrypt messages and files from the <a href="https://www.gnupg.org/gph/en/manual/x110.html">command line</a>, if that's your preference. The option --armor makes the encrypted output appear in the regular character set.</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3b .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-headers_unencrypted" class="step">\r
- <div class="main">\r
- <h3><em>Important:</em> Security tips</h3>\r
- <p>Even if you encrypt 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 a surveillance system can still figure out who you're communicating with. Also, surveillance agents will know that you're using GnuPG, even if they can't figure out what you're saying. When you send attachments, Enigmail will give you the choice to encrypt them or not, independent of the actual email.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-headers_unencrypted .step-->\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3c" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.c</em> Receive a response</h3>\r
- <p>When Edward receives your email, he will use his private key to decrypt it, then use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to encrypt his reply to you.</p>\r
-\r
- <p class="notes">It may take two or three minutes for Edward 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>\r
- <p>When you receive Edward'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>\r
- <p>Notice the bar that Enigmail shows you above the message, with information about the status of Edward's key.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3c .step -->\r
-\r
-\r
- <div id="step-3d" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.d</em> Send a test signed email</h3>\r
- <p>GnuPG includes a way for you to sign messages and files, verifying that they came from you and that they weren't tampered with along the way. These signatures are stronger than their pen-and-paper cousins -- they're impossible to forge, because they're impossible to create without your private key (another reason to keep your private key safe).</p>\r
-\r
- <p>You can sign messages to anyone, so it's a great way to make people aware that you use GnuPG and that they can communicate with you securely. If they don't have GnuPG, they will be able to read your message and see your signature. If they do have GnuPG, they'll also be able to verify that your signature is authentic.</p>\r
-\r
- <p>To sign an email to Edward, compose any message to him and click the pencil icon next to the lock icon so that it turns gold. If you sign a message, GnuPG may ask you for your password before it sends the message, because it needs to unlock your private key for signing.</p>\r
-\r
- <p>With the lock and pencil icons, you can choose whether each message will be encrypted, signed, both, or neither.</p>\r
- </div>\r
- </div>\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3e" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.e</em> Receive a response</h3>\r
- <p>When Edward receives your email, he will use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to verify that your signature is authentic and the message you sent has not been tampered with.</p>\r
-\r
- <p class="notes">It may take two or three minutes for Edward 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>\r
-\r
- <p>Edward's reply will arrive encrypted, because he prefers to use encryption whenever possible. If everything goes according to plan, it should say "Your signature was verified." If your test signed email was also encrypted, he will mention that first.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3c .step -->\r
- </div>\r
- </section>\r
-\r
-\r
- <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->\r
- <section class="row" id="section4">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#4</em> Learn the Web of Trust</h2>\r
- <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>\r
-\r
- <p>When you sign someone's key, you are publicly saying that you've verified that it belongs to them and not someone else.</p>\r
-\r
- <p>Signing keys and signing messages use the same type of mathematical operation, but they carry very different implications. It's a good practice to generally sign your email, but if you casually sign people's keys, you may accidently end up vouching for the identity of an imposter.</p>\r
-\r
- <p>People who use your public key can see who has signed it. Once you've used GnuPG for a long time, your key may have hundreds of signatures. You can consider a key to be more trustworthy if it has many signatures from people that you trust. The Web of Trust is a constellation of GnuPG users, connected to each other by chains of trust expressed through signatures.</p>\r
-\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-4a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 4.a</em> Sign a key</h3>\r
- <p>In your email program's menu, go to Enigmail → Key Management.</p>\r
- <p>Right click on Edward's public key and select Sign Key from the context menu.</p>\r
- <p>In the window that pops up, select "I will not answer" and click ok.</p>\r
- <p>Now you should be back at the Key Management menu. Select Keyserver → Upload Public Keys and hit ok.</p>\r
- <p class="notes">You've just effectively said "I trust that Edward's public key actually belongs to Edward." This doesn't mean much because Edward isn't a real person, but it's good practice.</p>\r
-\r
-\r
- <!--<div id="pgp-pathfinder">\r
- <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">\r
- <p><strong>From:</strong> <input type="text" placeholder="xD41A008" name="FROM"></p>\r
- <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>\r
- <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>\r
- </form>\r
- </div>End #pgp-pathfinder -->\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-4a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-identify_keys" class="step">\r
- <div class="main">\r
- <h3>Identifying keys: Fingerprints and IDs</h3>\r
- <p>People's public keys are usually identified by their key fingerprint, which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Edward's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to Enigmail → 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 people can double-check that they have the correct public key when they download yours from a keyserver.</p>\r
-\r
- <p class="notes">You may also see public keys referred to by their key ID, which is simply the last eight digits of the fingerprint, like C09A61E8 for Edward. 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 you are trying to communicate to verify which one to use.</p>\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-sign_real_keys .step-->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="check-ids-before-signing" class="step">\r
- <div class="main">\r
- <h3><em>Important:</em> What to consider when signing keys</h3>\r
- <p>Before signing a person's key, you need to be confident that it actually belongs to them, and that they are who they say they are. Ideally, this confidence comes from having interactions and conversations with them over time, and witnessing interactions between them and others. Whenever signing a key, ask to see the full public key fingerprint, and not just the shorter key ID. If you feel it's important to sign the key of someone you've just met, also ask them to show you their government identification, and make sure the name on the ID matches the name on the public key. 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?"\r
-</p>\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
- <dt>Master the Web of Trust</dt>\r
- <dd>Unfortunately, trust does not spread between users the way <a href="http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people think</a>. One of best ways to strengthen the GnuPG community is to deeply <a href="https://www.gnupg.org/gph/en/manual/x334.html">understand</a> the Web of Trust and to carefully sign as many people's keys as circumstances permit.</dd>\r
- <dt>Set ownertrust</dt>\r
- <dd>If you trust someone enough to validate other people's keys, you can assign them an ownertrust level through Enigmails's key management window. Right click on the other person's key, go to the "Select Owner Trust" menu option, select the trustlevel and click OK. Only do this once you feel you have a deep understanding of the Web of Trust.</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
-\r
- </div><!-- End #step-sign_real_keys .step-->\r
-\r
-\r
- </div>\r
- </section><!-- End #section4 -->\r
-\r
- <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->\r
- <section id="section5" class="row">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#5</em> Use it well</h2>\r
- <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>\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-5a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well (1)" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3>When should I encrypt? When should I sign?</h3>\r
-\r
- <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. 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>\r
- <p>Unless you don't want to reveal your own identity (which requires other protective measures), there's no reason not to sign every message, whether or not you are encrypting. In addition to allowing those with GnuPG to verify that the message came from you, signing is a non-intrusive way to remind everyone that you use GnuPG and show support for secure communication. If you often send signed messages to people that aren't familiar with GnuPG, it's nice to also include a link to this guide in your standard email signature (the text kind, not the cryptographic kind).</p>\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-5a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-5b" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well (2)" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3>Be wary of invalid keys</h3>\r
- <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>\r
- <p>In your email program, go back to the first encrypted email that Edward sent you. Because Edward encrypted it with your public key, it will have a message from Enigmail at the top, which most likely says "Enigmail: Part of this message encrypted."</p>\r
- <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>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-5b .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-5c" class="step">\r
- <div class="main">\r
- <h3>Copy your revocation certificate to somewhere safe</h3>\r
- <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, not on a device you carry with you regularly.</p>\r
- <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>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-5c .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-lost_key" class="step">\r
- <div class="main">\r
- <h3><em>Important:</em> act swiftly if someone gets your private key</h3>\r
- <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 or forge your signature. This guide doesn't cover how to revoke a key, but you can follow these <a href="https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions</a>. After you're done revoking, make a new key and send an email to everyone with whom you usually use your key to make sure they know, including a copy of your new key.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-lost_key .step-->\r
-\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <!---<div id="transfer-key" class="step">\r
- <div class="main">\r
- <h3>Transferring you key</h3>\r
- <p>You can use Enigmail's <a href="https://www.enigmail.net/documentation/keyman.php">key management window</a> to import and export keys. If you want to be able to read your encrypted email on a different computer, you will need to export your secret key from here. Be warned, if you transfer the key without <a href="https://help.ubuntu.com/community/EncryptedFilesystemsOnRemovableStorage">encrypting</a> the drive it's on the transfer will be dramatically less secure.</p>\r
- </div>--><!-- End .main -->\r
- </div><!-- End #step-lost_key .step-->\r
-\r
-\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="webmail-and-GnuPG" class="step">\r
- <div class="main">\r
- <h3>Webmail and GnuPG</h3>\r
- <p>When you use a web browser to access your email, you're using webmail, an email program stored on a distant website. Unlike webmail, your desktop email program runs on your own computer. Although webmail can't decrypt encrypted email, it will still display it in its encrypted form. If you primarily use webmail, you'll know to open your email client when you receive a scrambled email.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #webmail-and-GnuPG .step-->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~\r
- <div id="step-5d" class="step">\r
- <div class="main">\r
- <h3>Make your public key part of your online identity</h3>\r
- <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>\r
-\r
- <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>\r
- </div>--><!-- End .main\r
-</div> End #step-5d .step-->\r
-\r
-\r
-</section><!-- End #section5 -->\r
-\r
-\r
-\r
-<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->\r
-<section class="row" id="section6">\r
- <div id="step-click_here" class="step">\r
- <div class="main">\r
- <h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2>\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-click_here .step-->\r
-\r
-</section><!-- End #section6 -->\r
-\r
-<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->\r
-<!-- When un-commenting this section go to main.css and search\r
-for /* Guide Sections Background */ then add #faq to the desired color\r
-\r
-<section class="row" id="faq">\r
-<div>\r
-<div class="sidebar">\r
-<h2>FAQ</h2>\r
-</div>\r
-\r
-<div class="main">\r
-<dl>\r
-<dt>My key expired</dt>\r
-<dd>Answer coming soon.</dd>\r
-\r
-<dt>Who can read encrypted messages? Who can read signed ones?</dt>\r
-<dd>Answer coming soon.</dd>\r
-\r
-<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>\r
-<dd>Answer coming soon.</dd>\r
-</dl>\r
-</div>\r
-</div>\r
-</section> --><!-- End #faq -->\r
-\r
-<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->\r
-<footer class="row" id="footer">\r
- <div>\r
- <div id="copyright">\r
- <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>\r
- <p>Copyright © 2014-2016 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please support our work by <a href="https://u.fsf.org/yr">joining us as an associate member.</a></p>\r
-\r
- <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>. Download the <a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">source code of Edward reply bot</a> by Andrew Engelbrecht <sudoman@ninthfloor.org> and Josh Drake <zamnedix@gnu.org>, available under the GNU Affero General Public License. <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>\r
-\r
- <p>Fonts used in the guide & 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ś, <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a> by Florian Cramer.</p>\r
-\r
- <p>Download the <a href="emailselfdefense_source.zip">source package</a> for this guide, including fonts, image source files and the text of Edward's messages.</p>\r
-\r
- <p>This site uses the Weblabels standard for labeling <a href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" rel="jslicense">source code and license information</a>.</p>\r
- </div><!-- /#copyright -->\r
- <p class="credits">\r
- Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" alt="Journalism++" /></a>\r
- </p><!-- /.credits -->\r
- </div>\r
-</footer><!-- End #footer -->\r
-\r
-<script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>\r
-<script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>\r
-\r
-<!-- Piwik -->\r
-<script type="text/javascript" >\r
-// @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later\r
-var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");\r
-document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));\r
-try {\r
- var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13);\r
- piwikTracker.trackPageView();\r
- piwikTracker.enableLinkTracking();\r
-} catch( err ) {}\r
-// @license-end\r
-</script><noscript><p><img src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0" alt="" /></p></noscript>\r
-<!-- End Piwik Tracking Code -->\r
-\r
-\r
-\r
-</body>\r
-</html>\r
+<!DOCTYPE html>
+<html lang="zh-Hans">
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=utf-8" />
+
+ <title>电子邮件加密傻瓜指南</title>
+ <meta name="keywords" content="GnuPG, GPG, openpgp, 监控, 隐私, 电子邮件, Enigmail" />
+ <meta name="description" content="电子邮件监控侵犯了我们的基本权利，并危及了言论自由。本指南将在40分钟里教会你如何通过GnuPG加密邮件。" />
+
+ <meta name="viewport" content="width=device-width, initial-scale=1" />
+ <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />
+ <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
+
+</head>
+<body>
+
+<h3 class="wip">Translation in Progress</h3>
+<p class="wip">The <a href="/esd-zh-hans.po">PO file</a> is where work is being done. Please help us if you can. Thanks!</p>
+
+ <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
+
+ <header class="row" id="header">
+ <div>
+ <h1>电子邮件加密傻瓜指南</h1>
+
+ <!-- Language list for browsers that do not have JS enabled -->
+ <ul id="languages" class="os">
+<li><a href="/en">English - v4.0</a></li>
+<li><a href="/ar">العربية <span class="tip">tip</span></a></li>
+<li><a href="/cs">Čeština - v4.0</a></li>
+<li><a href="/de">Deutsch - v3.0</a></li>
+<li><a href="/el">ελληνικά - v3.0</a></li>
+<li><a href="/es">español - v4.0</a></li>
+<li><a href="/fa">فارسی - v4.0</a></li>
+<li><a href="/fr">français - v4.0</a></li>
+<li><a href="/it">italiano - v3.0</a></li>
+<li><a href="/ja">日本語 - v4.0</a></li>
+<li><a href="/ko">한국어 <span class="tip">tip</span></a></li>
+<li><a href="/ml">മലയാളം <span class="tip">tip</span></a></li>
+<li><a href="/pt-br">português do Brasil - v3.0</a></li>
+<li><a href="/ro">română - v3.0</a></li>
+<li><a href="/ru">русский - v4.0</a></li>
+<li><a href="/sq">Shqip - v4.0</a></li>
+<li><a href="/sv">svenska - v4.0</a></li>
+<li><a href="/tr">Türkçe - v4.0</a></li>
+<li><a class="current" href="/zh-hans">简体中文 <span class="tip">tip</span></a></li>
+<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide"><strong><span style="color: #2F5FAA;">帮助翻译</span></strong></a></li>
+ </ul>
+
+ <ul id="menu" class="os">
+ <li class="spacer">
+ <a href="index.html">GNU/Linux</a>
+ </li>
+ <li>
+ <a href="mac.html" class="current">Mac OS</a>
+ </li>
+ <li>
+ <a href="windows.html">Windows</a>
+ </li>
+ <li class="spacer"><a href="workshops.html">研讨会</a></li>
+ <li class="spacer">
+ <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">
+ 分享
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"
+ class="share-logo" alt="[GNU Social]" />
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"
+ class="share-logo" alt="[Pump.io]" />
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"
+ class="share-logo" alt="[Reddit]" />
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png"
+ class="share-logo" alt="[Hacker News]" />
+ </a>
+ </li>
+ </ul>
+
+ <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
+ <div id="fsf-intro">
+ <h3>
+ <a href="http://u.fsf.org/ys">
+ <img alt="Free Software Foundation"
+ src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />
+ </a>
+ </h3>
+ <div class="fsf-emphasis">
+ <p>
+ 我们为计算机用户的权利而战，并促进自由软件的开发，对抗大规模监控对我们至关重要。
+ </p>
+ <p>
+ <strong>
+ 请捐款以支持电子邮件加密指南。我们会一直改进它，使其充实，for the benefit of people around the world taking the first step towards protecting their privacy.
+ </strong>
+ </p>
+ </div>
+
+ <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a> </p>
+
+ </div><!-- End #fsf-intro -->
+
+ <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
+ <div class="intro">
+ <p>
+ <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png" alt="View & share our infographic →" /></a>大规模监控侵犯了我们的基本权利，并危及了言论自由。本指南将会教授你一个基本的监控自我保护技巧：加密电子邮件。一旦你学会了，你将能够收发其他人无法阅读的电子邮件，包括那些拦截你邮件的监控代理或窃贼。你需要的是一台带网络连接的计算机，一个电子邮箱账号，和大约四十分钟时间。</p>
+
+ <p>即使你没有什么见不得人的事情，通过加密可以保护通信对方的隐私，并使大规模监控变得困难。如果你确实有重要的东西需要隐藏，那么你并不孤独；告密者们在揭发人权侵犯、腐败以及其他犯罪问题时，也是使用同样的工具保护他们身份的。</p>
+
+ <p>除了使用加密技术，我们还需要坚持不懈地与监控作政治斗争，以政府减少<a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">对我们的大量数据收集</a>。但重中之重是保护好你自己，使得监控你的通讯尽可能的困难。本指南将帮助你做到。它是为初学者设计的，但如果你已经掌握了 GnuPG 的基本知识，或你是一位资深自由软件用户，你会喜欢进阶提示与<a href="workshops.html">加密探讨会指南</a>。</p>
+
+ </div><!-- End .intro -->
+
+ </div>
+ </header><!-- End #header -->
+
+ <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
+ <section class="row" id="section1">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#1</em> 获取部件</h2>
+ <p class="notes">本指南需要安装<a href="https://www.gnu.org/philosophy/free-sw.html">自由许可的</a>软件；它是完全透明的，任何人都可以复制它，并生成自己的版本。这使得它比专有软件（比如 Mac OS）更难受到监控。为了你免受监控，我们推荐你换用像 GNU/Linux 这样的自由软件操作系统。你可以在 <a href="https://u.fsf.org/ys">fsf.org</a> 上了解更多有关自由软件的信息。</p>
+ <p>在开始之前，你需要安装 IceDove 邮件程序。对于你的操作系统来说，IceDove 可能以其别名 Thunderbird 而为人所知。电子邮件程序是另一种访问邮箱账号的途径（你也可以像 Gmail 那样通过浏览器访问），但它提供了更多的功能。</p>
+ <p>如果你已经安装好了电子邮件程序，你可以跳至 <a href="#step-1b">Step 1.b</a>。</p>
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-1a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 1.a</em> 设置邮箱账号</h3>
+ <p>打开你的邮件程序，按照向导程序的提示逐步设置好你的邮箱账号。</p>
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>The wizard doesn't launch</dt>
+ <dd>You can launch the wizard yourself, but the menu option for doing so is named differently in each email programs. The button to launch it will be in the program's main menu, under "New" or something similar, titled something like "Add account" or "New/Existing email account."</dd>
+ <dt>The wizard can't find my account or isn't downloading my mail</dt>
+ <dd>Before searching the Web, we recommend you start by asking other people who use your email system, to figure out the correct settings.</dd>
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+ </div><!-- End .main -->
+ </div><!-- End #step1-a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-1b" class="step">
+
+ <div class="main">
+ <h3><em>Step 1.b</em> 下载 GPGTools</h3>
+ <p>GPGTools 是一个包含了 GnuPG 的软件包。<a href="https://gpgtools.org/#gpgsuite">下载</a>并安装它，选择默认选项无论提示什么。安装完成后关闭窗口。</p>
+
+ </div><!-- End .main -->
+ </div><!-- End #step1-b .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-1c" class="step">
+ <div class="sidebar">
+ <ul class="images">
+ <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png" alt="Step 1.C: Tools -> Add-ons" /></li>
+ <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png" alt="Step 1.C: Search Add-ons" /></li>
+ <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png" alt="Step 1.C: Install Add-ons" /></li>
+ </ul>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 1.c</em> 安装 ENIGMAIL 插件</h3>
+ <p>在邮件程序的菜单栏里，选择“附加组件”（Add-ons，它可能在工具选项里）。确认选上了左侧的“扩展”（Extensions）。看到了 Enigmail 吗？如果是，请跳过此步。</p>
+ <p>如果没有，在右上方的搜索框里搜索“Enigmail”。你可以在这里获取到它。安装完成后重启邮件程序。</p>
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>I can't find the menu.</dt>
+ <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars.</dd>
+
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+ </div><!-- End #step-1c .step -->
+ </div>
+ </section><!-- End #section1 -->
+
+ <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
+ <section class="row" id="section2">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#2</em> 生成密钥</h2>
+ <p>要使用 GnuPG 体系，你将会用到一把公钥（public key）和一把私钥（private key），他们合称为密钥对（keypair）。每一把都是随机生成的一长串数字和字母的值，它是独一无二的。你的公钥和私钥由一种特殊的数学函数联系在一起。</p>
+
+ <p>你的公钥不太像现实中的钥匙，它公开储存在被称之为密钥服务器（keyserver）的在线目录上。人们可以下载使用它，借助 GnuPG，人们向你发送加密邮件。你可以把密钥服务器想象成一本电话簿；想要给你发送加密邮件的人能够找到你的公钥。</p>
+
+ <p>你的私钥更像是现实中的钥匙，你需要自行保管它（在你的计算机中）。你可以使用 GnuPG 和你的私钥来解密他人发给你的加密邮件。<span style="font-weight: bold;">无论如何，你都不应该改向他人分享你的私钥。</span></p>
+ <p>除了加密和解密，你可以使用这些密钥对消息进行签名，并检查其他人签名的真实性。我们将在下一节里详细探讨它。</p>
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-2a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 2.a</em> 生成密钥对</h3>
+ <p>Enigmail 安装向导可能会自动运行。如果没有，在你的邮件程序你选择 Enigmail → Setup Wizard。如果你不愿意，你不必去阅读弹出窗口中的文字，但读一读总归是好的。点击下一步而不对默认选项作修改，但除了下列情况以外：</p>
+ <ul>
+ <li>在“加密”（Encryption）界面，选中“默认加密所有我的消息，因为隐私对我很重要”（Encrypt all of my messages by default, because privacy is critical to me）。</li>
+ <li>在“签名”（Signing）界面，选中“默认不对我的消息签名”（Don't sign my messages by default）。</li>
+ <li>在“密钥选择”（Key Selection）界面，选择“我想为数字签名和加密邮件创建新密钥对”（I want to create a new key pair for signing and encrypting my email）。</li>
+ <li>在“创建密钥”（Create Key）界面。取一个强壮的密码吧！你可以自行取密码，也可以使用 Diceware 模式。自己取密码虽然快速，但不安全。使用 Diceware 需要更长时间 and requires dice,但能生成攻击者难以辨识出的密码。要使用它，请阅读 Micah Lee 写的<a href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">这篇文章</a>的 Make a secure passphrase with Diceware 一节。</li>
+ </ul>
+
+ <p>如果你喜欢自己取密码，想一个你记得起的至少十二字符长的东西，至少包含一个小写和大写字母，和一个数字或标点符号。永远不要使用你其他地方使用过的密码。不用使用任何可辨识的模式，诸如生日、电话号码、宠物名字、歌词或书中的引言。</p>
+
+ <p class="notes">在“生成密钥”（Key Creation）界面，程序需要花费小会儿完成下一步。等待时，你可以在计算机上做一些其他事情，比如看电影或浏览网页。此时你计算机使用的越频繁，密钥生成的速度越快。</p>
+ <p><span style="font-weight: bold;">当 "Key Generation Completed" （密钥已生成）窗口弹出，选中 Generate Certificate （生成证书）并选择把它储存在计算机上安全的地方（我们推荐新建一个名为 Revocation Certificate [吊销证书]的文件夹在你的家目录下，并把它保存在那里）。这是本指南重要的一步，你将会在 <a href="#section5">Section 5</a> 了解到更多信息。</span></p>
+
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>I can't find the Enigmail menu.</dt>
+ <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars. Enigmail may be inside a section called Tools.</dd>
+
+ <dt>My email looks weird</dt>
+ <dd>Enigmail doesn't tend to play nice with HTML, which is used to format emails, so it may disable your HTML formatting automatically. To send an HTML-formatted email without encryption or a signature, hold down the Shift key when you select compose. You can then write an email as if Enigmail wasn't there.</dd>
+
+ <dt>More resources</dt>
+ <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Key_Management#Generating_your_own_key_pair">Enigmail's wiki instructions for key generation</a>.</dd>
+
+
+
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+
+
+ <dt>Command line key generation</dt>
+ <dd>If you prefer using the command line for a higher degree of control, you can follow the documentation from <a href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy Handbook</a>. Make sure you stick with "RSA and RSA" (the default), because it's newer and more secure than the algorithms the documentation recommends. Also make sure your key is at least 2048 bits, or 4096 if you want to be extra secure.</dd>
+
+ <dt>Advanced key pairs</dt>
+ <dd>When GnuPG creates a new keypair, it compartmentalizes the encryption function from the signing function through <a href="https://wiki.debian.org/Subkeys">subkeys</a>. If you use subkeys carefully, you can keep your GnuPG identity much more secure and recover from a compromised key much more quickly. <a href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal</a> and <a href="http://keyring.debian.org/creating-key.html">the Debian wiki</a> provide good guides for setting up a secure subkey configuration.</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+ </div><!-- End #step-2a .step -->
+
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-2b" class="step">
+ <div class="main">
+ <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
+ <p>In your email program's menu, select Enigmail → Key Management.</p>
+ <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
+ <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>
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>The progress bar never finishes</dt>
+ <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>
+ <dt>My key doesn't appear in the list</dt>
+ <dd>Try checking "Display All Keys by Default."</dd>
+ <dt>More documentation</dt>
+ <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://www.enigmail.net/documentation/quickstart-ch2.php#id2533620">Enigmail's documentation</a>.</dd>
+
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+ <dt>Uploading a key from the command line</dt>
+ <dd>You can also upload your keys to a keyserver through the <a href="https://www.gnupg.org/gph/en/manual/x457.html">command line</a>. <a href="https://sks-keyservers.net/overview-of-pools.php">The sks Web site</a> maintains a list of highly interconnected keyservers. You can also <a href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export your key</a> as a file on your computer.</dd>
+
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+ </div><!-- End #step-2b .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="terminology" class="step">
+ <div class="main">
+ <h3>GnuPG, OpenPGP, what?</h3>
+ <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG) is the program that implements the standard. Enigmail is a plug-in program for your email program that provides an interface for GnuPG.</p>
+ </div><!-- End .main -->
+ </div><!-- End #terminology.step-->
+
+
+ </div>
+ </section><!-- End #section2 -->
+
+ <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
+ <section class="row" id="section3">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#3</em> Try it out!</h2>
+ <p>Now you'll try a test correspondence with a computer program named Edward, who knows how to use encryption. Except where noted, these are the same steps you'd follow when corresponding with a real, live person.</p>
+
+ <!-- <p>NOTE: Edward is currently having some technical difficulties, so he may take a long time to respond, or not respond at all. We're sorry about this and we're working hard to fix it. Your key will still work even without testing with Edward.</p> -->
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 3.a</em> Send Edward your public key</h3>
+ <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 Enigmail → 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>
+
+ <p>Address the message to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Put at least one word (whatever you want) in the subject and body of the email. Don't send yet.</p>
+
+ <p>The lock icon in the top left should be yellow, meaning encryption is
+ turned on. We want this first special message to be unencrypted, so
+ click the icon once to turn it off. The lock should become grey, with a
+ blue dot on it (to alert you that the setting has been changed from the
+ default). Once encryption is off, hit Send.</p>
+
+ <p class="notes">It may take two or three minutes for Edward 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 he'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>
+
+ <p>When you open Edward's reply, GnuPG may prompt you for your password before using your private key to decrypt it.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-3a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3b" class="step">
+ <div class="main">
+ <h3><em>Step 3.b</em> Send a test encrypted email</h3>
+ <p>Write a new email in your email program, addressed to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Make the subject "Encryption test" or something similar and write something in the body.</p>
+ <p>The lock icon in the top left of the window should be yellow, meaning encryption is on. This will be your default from now on.</p>
+ <p class="notes">Next to the lock, you'll notice an icon of a pencil. We'll get to this in a moment.</p>
+ <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
+
+ <p>To encrypt an email to Edward, you need his public key, so now you'll have Enigmail download it from a keyserver. Click Download Missing Keys and use the default in the pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key ID starting with C), then select ok. Select ok in the next pop-up.</p>
+
+ <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Check the box in front of Edward's key and click Send.</p>
+
+ <p class="notes">Since you encrypted this email with Edward's public key, Edward's private key is required to decrypt it. Edward is the only one with his private key, so no one except him can decrypt it.</p>
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>Enigmail can't find Edward's key</dt>
+ <dd>Close the pop-ups that have appeared since you clicked Send. 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>
+ <dt>Unscrambled messages in the Sent folder</dt>
+ <dd>Even though you can't decrypt messages encrypted to someone else's key, your email program will automatically save a copy encrypted to your public key, which you'll be able to view from the Sent folder like a normal email. This is normal, and it doesn't mean that your email was not sent encrypted.</dd>
+ <dt>More resources</dt>
+ <dd>If you're still having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Signature_and_Encryption#Encrypting_a_message">Enigmail's wiki</a>.</dd>
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+ <dt>Encrypt messages from the command line</dt>
+ <dd>You can also encrypt and decrypt messages and files from the <a href="https://www.gnupg.org/gph/en/manual/x110.html">command line</a>, if that's your preference. The option --armor makes the encrypted output appear in the regular character set.</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+
+ </div><!-- End .main -->
+ </div><!-- End #step-3b .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-headers_unencrypted" class="step">
+ <div class="main">
+ <h3><em>Important:</em> Security tips</h3>
+ <p>Even if you encrypt 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 a surveillance system can still figure out who you're communicating with. Also, surveillance agents will know that you're using GnuPG, even if they can't figure out what you're saying. When you send attachments, Enigmail will give you the choice to encrypt them or not, independent of the actual email.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-headers_unencrypted .step-->
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3c" class="step">
+ <div class="main">
+ <h3><em>Step 3.c</em> Receive a response</h3>
+ <p>When Edward receives your email, he will use his private key to decrypt it, then use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to encrypt his reply to you.</p>
+
+ <p class="notes">It may take two or three minutes for Edward 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>
+ <p>When you receive Edward'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>
+ <p>Notice the bar that Enigmail shows you above the message, with information about the status of Edward's key.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-3c .step -->
+
+
+ <div id="step-3d" class="step">
+ <div class="main">
+ <h3><em>Step 3.d</em> Send a test signed email</h3>
+ <p>GnuPG includes a way for you to sign messages and files, verifying that they came from you and that they weren't tampered with along the way. These signatures are stronger than their pen-and-paper cousins -- they're impossible to forge, because they're impossible to create without your private key (another reason to keep your private key safe).</p>
+
+ <p>You can sign messages to anyone, so it's a great way to make people aware that you use GnuPG and that they can communicate with you securely. If they don't have GnuPG, they will be able to read your message and see your signature. If they do have GnuPG, they'll also be able to verify that your signature is authentic.</p>
+
+ <p>To sign an email to Edward, compose any message to him and click the pencil icon next to the lock icon so that it turns gold. If you sign a message, GnuPG may ask you for your password before it sends the message, because it needs to unlock your private key for signing.</p>
+
+ <p>With the lock and pencil icons, you can choose whether each message will be encrypted, signed, both, or neither.</p>
+ </div>
+ </div>
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3e" class="step">
+ <div class="main">
+ <h3><em>Step 3.e</em> Receive a response</h3>
+ <p>When Edward receives your email, he will use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to verify that your signature is authentic and the message you sent has not been tampered with.</p>
+
+ <p class="notes">It may take two or three minutes for Edward 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>
+
+ <p>Edward's reply will arrive encrypted, because he prefers to use encryption whenever possible. If everything goes according to plan, it should say "Your signature was verified." If your test signed email was also encrypted, he will mention that first.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-3c .step -->
+ </div>
+ </section>
+
+
+ <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
+ <section class="row" id="section4">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#4</em> Learn the Web of Trust</h2>
+ <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>
+
+ <p>When you sign someone's key, you are publicly saying that you've verified that it belongs to them and not someone else.</p>
+
+ <p>Signing keys and signing messages use the same type of mathematical operation, but they carry very different implications. It's a good practice to generally sign your email, but if you casually sign people's keys, you may accidently end up vouching for the identity of an imposter.</p>
+
+ <p>People who use your public key can see who has signed it. Once you've used GnuPG for a long time, your key may have hundreds of signatures. You can consider a key to be more trustworthy if it has many signatures from people that you trust. The Web of Trust is a constellation of GnuPG users, connected to each other by chains of trust expressed through signatures.</p>
+
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-4a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 4.a</em> Sign a key</h3>
+ <p>In your email program's menu, go to Enigmail → Key Management.</p>
+ <p>Right click on Edward's public key and select Sign Key from the context menu.</p>
+ <p>In the window that pops up, select "I will not answer" and click ok.</p>
+ <p>Now you should be back at the Key Management menu. Select Keyserver → Upload Public Keys and hit ok.</p>
+ <p class="notes">You've just effectively said "I trust that Edward's public key actually belongs to Edward." This doesn't mean much because Edward isn't a real person, but it's good practice.</p>
+
+
+ <!--<div id="pgp-pathfinder">
+ <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
+ <p><strong>From:</strong> <input type="text" placeholder="xD41A008" name="FROM"></p>
+ <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
+ <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
+ </form>
+ </div>End #pgp-pathfinder -->
+
+ </div><!-- End .main -->
+ </div><!-- End #step-4a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-identify_keys" class="step">
+ <div class="main">
+ <h3>Identifying keys: Fingerprints and IDs</h3>
+ <p>People's public keys are usually identified by their key fingerprint, which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Edward's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to Enigmail → 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 people can double-check that they have the correct public key when they download yours from a keyserver.</p>
+
+ <p class="notes">You may also see public keys referred to by their key ID, which is simply the last eight digits of the fingerprint, like C09A61E8 for Edward. 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 you are trying to communicate to verify which one to use.</p>
+
+ </div><!-- End .main -->
+ </div><!-- End #step-sign_real_keys .step-->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="check-ids-before-signing" class="step">
+ <div class="main">
+ <h3><em>Important:</em> What to consider when signing keys</h3>
+ <p>Before signing a person's key, you need to be confident that it actually belongs to them, and that they are who they say they are. Ideally, this confidence comes from having interactions and conversations with them over time, and witnessing interactions between them and others. Whenever signing a key, ask to see the full public key fingerprint, and not just the shorter key ID. If you feel it's important to sign the key of someone you've just met, also ask them to show you their government identification, and make sure the name on the ID matches the name on the public key. 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>
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+ <dt>Master the Web of Trust</dt>
+ <dd>Unfortunately, trust does not spread between users the way <a href="http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people think</a>. One of best ways to strengthen the GnuPG community is to deeply <a href="https://www.gnupg.org/gph/en/manual/x334.html">understand</a> the Web of Trust and to carefully sign as many people's keys as circumstances permit.</dd>
+ <dt>Set ownertrust</dt>
+ <dd>If you trust someone enough to validate other people's keys, you can assign them an ownertrust level through Enigmails's key management window. Right click on the other person's key, go to the "Select Owner Trust" menu option, select the trustlevel and click OK. Only do this once you feel you have a deep understanding of the Web of Trust.</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+
+ </div><!-- End #step-sign_real_keys .step-->
+
+
+ </div>
+ </section><!-- End #section4 -->
+
+ <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
+ <section id="section5" class="row">
+ <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>
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-5a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well (1)" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3>When should I encrypt? When should I sign?</h3>
+
+ <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. 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>Unless you don't want to reveal your own identity (which requires other protective measures), there's no reason not to sign every message, whether or not you are encrypting. In addition to allowing those with GnuPG to verify that the message came from you, signing is a non-intrusive way to remind everyone that you use GnuPG and show support for secure communication. If you often send signed messages to people that aren't familiar with GnuPG, it's nice to also include a link to this guide in your standard email signature (the text kind, not the cryptographic kind).</p>
+
+ </div><!-- End .main -->
+ </div><!-- End #step-5a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-5b" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well (2)" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3>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 first encrypted email that Edward sent you. Because Edward encrypted it with your public key, it will have a message from Enigmail at the top, which most likely says "Enigmail: 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>
+ </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, not on a device you carry with you regularly.</p>
+ <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>
+ </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 or forge your signature. This guide doesn't cover how to revoke a key, but you can follow these <a href="https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions</a>. After you're done revoking, make a new key and send an email to everyone with whom you usually use your key to make sure they know, including a copy of your new key.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-lost_key .step-->
+
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <!---<div id="transfer-key" class="step">
+ <div class="main">
+ <h3>Transferring you key</h3>
+ <p>You can use Enigmail's <a href="https://www.enigmail.net/documentation/keyman.php">key management window</a> to import and export keys. If you want to be able to read your encrypted email on a different computer, you will need to export your secret key from here. Be warned, if you transfer the key without <a href="https://help.ubuntu.com/community/EncryptedFilesystemsOnRemovableStorage">encrypting</a> the drive it's on the transfer will be dramatically less secure.</p>
+ </div>--><!-- End .main -->
+ </div><!-- End #step-lost_key .step-->
+
+
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="webmail-and-GnuPG" class="step">
+ <div class="main">
+ <h3>Webmail and GnuPG</h3>
+ <p>When you use a web browser to access your email, you're using webmail, an email program stored on a distant website. Unlike webmail, your desktop email program runs on your own computer. Although webmail can't decrypt encrypted email, it will still display it in its encrypted form. If you primarily use webmail, you'll know to open your email client when you receive a scrambled email.</p>
+ </div><!-- End .main -->
+ </div><!-- End #webmail-and-GnuPG .step-->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
+ <div id="step-5d" class="step">
+ <div class="main">
+ <h3>Make your public key part of your online identity</h3>
+ <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>
+
+ <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>
+ </div>--><!-- End .main
+</div> End #step-5d .step-->
+
+
+</section><!-- End #section5 -->
+
+
+
+<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
+<section class="row" id="section6">
+ <div id="step-click_here" class="step">
+ <div class="main">
+ <h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2>
+
+ </div><!-- End .main -->
+ </div><!-- End #step-click_here .step-->
+
+</section><!-- End #section6 -->
+
+<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
+<!-- When un-commenting this section go to main.css and search
+for /* Guide Sections Background */ then add #faq to the desired color
+
+<section class="row" id="faq">
+<div>
+<div class="sidebar">
+<h2>FAQ</h2>
+</div>
+
+<div class="main">
+<dl>
+<dt>My key expired</dt>
+<dd>Answer coming soon.</dd>
+
+<dt>Who can read encrypted messages? Who can read signed ones?</dt>
+<dd>Answer coming soon.</dd>
+
+<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>
+<dd>Answer coming soon.</dd>
+</dl>
+</div>
+</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>Copyright © 2014-2016 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please support our work by <a href="https://u.fsf.org/yr">joining us as an associate member.</a></p>
+
+ <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>. Download the <a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">source code of Edward reply bot</a> by Andrew Engelbrecht <sudoman@ninthfloor.org> and Josh Drake <zamnedix@gnu.org>, available under the GNU Affero General Public License. <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
+
+ <p>Fonts used in the guide & 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ś, <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a> by Florian Cramer.</p>
+
+ <p>Download the <a href="emailselfdefense_source.zip">source package</a> for this guide, including fonts, image source files and the text of Edward's messages.</p>
+
+ <p>This site uses the Weblabels standard for labeling <a href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" rel="jslicense">source code and license information</a>.</p>
+ </div><!-- /#copyright -->
+ <p class="credits">
+ Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" alt="Journalism++" /></a>
+ </p><!-- /.credits -->
+ </div>
+</footer><!-- End #footer -->
+
+<script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
+<script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
+
+<!-- Piwik -->
+<script type="text/javascript" >
+// @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later
+var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");
+document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
+try {
+ var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13);
+ piwikTracker.trackPageView();
+ piwikTracker.enableLinkTracking();
+} catch( err ) {}
+// @license-end
+</script><noscript><p><img src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0" alt="" /></p></noscript>
+<!-- End Piwik Tracking Code -->
+
+
+
+</body>
+</html>
-<!DOCTYPE html>\r
-<html lang="zh-Hans">\r
-<head>\r
- <meta http-equiv="content-type" content="text/html; charset=utf-8" />\r
-\r
- <title>电子邮件加密傻瓜指南</title>\r
- <meta name="keywords" content="GnuPG, GPG, openpgp, 监控, 隐私, 电子邮件, Enigmail" />\r
- <meta name="description" content="电子邮件监控侵犯了我们的基本权利，并危及了言论自由。本指南将在40分钟里教会你如何通过GnuPG加密邮件。" />\r
-\r
- <meta name="viewport" content="width=device-width, initial-scale=1" />\r
- <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />\r
- <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />\r
-\r
-</head>\r
-<body>\r
-\r
-<h3 class="wip">Translation in Progress</h3>\r
-<p class="wip">The <a href="/esd-zh-hans.po">PO file</a> is where work is being done. Please help us if you can. Thanks!</p>\r
-\r
- <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->\r
-\r
- <header class="row" id="header">\r
- <div>\r
- <h1>电子邮件加密傻瓜指南</h1>\r
-\r
- <!-- Language list for browsers that do not have JS enabled -->\r
- <ul id="languages" class="os">\r
-<li><a href="/en">English - v4.0</a></li>\r
-<li><a href="/ar">العربية <span class="tip">tip</span></a></li>\r
-<li><a href="/cs">Čeština - v4.0</a></li>\r
-<li><a href="/de">Deutsch - v3.0</a></li>\r
-<li><a href="/el">ελληνικά - v3.0</a></li>\r
-<li><a href="/es">español - v4.0</a></li>\r
-<li><a href="/fa">فارسی - v4.0</a></li>\r
-<li><a href="/fr">français - v4.0</a></li>\r
-<li><a href="/it">italiano - v3.0</a></li>\r
-<li><a href="/ja">日本語 - v4.0</a></li>\r
-<li><a href="/ko">한국어 <span class="tip">tip</span></a></li>\r
-<li><a href="/ml">മലയാളം <span class="tip">tip</span></a></li>\r
-<li><a href="/pt-br">português do Brasil - v3.0</a></li>\r
-<li><a href="/ro">română - v3.0</a></li>\r
-<li><a href="/ru">русский - v4.0</a></li>\r
-<li><a href="/sq">Shqip - v4.0</a></li>\r
-<li><a href="/sv">svenska - v4.0</a></li>\r
-<li><a href="/tr">Türkçe - v4.0</a></li>\r
-<li><a class="current" href="/zh-hans">简体中文 <span class="tip">tip</span></a></li>\r
-<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide"><strong><span style="color: #2F5FAA;">帮助翻译</span></strong></a></li>\r
- </ul>\r
-\r
- <ul id="menu" class="os">\r
- <li class="spacer">\r
- <a href="index.html">GNU/Linux</a>\r
- </li>\r
- <li>\r
- <a href="mac.html">Mac OS</a>\r
- </li>\r
- <li>\r
- <a href="windows.html" class="current">Windows</a>\r
- </li>\r
- <li class="spacer"><a href="workshops.html">研讨会</a></li>\r
- <li class="spacer">\r
- <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">\r
- 分享 \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"\r
- class="share-logo" alt="[GNU Social]" /> \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"\r
- class="share-logo" alt="[Pump.io]" /> \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"\r
- class="share-logo" alt="[Reddit]" /> \r
- <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png"\r
- class="share-logo" alt="[Hacker News]" />\r
- </a>\r
- </li>\r
- </ul>\r
-\r
- <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->\r
- <div id="fsf-intro">\r
- <h3>\r
- <a href="http://u.fsf.org/ys">\r
- <img alt="Free Software Foundation"\r
- src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />\r
- </a>\r
- </h3>\r
- <div class="fsf-emphasis">\r
- <p>\r
- 我们为计算机用户的权利而战，并促进自由软件的开发，对抗大规模监控对我们至关重要。\r
- </p>\r
- <p>\r
- <strong>\r
- 请捐款以支持电子邮件加密指南。我们会一直改进它，使其充实，for the benefit of people around the world taking the first step towards protecting their privacy.\r
- </strong>\r
- </p>\r
- </div>\r
-\r
- <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a> </p>\r
-\r
- </div><!-- End #fsf-intro -->\r
-\r
- <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->\r
- <div class="intro">\r
- <p>\r
- <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png" alt="View & share our infographic →" /></a>大规模监控侵犯了我们的基本权利，并危及了言论自由。本指南将会教授你一个基本的监控自我保护技巧：加密电子邮件。一旦你学会了，你将能够收发其他人无法阅读的电子邮件，包括那些拦截你邮件的监控代理或窃贼。你需要的是一台带网络连接的计算机，一个电子邮箱账号，和大约四十分钟时间。</p>\r
-\r
- <p>即使你没有什么见不得人的事情，通过加密可以保护通信对方的隐私，并使大规模监控变得困难。如果你确实有重要的东西需要隐藏，那么你并不孤独；告密者们在揭发人权侵犯、腐败以及其他犯罪问题时，也是使用同样的工具保护他们身份的。</p>\r
-\r
- <p>除了使用加密技术，我们还需要坚持不懈地与监控作政治斗争，以政府减少<a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">对我们的大量数据收集</a>。但重中之重是保护好你自己，使得监控你的通讯尽可能的困难。本指南将帮助你做到。它是为初学者设计的，但如果你已经掌握了 GnuPG 的基本知识，或你是一位资深自由软件用户，你会喜欢进阶提示与<a href="workshops.html">加密探讨会指南</a>。</p>\r
-\r
- </div><!-- End .intro -->\r
-\r
- </div>\r
- </header><!-- End #header -->\r
-\r
- <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->\r
- <section class="row" id="section1">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#1</em> Get the pieces</h2>\r
- <p class="notes">本指南需要安装<a href="https://www.gnu.org/philosophy/free-sw.html">自由许可的</a>软件；它是完全透明的，任何人都可以复制它，并生成自己的版本。这使得它比专有软件（比如 Windows）更难受到监控。为了你免受监控，我们推荐你换用像 GNU/Linux 这样的自由软件操作系统。你可以在 <a href="https://u.fsf.org/ys">fsf.org</a> 上了解更多关于自由软件的信息。</p>\r
- <p>在开始之前，你需要安装 IceDove 电子邮件客户端。对于你的操作系统来说，IceDove 可能以其别名 Thunderbird 而为人所知。电子邮件程序是另一种访问邮箱账号的途径（你也可以像 Gmail 那样通过浏览器访问），但它提供了更多的功能。</p>\r
- <p>如果你已经安装好了邮件程序，请跳至 <a href="#step-1b">Step 1.b</a>。</p>\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-1a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 1.a</em> 设置邮箱账号</h3>\r
- <p>打开你的邮件程序，按照向导程序的提示逐步设置好你的邮箱账号。</p>\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>The wizard doesn't launch</dt>\r
- <dd>You can launch the wizard yourself, but the menu option for doing so is named differently in each email programs. The button to launch it will be in the program's main menu, under "New" or something similar, titled something like "Add account" or "New/Existing email account."</dd>\r
- <dt>The wizard can't find my account or isn't downloading my mail</dt>\r
- <dd>Before searching the Web, we recommend you start by asking other people who use your email system, to figure out the correct settings.</dd>\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step1-a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-1b" class="step">\r
-\r
- <div class="main">\r
- <h3><em>Step 1.b</em> 下载 GPG4Win</h3>\r
- <p>GPG4Win 是一个包含了 GnuPG 的软件包。<a href="https://www.gpg4win.org/">下载</a>并安装它，选择默认选项无论提示什么。安装完成后关闭窗口。</p>\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step1-b .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-1c" class="step">\r
- <div class="sidebar">\r
- <ul class="images">\r
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png" alt="Step 1.C: Tools -> Add-ons" /></li>\r
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png" alt="Step 1.C: Search Add-ons" /></li>\r
- <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png" alt="Step 1.C: Install Add-ons" /></li>\r
- </ul>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 1.c</em> 安装 ENIGMAIL 插件</h3>\r
- <p>在邮件程序的菜单栏里，选择“附加组件”（Add-ons，它可能在工具选项里）。确认选上了左侧的“扩展”（Extensions）。看到了 Enigmail 吗？如果是，请跳过此步。</p>\r
- <p>如果没有，在右上方的搜索框里搜索“Enigmail”。你可以在这里获取到它。安装完成后重启邮件程序。</p>\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>I can't find the menu.</dt>\r
- <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars.</dd>\r
-\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
- </div><!-- End #step-1c .step -->\r
- </div>\r
- </section><!-- End #section1 -->\r
-\r
- <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->\r
- <section class="row" id="section2">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#2</em> 生成密钥</h2>\r
- <p>要使用 GnuPG 体系，你将会用到一把公钥（public key）和一把私钥（private key），他们合称为密钥对（keypair）。每一把都是随机生成的一长串数字和字母的值，它是独一无二的。你的公钥和私钥由一种特殊的数学函数联系在一起。</p>\r
-\r
- <p>你的公钥不太像现实中的钥匙，它公开储存在被称之为密钥服务器（keyserver）的在线目录上。人们可以下载使用它，借助 GnuPG，人们向你发送加密邮件。你可以把密钥服务器想象成一本电话簿；想要给你发送加密邮件的人能够找到你的公钥。</p>\r
-\r
- <p>你的私钥更像是现实中的钥匙，你需要自行保管它（在你的计算机中）。你可以使用 GnuPG 和你的私钥来解密他人发给你的加密邮件。<span style="font-weight: bold;">无论如何，你都不应该改向他人分享你的私钥。</span></p>\r
- <p>除了加密和解密，你可以使用这些密钥对消息进行签名，并检查其他人签名的真实性。我们将在下一节里详细探讨它。</p>\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-2a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 2.a</em> 生成密钥对</h3>\r
- <p>Enigmail 安装向导可能会自动运行。如果没有，在你的邮件程序你选择 Enigmail → Setup Wizard。如果你不愿意，你不必去阅读弹出窗口中的文字，但读一读总归是好的。点击下一步而不对默认选项作修改，但除了下列情况以外：</p>\r
- <ul>\r
- <li>在“加密”（Encryption）界面，选中“默认加密所有我的消息，因为隐私对我很重要”（Encrypt all of my messages by default, because privacy is critical to me）。</li>\r
- <li>在“签名”（Signing）界面，选中“默认不对我的消息签名”（Don't sign my messages by default）。</li>\r
- <li>在“密钥选择”（Key Selection）界面，选择“我想为数字签名和加密邮件创建新密钥对”（I want to create a new key pair for signing and encrypting my email）。</li>\r
- <li>在“创建密钥”（Create Key）界面。取一个强壮的密码吧！你可以自行取密码，也可以使用 Diceware 模式。自己取密码虽然快速，但不安全。使用 Diceware 需要更长时间 and requires dice,但能生成攻击者难以辨识出的密码。要使用它，请阅读 Micah Lee 写的<a href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">这篇文章</a>的 Make a secure passphrase with Diceware 一节。</li>\r
- </ul>\r
-\r
- <p>如果你喜欢自己取密码，想一个你记得起的至少十二字符长的东西，至少包含一个小写和大写字母，和一个数字或标点符号。永远不要使用你其他地方使用过的密码。不用使用任何可辨识的模式，诸如生日、电话号码、宠物名字、歌词或书中的引言。</p>\r
-\r
- <p class="notes">在“生成密钥”（Key Creation）界面，程序需要花费小会儿完成下一步。等待时，你可以在计算机上做一些其他事情，比如看电影或浏览网页。此时你计算机使用的越频繁，密钥生成的速度越快。</p>\r
- <p><span style="font-weight: bold;">当 "Key Generation Completed" （密钥已生成）窗口弹出，选中 Generate Certificate （生成证书）并选择把它储存在计算机上安全的地方（我们推荐新建一个名为 Revocation Certificate [吊销证书]的文件夹在你的家目录下，并把它保存在那里）。这是本指南重要的一步，你将会在 <a href="#section5">Section 5</a> 了解到更多信息。</span></p>\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>I can't find the Enigmail menu.</dt>\r
- <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars. Enigmail may be inside a section called Tools.</dd>\r
-\r
- <dt>More resources</dt>\r
- <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Key_Management#Generating_your_own_key_pair">Enigmail's wiki instructions for key generation</a>.</dd>\r
-\r
- <dt>My email looks weird</dt>\r
- <dd>Enigmail doesn't tend to play nice with HTML, which is used to format emails, so it may disable your HTML formatting automatically. To send an HTML-formatted email without encryption or a signature, hold down the Shift key when you select compose. You can then write an email as if Enigmail wasn't there.</dd>\r
-\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
-\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
- <dt>Command line key generation</dt>\r
- <dd>If you prefer using the command line for a higher degree of control, you can follow the documentation from <a href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy Handbook</a>. Make sure you stick with "RSA and RSA" (the default), because it's newer and more secure than the algorithms the documentation recommends. Also make sure your key is at least 2048 bits, or 4096 if you want to be extra secure.</dd>\r
-\r
- <dt>Advanced key pairs</dt>\r
- <dd>When GnuPG creates a new keypair, it compartmentalizes the encryption function from the signing function through <a href="https://wiki.debian.org/Subkeys">subkeys</a>. If you use subkeys carefully, you can keep your GnuPG identity much more secure and recover from a compromised key much more quickly. <a href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal</a> and <a href="http://keyring.debian.org/creating-key.html">the Debian wiki</a> provide good guides for setting up a secure subkey configuration.</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
- </div><!-- End #step-2a .step -->\r
-\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-2b" class="step">\r
- <div class="main">\r
- <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>\r
- <p>In your email program's menu, select Enigmail → Key Management.</p>\r
- <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>\r
- <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>\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>The progress bar never finishes</dt>\r
- <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>\r
- <dt>My key doesn't appear in the list</dt>\r
- <dd>Try checking "Display All Keys by Default."</dd>\r
- <dt>More documentation</dt>\r
- <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://www.enigmail.net/documentation/quickstart-ch2.php#id2533620">Enigmail's documentation</a>.</dd>\r
-\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
-\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
- <dt>Uploading a key from the command line</dt>\r
- <dd>You can also upload your keys to a keyserver through the <a href="https://www.gnupg.org/gph/en/manual/x457.html">command line</a>. <a href="https://sks-keyservers.net/overview-of-pools.php">The sks Web site</a> maintains a list of highly interconnected keyservers. You can also <a href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export your key</a> as a file on your computer.</dd>\r
-\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
- </div><!-- End #step-2b .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="terminology" class="step">\r
- <div class="main">\r
- <h3>GnuPG, OpenPGP, what?</h3>\r
- <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG) is the program that implements the standard. Enigmail is a plug-in program for your email program that provides an interface for GnuPG.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #terminology.step-->\r
-\r
-\r
- </div>\r
- </section><!-- End #section2 -->\r
-\r
- <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->\r
- <section class="row" id="section3">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#3</em> Try it out!</h2>\r
- <p>Now you'll try a test correspondence with a computer program named Edward, who knows how to use encryption. Except where noted, these are the same steps you'd follow when corresponding with a real, live person.</p>\r
-\r
- <!-- <p>NOTE: Edward is currently having some technical difficulties, so he may take a long time to respond, or not respond at all. We're sorry about this and we're working hard to fix it. Your key will still work even without testing with Edward.</p> -->\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png" alt="Try it out." /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 3.a</em> Send Edward your public key</h3>\r
- <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 Enigmail → 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>\r
-\r
- <p>Address the message to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Put at least one word (whatever you want) in the subject and body of the email. Don't send yet.</p>\r
-\r
- <p>The lock icon in the top left should be yellow, meaning encryption is\r
- turned on. We want this first special message to be unencrypted, so\r
- click the icon once to turn it off. The lock should become grey, with a\r
- blue dot on it (to alert you that the setting has been changed from the\r
- default). Once encryption is off, hit Send.</p>\r
-\r
- <p class="notes">It may take two or three minutes for Edward 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 he'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>\r
-\r
- <p>When you open Edward's reply, GnuPG may prompt you for your password before using your private key to decrypt it.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3b" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.b</em> Send a test encrypted email</h3>\r
- <p>Write a new email in your email program, addressed to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Make the subject "Encryption test" or something similar and write something in the body.</p>\r
- <p>The lock icon in the top left of the window should be yellow, meaning encryption is on. This will be your default from now on.</p>\r
- <p class="notes">Next to the lock, you'll notice an icon of a pencil. We'll get to this in a moment.</p>\r
- <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>\r
-\r
- <p>To encrypt an email to Edward, you need his public key, so now you'll have Enigmail download it from a keyserver. Click Download Missing Keys and use the default in the pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key ID starting with C), then select ok. Select ok in the next pop-up.</p>\r
-\r
- <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Check the box in front of Edward's key and click Send.</p>\r
-\r
- <p class="notes">Since you encrypted this email with Edward's public key, Edward's private key is required to decrypt it. Edward is the only one with his private key, so no one except him can decrypt it.</p>\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>疑难解答</h4>\r
- <dl>\r
- <dt>Enigmail can't find Edward's key</dt>\r
- <dd>Close the pop-ups that have appeared since you clicked Send. 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>\r
- <dt>Unscrambled messages in the Sent folder</dt>\r
- <dd>Even though you can't decrypt messages encrypted to someone else's key, your email program will automatically save a copy encrypted to your public key, which you'll be able to view from the Sent folder like a normal email. This is normal, and it doesn't mean that your email was not sent encrypted.</dd>\r
- <dt>More resources</dt>\r
- <dd>If you're still having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Signature_and_Encryption#Encrypting_a_message">Enigmail's wiki</a>.</dd>\r
- <dt class="feedback">没有得到解答？</dt>\r
- <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
- <dt>Encrypt messages from the command line</dt>\r
- <dd>You can also encrypt and decrypt messages and files from the <a href="https://www.gnupg.org/gph/en/manual/x110.html">command line</a>, if that's your preference. The option --armor makes the encrypted output appear in the regular character set.</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
-\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3b .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-headers_unencrypted" class="step">\r
- <div class="main">\r
- <h3><em>Important:</em> Security tips</h3>\r
- <p>Even if you encrypt 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 a surveillance system can still figure out who you're communicating with. Also, surveillance agents will know that you're using GnuPG, even if they can't figure out what you're saying. When you send attachments, Enigmail will give you the choice to encrypt them or not, independent of the actual email.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-headers_unencrypted .step-->\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3c" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.c</em> Receive a response</h3>\r
- <p>When Edward receives your email, he will use his private key to decrypt it, then use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to encrypt his reply to you.</p>\r
-\r
- <p class="notes">It may take two or three minutes for Edward 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>\r
- <p>When you receive Edward'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>\r
- <p>Notice the bar that Enigmail shows you above the message, with information about the status of Edward's key.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3c .step -->\r
-\r
-\r
- <div id="step-3d" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.d</em> Send a test signed email</h3>\r
- <p>GnuPG includes a way for you to sign messages and files, verifying that they came from you and that they weren't tampered with along the way. These signatures are stronger than their pen-and-paper cousins -- they're impossible to forge, because they're impossible to create without your private key (another reason to keep your private key safe).</p>\r
-\r
- <p>You can sign messages to anyone, so it's a great way to make people aware that you use GnuPG and that they can communicate with you securely. If they don't have GnuPG, they will be able to read your message and see your signature. If they do have GnuPG, they'll also be able to verify that your signature is authentic.</p>\r
-\r
- <p>To sign an email to Edward, compose any message to him and click the pencil icon next to the lock icon so that it turns gold. If you sign a message, GnuPG may ask you for your password before it sends the message, because it needs to unlock your private key for signing.</p>\r
-\r
- <p>With the lock and pencil icons, you can choose whether each message will be encrypted, signed, both, or neither.</p>\r
- </div>\r
- </div>\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-3e" class="step">\r
- <div class="main">\r
- <h3><em>Step 3.e</em> Receive a response</h3>\r
- <p>When Edward receives your email, he will use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to verify that your signature is authentic and the message you sent has not been tampered with.</p>\r
-\r
- <p class="notes">It may take two or three minutes for Edward 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>\r
-\r
- <p>Edward's reply will arrive encrypted, because he prefers to use encryption whenever possible. If everything goes according to plan, it should say "Your signature was verified." If your test signed email was also encrypted, he will mention that first.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-3c .step -->\r
- </div>\r
- </section>\r
-\r
-\r
- <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->\r
- <section class="row" id="section4">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#4</em> Learn the Web of Trust</h2>\r
- <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>\r
-\r
- <p>When you sign someone's key, you are publicly saying that you've verified that it belongs to them and not someone else.</p>\r
-\r
- <p>Signing keys and signing messages use the same type of mathematical operation, but they carry very different implications. It's a good practice to generally sign your email, but if you casually sign people's keys, you may accidently end up vouching for the identity of an imposter.</p>\r
-\r
- <p>People who use your public key can see who has signed it. Once you've used GnuPG for a long time, your key may have hundreds of signatures. You can consider a key to be more trustworthy if it has many signatures from people that you trust. The Web of Trust is a constellation of GnuPG users, connected to each other by chains of trust expressed through signatures.</p>\r
-\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-4a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3><em>Step 4.a</em> Sign a key</h3>\r
- <p>In your email program's menu, go to Enigmail → Key Management.</p>\r
- <p>Right click on Edward's public key and select Sign Key from the context menu.</p>\r
- <p>In the window that pops up, select "I will not answer" and click ok.</p>\r
- <p>Now you should be back at the Key Management menu. Select Keyserver → Upload Public Keys and hit ok.</p>\r
- <p class="notes">You've just effectively said "I trust that Edward's public key actually belongs to Edward." This doesn't mean much because Edward isn't a real person, but it's good practice.</p>\r
-\r
-\r
- <!--<div id="pgp-pathfinder">\r
- <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">\r
- <p><strong>From:</strong> <input type="text" placeholder="xD41A008" name="FROM"></p>\r
- <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>\r
- <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>\r
- </form>\r
- </div>End #pgp-pathfinder -->\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-4a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-identify_keys" class="step">\r
- <div class="main">\r
- <h3>Identifying keys: Fingerprints and IDs</h3>\r
- <p>People's public keys are usually identified by their key fingerprint, which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Edward's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to Enigmail → 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 people can double-check that they have the correct public key when they download yours from a keyserver.</p>\r
-\r
- <p class="notes">You may also see public keys referred to by their key ID, which is simply the last eight digits of the fingerprint, like C09A61E8 for Edward. 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 you are trying to communicate to verify which one to use.</p>\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-sign_real_keys .step-->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="check-ids-before-signing" class="step">\r
- <div class="main">\r
- <h3><em>Important:</em> What to consider when signing keys</h3>\r
- <p>Before signing a person's key, you need to be confident that it actually belongs to them, and that they are who they say they are. Ideally, this confidence comes from having interactions and conversations with them over time, and witnessing interactions between them and others. Whenever signing a key, ask to see the full public key fingerprint, and not just the shorter key ID. If you feel it's important to sign the key of someone you've just met, also ask them to show you their government identification, and make sure the name on the ID matches the name on the public key. 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?"\r
-</p>\r
-\r
- <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->\r
- <div class="troubleshooting">\r
- <h4>Advanced</h4>\r
- <dl>\r
- <dt>Master the Web of Trust</dt>\r
- <dd>Unfortunately, trust does not spread between users the way <a href="http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people think</a>. One of best ways to strengthen the GnuPG community is to deeply <a href="https://www.gnupg.org/gph/en/manual/x334.html">understand</a> the Web of Trust and to carefully sign as many people's keys as circumstances permit.</dd>\r
- <dt>Set ownertrust</dt>\r
- <dd>If you trust someone enough to validate other people's keys, you can assign them an ownertrust level through Enigmails's key management window. Right click on the other person's key, go to the "Select Owner Trust" menu option, select the trustlevel and click OK. Only do this once you feel you have a deep understanding of the Web of Trust.</dd>\r
- </dl>\r
- </div><!-- /.troubleshooting -->\r
- </div><!-- End .main -->\r
-\r
- </div><!-- End #step-sign_real_keys .step-->\r
-\r
-\r
- </div>\r
- </section><!-- End #section4 -->\r
-\r
- <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->\r
- <section id="section5" class="row">\r
- <div>\r
- <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->\r
- <div class="section-intro">\r
- <h2><em>#5</em> Use it well</h2>\r
- <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>\r
- </div><!-- End .section-intro -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-5a" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well (1)" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3>When should I encrypt? When should I sign?</h3>\r
-\r
- <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. 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>\r
- <p>Unless you don't want to reveal your own identity (which requires other protective measures), there's no reason not to sign every message, whether or not you are encrypting. In addition to allowing those with GnuPG to verify that the message came from you, signing is a non-intrusive way to remind everyone that you use GnuPG and show support for secure communication. If you often send signed messages to people that aren't familiar with GnuPG, it's nice to also include a link to this guide in your standard email signature (the text kind, not the cryptographic kind).</p>\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-5a .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-5b" class="step">\r
- <div class="sidebar">\r
- <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well (2)" /></p>\r
- </div><!-- /.sidebar -->\r
- <div class="main">\r
- <h3>Be wary of invalid keys</h3>\r
- <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>\r
- <p>In your email program, go back to the first encrypted email that Edward sent you. Because Edward encrypted it with your public key, it will have a message from Enigmail at the top, which most likely says "Enigmail: Part of this message encrypted."</p>\r
- <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>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-5b .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-5c" class="step">\r
- <div class="main">\r
- <h3>Copy your revocation certificate to somewhere safe</h3>\r
- <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, not on a device you carry with you regularly.</p>\r
- <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>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-5c .step -->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="step-lost_key" class="step">\r
- <div class="main">\r
- <h3><em>Important:</em> act swiftly if someone gets your private key</h3>\r
- <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 or forge your signature. This guide doesn't cover how to revoke a key, but you can follow these <a href="https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions</a>. After you're done revoking, make a new key and send an email to everyone with whom you usually use your key to make sure they know, including a copy of your new key.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #step-lost_key .step-->\r
-\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <!---<div id="transfer-key" class="step">\r
- <div class="main">\r
- <h3>Transferring you key</h3>\r
- <p>You can use Enigmail's <a href="https://www.enigmail.net/documentation/keyman.php">key management window</a> to import and export keys. If you want to be able to read your encrypted email on a different computer, you will need to export your secret key from here. Be warned, if you transfer the key without <a href="https://help.ubuntu.com/community/EncryptedFilesystemsOnRemovableStorage">encrypting</a> the drive it's on the transfer will be dramatically less secure.</p>\r
- </div>--><!-- End .main -->\r
- </div><!-- End #step-lost_key .step-->\r
-\r
-\r
-\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->\r
- <div id="webmail-and-GnuPG" class="step">\r
- <div class="main">\r
- <h3>Webmail and GnuPG</h3>\r
- <p>When you use a web browser to access your email, you're using webmail, an email program stored on a distant website. Unlike webmail, your desktop email program runs on your own computer. Although webmail can't decrypt encrypted email, it will still display it in its encrypted form. If you primarily use webmail, you'll know to open your email client when you receive a scrambled email.</p>\r
- </div><!-- End .main -->\r
- </div><!-- End #webmail-and-GnuPG .step-->\r
-\r
- <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~\r
- <div id="step-5d" class="step">\r
- <div class="main">\r
- <h3>Make your public key part of your online identity</h3>\r
- <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>\r
-\r
- <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>\r
- </div>--><!-- End .main\r
-</div> End #step-5d .step-->\r
-\r
-\r
-</section><!-- End #section5 -->\r
-\r
-\r
-\r
-<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->\r
-<section class="row" id="section6">\r
- <div id="step-click_here" class="step">\r
- <div class="main">\r
- <h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2>\r
-\r
- </div><!-- End .main -->\r
- </div><!-- End #step-click_here .step-->\r
-\r
-</section><!-- End #section6 -->\r
-\r
-<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->\r
-<!-- When un-commenting this section go to main.css and search\r
-for /* Guide Sections Background */ then add #faq to the desired color\r
-\r
-<section class="row" id="faq">\r
-<div>\r
-<div class="sidebar">\r
-<h2>FAQ</h2>\r
-</div>\r
-\r
-<div class="main">\r
-<dl>\r
-<dt>My key expired</dt>\r
-<dd>Answer coming soon.</dd>\r
-\r
-<dt>Who can read encrypted messages? Who can read signed ones?</dt>\r
-<dd>Answer coming soon.</dd>\r
-\r
-<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>\r
-<dd>Answer coming soon.</dd>\r
-</dl>\r
-</div>\r
-</div>\r
-</section> --><!-- End #faq -->\r
-\r
-<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->\r
-<footer class="row" id="footer">\r
- <div>\r
- <div id="copyright">\r
- <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>\r
- <p>Copyright © 2014-2016 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please support our work by <a href="https://u.fsf.org/yr">joining us as an associate member.</a></p>\r
-\r
- <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>. Download the <a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">source code of Edward reply bot</a> by Andrew Engelbrecht <sudoman@ninthfloor.org> and Josh Drake <zamnedix@gnu.org>, available under the GNU Affero General Public License. <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>\r
-\r
- <p>Fonts used in the guide & 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ś, <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a> by Florian Cramer.</p>\r
-\r
- <p>Download the <a href="emailselfdefense_source.zip">source package</a> for this guide, including fonts, image source files and the text of Edward's messages.</p>\r
-\r
- <p>This site uses the Weblabels standard for labeling <a href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" rel="jslicense">source code and license information</a>.</p>\r
- </div><!-- /#copyright -->\r
- <p class="credits">\r
- Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" alt="Journalism++" /></a>\r
- </p><!-- /.credits -->\r
- </div>\r
-</footer><!-- End #footer -->\r
-\r
-<script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>\r
-<script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>\r
-\r
-<!-- Piwik -->\r
-<script type="text/javascript" >\r
-// @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later\r
-var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");\r
-document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));\r
-try {\r
- var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13);\r
- piwikTracker.trackPageView();\r
- piwikTracker.enableLinkTracking();\r
-} catch( err ) {}\r
-// @license-end\r
-</script><noscript><p><img src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0" alt="" /></p></noscript>\r
-<!-- End Piwik Tracking Code -->\r
-\r
-\r
-\r
-</body>\r
-</html>\r
+<!DOCTYPE html>
+<html lang="zh-Hans">
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=utf-8" />
+
+ <title>电子邮件加密傻瓜指南</title>
+ <meta name="keywords" content="GnuPG, GPG, openpgp, 监控, 隐私, 电子邮件, Enigmail" />
+ <meta name="description" content="电子邮件监控侵犯了我们的基本权利，并危及了言论自由。本指南将在40分钟里教会你如何通过GnuPG加密邮件。" />
+
+ <meta name="viewport" content="width=device-width, initial-scale=1" />
+ <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />
+ <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
+
+</head>
+<body>
+
+<h3 class="wip">Translation in Progress</h3>
+<p class="wip">The <a href="/esd-zh-hans.po">PO file</a> is where work is being done. Please help us if you can. Thanks!</p>
+
+ <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
+
+ <header class="row" id="header">
+ <div>
+ <h1>电子邮件加密傻瓜指南</h1>
+
+ <!-- Language list for browsers that do not have JS enabled -->
+ <ul id="languages" class="os">
+<li><a href="/en">English - v4.0</a></li>
+<li><a href="/ar">العربية <span class="tip">tip</span></a></li>
+<li><a href="/cs">Čeština - v4.0</a></li>
+<li><a href="/de">Deutsch - v3.0</a></li>
+<li><a href="/el">ελληνικά - v3.0</a></li>
+<li><a href="/es">español - v4.0</a></li>
+<li><a href="/fa">فارسی - v4.0</a></li>
+<li><a href="/fr">français - v4.0</a></li>
+<li><a href="/it">italiano - v3.0</a></li>
+<li><a href="/ja">日本語 - v4.0</a></li>
+<li><a href="/ko">한국어 <span class="tip">tip</span></a></li>
+<li><a href="/ml">മലയാളം <span class="tip">tip</span></a></li>
+<li><a href="/pt-br">português do Brasil - v3.0</a></li>
+<li><a href="/ro">română - v3.0</a></li>
+<li><a href="/ru">русский - v4.0</a></li>
+<li><a href="/sq">Shqip - v4.0</a></li>
+<li><a href="/sv">svenska - v4.0</a></li>
+<li><a href="/tr">Türkçe - v4.0</a></li>
+<li><a class="current" href="/zh-hans">简体中文 <span class="tip">tip</span></a></li>
+<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide"><strong><span style="color: #2F5FAA;">帮助翻译</span></strong></a></li>
+ </ul>
+
+ <ul id="menu" class="os">
+ <li class="spacer">
+ <a href="index.html">GNU/Linux</a>
+ </li>
+ <li>
+ <a href="mac.html">Mac OS</a>
+ </li>
+ <li>
+ <a href="windows.html" class="current">Windows</a>
+ </li>
+ <li class="spacer"><a href="workshops.html">研讨会</a></li>
+ <li class="spacer">
+ <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">
+ 分享
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"
+ class="share-logo" alt="[GNU Social]" />
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"
+ class="share-logo" alt="[Pump.io]" />
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"
+ class="share-logo" alt="[Reddit]" />
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png"
+ class="share-logo" alt="[Hacker News]" />
+ </a>
+ </li>
+ </ul>
+
+ <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
+ <div id="fsf-intro">
+ <h3>
+ <a href="http://u.fsf.org/ys">
+ <img alt="Free Software Foundation"
+ src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />
+ </a>
+ </h3>
+ <div class="fsf-emphasis">
+ <p>
+ 我们为计算机用户的权利而战，并促进自由软件的开发，对抗大规模监控对我们至关重要。
+ </p>
+ <p>
+ <strong>
+ 请捐款以支持电子邮件加密指南。我们会一直改进它，使其充实，for the benefit of people around the world taking the first step towards protecting their privacy.
+ </strong>
+ </p>
+ </div>
+
+ <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a> </p>
+
+ </div><!-- End #fsf-intro -->
+
+ <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
+ <div class="intro">
+ <p>
+ <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png" alt="View & share our infographic →" /></a>大规模监控侵犯了我们的基本权利，并危及了言论自由。本指南将会教授你一个基本的监控自我保护技巧：加密电子邮件。一旦你学会了，你将能够收发其他人无法阅读的电子邮件，包括那些拦截你邮件的监控代理或窃贼。你需要的是一台带网络连接的计算机，一个电子邮箱账号，和大约四十分钟时间。</p>
+
+ <p>即使你没有什么见不得人的事情，通过加密可以保护通信对方的隐私，并使大规模监控变得困难。如果你确实有重要的东西需要隐藏，那么你并不孤独；告密者们在揭发人权侵犯、腐败以及其他犯罪问题时，也是使用同样的工具保护他们身份的。</p>
+
+ <p>除了使用加密技术，我们还需要坚持不懈地与监控作政治斗争，以政府减少<a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">对我们的大量数据收集</a>。但重中之重是保护好你自己，使得监控你的通讯尽可能的困难。本指南将帮助你做到。它是为初学者设计的，但如果你已经掌握了 GnuPG 的基本知识，或你是一位资深自由软件用户，你会喜欢进阶提示与<a href="workshops.html">加密探讨会指南</a>。</p>
+
+ </div><!-- End .intro -->
+
+ </div>
+ </header><!-- End #header -->
+
+ <!-- ~~~~~~~~~ Section 1: Get the pieces ~~~~~~~~~ -->
+ <section class="row" id="section1">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#1</em> Get the pieces</h2>
+ <p class="notes">本指南需要安装<a href="https://www.gnu.org/philosophy/free-sw.html">自由许可的</a>软件；它是完全透明的，任何人都可以复制它，并生成自己的版本。这使得它比专有软件（比如 Windows）更难受到监控。为了你免受监控，我们推荐你换用像 GNU/Linux 这样的自由软件操作系统。你可以在 <a href="https://u.fsf.org/ys">fsf.org</a> 上了解更多关于自由软件的信息。</p>
+ <p>在开始之前，你需要安装 IceDove 电子邮件客户端。对于你的操作系统来说，IceDove 可能以其别名 Thunderbird 而为人所知。电子邮件程序是另一种访问邮箱账号的途径（你也可以像 Gmail 那样通过浏览器访问），但它提供了更多的功能。</p>
+ <p>如果你已经安装好了邮件程序，请跳至 <a href="#step-1b">Step 1.b</a>。</p>
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-1a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 1.a</em> 设置邮箱账号</h3>
+ <p>打开你的邮件程序，按照向导程序的提示逐步设置好你的邮箱账号。</p>
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>The wizard doesn't launch</dt>
+ <dd>You can launch the wizard yourself, but the menu option for doing so is named differently in each email programs. The button to launch it will be in the program's main menu, under "New" or something similar, titled something like "Add account" or "New/Existing email account."</dd>
+ <dt>The wizard can't find my account or isn't downloading my mail</dt>
+ <dd>Before searching the Web, we recommend you start by asking other people who use your email system, to figure out the correct settings.</dd>
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+ </div><!-- End .main -->
+ </div><!-- End #step1-a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-1b" class="step">
+
+ <div class="main">
+ <h3><em>Step 1.b</em> 下载 GPG4Win</h3>
+ <p>GPG4Win 是一个包含了 GnuPG 的软件包。<a href="https://www.gpg4win.org/">下载</a>并安装它，选择默认选项无论提示什么。安装完成后关闭窗口。</p>
+
+ </div><!-- End .main -->
+ </div><!-- End #step1-b .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-1c" class="step">
+ <div class="sidebar">
+ <ul class="images">
+ <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-01-tools-addons.png" alt="Step 1.C: Tools -> Add-ons" /></li>
+ <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-02-search.png" alt="Step 1.C: Search Add-ons" /></li>
+ <li><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1b-03-install.png" alt="Step 1.C: Install Add-ons" /></li>
+ </ul>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 1.c</em> 安装 ENIGMAIL 插件</h3>
+ <p>在邮件程序的菜单栏里，选择“附加组件”（Add-ons，它可能在工具选项里）。确认选上了左侧的“扩展”（Extensions）。看到了 Enigmail 吗？如果是，请跳过此步。</p>
+ <p>如果没有，在右上方的搜索框里搜索“Enigmail”。你可以在这里获取到它。安装完成后重启邮件程序。</p>
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>I can't find the menu.</dt>
+ <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars.</dd>
+
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+ </div><!-- End #step-1c .step -->
+ </div>
+ </section><!-- End #section1 -->
+
+ <!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
+ <section class="row" id="section2">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#2</em> 生成密钥</h2>
+ <p>要使用 GnuPG 体系，你将会用到一把公钥（public key）和一把私钥（private key），他们合称为密钥对（keypair）。每一把都是随机生成的一长串数字和字母的值，它是独一无二的。你的公钥和私钥由一种特殊的数学函数联系在一起。</p>
+
+ <p>你的公钥不太像现实中的钥匙，它公开储存在被称之为密钥服务器（keyserver）的在线目录上。人们可以下载使用它，借助 GnuPG，人们向你发送加密邮件。你可以把密钥服务器想象成一本电话簿；想要给你发送加密邮件的人能够找到你的公钥。</p>
+
+ <p>你的私钥更像是现实中的钥匙，你需要自行保管它（在你的计算机中）。你可以使用 GnuPG 和你的私钥来解密他人发给你的加密邮件。<span style="font-weight: bold;">无论如何，你都不应该改向他人分享你的私钥。</span></p>
+ <p>除了加密和解密，你可以使用这些密钥对消息进行签名，并检查其他人签名的真实性。我们将在下一节里详细探讨它。</p>
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-2a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 2.a</em> 生成密钥对</h3>
+ <p>Enigmail 安装向导可能会自动运行。如果没有，在你的邮件程序你选择 Enigmail → Setup Wizard。如果你不愿意，你不必去阅读弹出窗口中的文字，但读一读总归是好的。点击下一步而不对默认选项作修改，但除了下列情况以外：</p>
+ <ul>
+ <li>在“加密”（Encryption）界面，选中“默认加密所有我的消息，因为隐私对我很重要”（Encrypt all of my messages by default, because privacy is critical to me）。</li>
+ <li>在“签名”（Signing）界面，选中“默认不对我的消息签名”（Don't sign my messages by default）。</li>
+ <li>在“密钥选择”（Key Selection）界面，选择“我想为数字签名和加密邮件创建新密钥对”（I want to create a new key pair for signing and encrypting my email）。</li>
+ <li>在“创建密钥”（Create Key）界面。取一个强壮的密码吧！你可以自行取密码，也可以使用 Diceware 模式。自己取密码虽然快速，但不安全。使用 Diceware 需要更长时间 and requires dice,但能生成攻击者难以辨识出的密码。要使用它，请阅读 Micah Lee 写的<a href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">这篇文章</a>的 Make a secure passphrase with Diceware 一节。</li>
+ </ul>
+
+ <p>如果你喜欢自己取密码，想一个你记得起的至少十二字符长的东西，至少包含一个小写和大写字母，和一个数字或标点符号。永远不要使用你其他地方使用过的密码。不用使用任何可辨识的模式，诸如生日、电话号码、宠物名字、歌词或书中的引言。</p>
+
+ <p class="notes">在“生成密钥”（Key Creation）界面，程序需要花费小会儿完成下一步。等待时，你可以在计算机上做一些其他事情，比如看电影或浏览网页。此时你计算机使用的越频繁，密钥生成的速度越快。</p>
+ <p><span style="font-weight: bold;">当 "Key Generation Completed" （密钥已生成）窗口弹出，选中 Generate Certificate （生成证书）并选择把它储存在计算机上安全的地方（我们推荐新建一个名为 Revocation Certificate [吊销证书]的文件夹在你的家目录下，并把它保存在那里）。这是本指南重要的一步，你将会在 <a href="#section5">Section 5</a> 了解到更多信息。</span></p>
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>I can't find the Enigmail menu.</dt>
+ <dd>In many new email programs, the main menu is represented by an image of three stacked horizontal bars. Enigmail may be inside a section called Tools.</dd>
+
+ <dt>More resources</dt>
+ <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Key_Management#Generating_your_own_key_pair">Enigmail's wiki instructions for key generation</a>.</dd>
+
+ <dt>My email looks weird</dt>
+ <dd>Enigmail doesn't tend to play nice with HTML, which is used to format emails, so it may disable your HTML formatting automatically. To send an HTML-formatted email without encryption or a signature, hold down the Shift key when you select compose. You can then write an email as if Enigmail wasn't there.</dd>
+
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+ <dt>Command line key generation</dt>
+ <dd>If you prefer using the command line for a higher degree of control, you can follow the documentation from <a href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">The GNU Privacy Handbook</a>. Make sure you stick with "RSA and RSA" (the default), because it's newer and more secure than the algorithms the documentation recommends. Also make sure your key is at least 2048 bits, or 4096 if you want to be extra secure.</dd>
+
+ <dt>Advanced key pairs</dt>
+ <dd>When GnuPG creates a new keypair, it compartmentalizes the encryption function from the signing function through <a href="https://wiki.debian.org/Subkeys">subkeys</a>. If you use subkeys carefully, you can keep your GnuPG identity much more secure and recover from a compromised key much more quickly. <a href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex Cabal</a> and <a href="http://keyring.debian.org/creating-key.html">the Debian wiki</a> provide good guides for setting up a secure subkey configuration.</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+ </div><!-- End #step-2a .step -->
+
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-2b" class="step">
+ <div class="main">
+ <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
+ <p>In your email program's menu, select Enigmail → Key Management.</p>
+ <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
+ <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>
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>The progress bar never finishes</dt>
+ <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>
+ <dt>My key doesn't appear in the list</dt>
+ <dd>Try checking "Display All Keys by Default."</dd>
+ <dt>More documentation</dt>
+ <dd>If you're having trouble with our instructions or just want to learn more, check out <a href="https://www.enigmail.net/documentation/quickstart-ch2.php#id2533620">Enigmail's documentation</a>.</dd>
+
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+ <dt>Uploading a key from the command line</dt>
+ <dd>You can also upload your keys to a keyserver through the <a href="https://www.gnupg.org/gph/en/manual/x457.html">command line</a>. <a href="https://sks-keyservers.net/overview-of-pools.php">The sks Web site</a> maintains a list of highly interconnected keyservers. You can also <a href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">directly export your key</a> as a file on your computer.</dd>
+
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+ </div><!-- End #step-2b .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="terminology" class="step">
+ <div class="main">
+ <h3>GnuPG, OpenPGP, what?</h3>
+ <p>In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used interchangeably. Technically, OpenPGP (Pretty Good Privacy) is the encryption standard, and GNU Privacy Guard (often shortened to GPG or GnuPG) is the program that implements the standard. Enigmail is a plug-in program for your email program that provides an interface for GnuPG.</p>
+ </div><!-- End .main -->
+ </div><!-- End #terminology.step-->
+
+
+ </div>
+ </section><!-- End #section2 -->
+
+ <!-- ~~~~~~~~~ Section 3: Try it out ~~~~~~~~~ -->
+ <section class="row" id="section3">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#3</em> Try it out!</h2>
+ <p>Now you'll try a test correspondence with a computer program named Edward, who knows how to use encryption. Except where noted, these are the same steps you'd follow when corresponding with a real, live person.</p>
+
+ <!-- <p>NOTE: Edward is currently having some technical difficulties, so he may take a long time to respond, or not respond at all. We're sorry about this and we're working hard to fix it. Your key will still work even without testing with Edward.</p> -->
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 3.a</em> Send Edward your public key</h3>
+ <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 Enigmail → 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>
+
+ <p>Address the message to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Put at least one word (whatever you want) in the subject and body of the email. Don't send yet.</p>
+
+ <p>The lock icon in the top left should be yellow, meaning encryption is
+ turned on. We want this first special message to be unencrypted, so
+ click the icon once to turn it off. The lock should become grey, with a
+ blue dot on it (to alert you that the setting has been changed from the
+ default). Once encryption is off, hit Send.</p>
+
+ <p class="notes">It may take two or three minutes for Edward 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 he'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>
+
+ <p>When you open Edward's reply, GnuPG may prompt you for your password before using your private key to decrypt it.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-3a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3b" class="step">
+ <div class="main">
+ <h3><em>Step 3.b</em> Send a test encrypted email</h3>
+ <p>Write a new email in your email program, addressed to <a href="mailto:edward-en@fsf.org">edward-en@fsf.org</a>. Make the subject "Encryption test" or something similar and write something in the body.</p>
+ <p>The lock icon in the top left of the window should be yellow, meaning encryption is on. This will be your default from now on.</p>
+ <p class="notes">Next to the lock, you'll notice an icon of a pencil. We'll get to this in a moment.</p>
+ <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
+
+ <p>To encrypt an email to Edward, you need his public key, so now you'll have Enigmail download it from a keyserver. Click Download Missing Keys and use the default in the pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key ID starting with C), then select ok. Select ok in the next pop-up.</p>
+
+ <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Check the box in front of Edward's key and click Send.</p>
+
+ <p class="notes">Since you encrypted this email with Edward's public key, Edward's private key is required to decrypt it. Edward is the only one with his private key, so no one except him can decrypt it.</p>
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>疑难解答</h4>
+ <dl>
+ <dt>Enigmail can't find Edward's key</dt>
+ <dd>Close the pop-ups that have appeared since you clicked Send. 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>
+ <dt>Unscrambled messages in the Sent folder</dt>
+ <dd>Even though you can't decrypt messages encrypted to someone else's key, your email program will automatically save a copy encrypted to your public key, which you'll be able to view from the Sent folder like a normal email. This is normal, and it doesn't mean that your email was not sent encrypted.</dd>
+ <dt>More resources</dt>
+ <dd>If you're still having trouble with our instructions or just want to learn more, check out <a href="https://enigmail.wiki/Signature_and_Encryption#Encrypting_a_message">Enigmail's wiki</a>.</dd>
+ <dt class="feedback">没有得到解答？</dt>
+ <dd class="feedback">请在<a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">反馈页</a>上告诉我们。</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+ <dt>Encrypt messages from the command line</dt>
+ <dd>You can also encrypt and decrypt messages and files from the <a href="https://www.gnupg.org/gph/en/manual/x110.html">command line</a>, if that's your preference. The option --armor makes the encrypted output appear in the regular character set.</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+
+ </div><!-- End .main -->
+ </div><!-- End #step-3b .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-headers_unencrypted" class="step">
+ <div class="main">
+ <h3><em>Important:</em> Security tips</h3>
+ <p>Even if you encrypt 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 a surveillance system can still figure out who you're communicating with. Also, surveillance agents will know that you're using GnuPG, even if they can't figure out what you're saying. When you send attachments, Enigmail will give you the choice to encrypt them or not, independent of the actual email.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-headers_unencrypted .step-->
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3c" class="step">
+ <div class="main">
+ <h3><em>Step 3.c</em> Receive a response</h3>
+ <p>When Edward receives your email, he will use his private key to decrypt it, then use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to encrypt his reply to you.</p>
+
+ <p class="notes">It may take two or three minutes for Edward 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>
+ <p>When you receive Edward'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>
+ <p>Notice the bar that Enigmail shows you above the message, with information about the status of Edward's key.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-3c .step -->
+
+
+ <div id="step-3d" class="step">
+ <div class="main">
+ <h3><em>Step 3.d</em> Send a test signed email</h3>
+ <p>GnuPG includes a way for you to sign messages and files, verifying that they came from you and that they weren't tampered with along the way. These signatures are stronger than their pen-and-paper cousins -- they're impossible to forge, because they're impossible to create without your private key (another reason to keep your private key safe).</p>
+
+ <p>You can sign messages to anyone, so it's a great way to make people aware that you use GnuPG and that they can communicate with you securely. If they don't have GnuPG, they will be able to read your message and see your signature. If they do have GnuPG, they'll also be able to verify that your signature is authentic.</p>
+
+ <p>To sign an email to Edward, compose any message to him and click the pencil icon next to the lock icon so that it turns gold. If you sign a message, GnuPG may ask you for your password before it sends the message, because it needs to unlock your private key for signing.</p>
+
+ <p>With the lock and pencil icons, you can choose whether each message will be encrypted, signed, both, or neither.</p>
+ </div>
+ </div>
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-3e" class="step">
+ <div class="main">
+ <h3><em>Step 3.e</em> Receive a response</h3>
+ <p>When Edward receives your email, he will use your public key (which you sent him in <a href="#step-3a">Step 3.A</a>) to verify that your signature is authentic and the message you sent has not been tampered with.</p>
+
+ <p class="notes">It may take two or three minutes for Edward 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>
+
+ <p>Edward's reply will arrive encrypted, because he prefers to use encryption whenever possible. If everything goes according to plan, it should say "Your signature was verified." If your test signed email was also encrypted, he will mention that first.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-3c .step -->
+ </div>
+ </section>
+
+
+ <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust ~~~~~~~~~ -->
+ <section class="row" id="section4">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#4</em> Learn the Web of Trust</h2>
+ <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>
+
+ <p>When you sign someone's key, you are publicly saying that you've verified that it belongs to them and not someone else.</p>
+
+ <p>Signing keys and signing messages use the same type of mathematical operation, but they carry very different implications. It's a good practice to generally sign your email, but if you casually sign people's keys, you may accidently end up vouching for the identity of an imposter.</p>
+
+ <p>People who use your public key can see who has signed it. Once you've used GnuPG for a long time, your key may have hundreds of signatures. You can consider a key to be more trustworthy if it has many signatures from people that you trust. The Web of Trust is a constellation of GnuPG users, connected to each other by chains of trust expressed through signatures.</p>
+
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-4a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 4.a</em> Sign a key</h3>
+ <p>In your email program's menu, go to Enigmail → Key Management.</p>
+ <p>Right click on Edward's public key and select Sign Key from the context menu.</p>
+ <p>In the window that pops up, select "I will not answer" and click ok.</p>
+ <p>Now you should be back at the Key Management menu. Select Keyserver → Upload Public Keys and hit ok.</p>
+ <p class="notes">You've just effectively said "I trust that Edward's public key actually belongs to Edward." This doesn't mean much because Edward isn't a real person, but it's good practice.</p>
+
+
+ <!--<div id="pgp-pathfinder">
+ <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
+ <p><strong>From:</strong> <input type="text" placeholder="xD41A008" name="FROM"></p>
+ <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
+ <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
+ </form>
+ </div>End #pgp-pathfinder -->
+
+ </div><!-- End .main -->
+ </div><!-- End #step-4a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-identify_keys" class="step">
+ <div class="main">
+ <h3>Identifying keys: Fingerprints and IDs</h3>
+ <p>People's public keys are usually identified by their key fingerprint, which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Edward's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to Enigmail → 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 people can double-check that they have the correct public key when they download yours from a keyserver.</p>
+
+ <p class="notes">You may also see public keys referred to by their key ID, which is simply the last eight digits of the fingerprint, like C09A61E8 for Edward. 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 you are trying to communicate to verify which one to use.</p>
+
+ </div><!-- End .main -->
+ </div><!-- End #step-sign_real_keys .step-->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="check-ids-before-signing" class="step">
+ <div class="main">
+ <h3><em>Important:</em> What to consider when signing keys</h3>
+ <p>Before signing a person's key, you need to be confident that it actually belongs to them, and that they are who they say they are. Ideally, this confidence comes from having interactions and conversations with them over time, and witnessing interactions between them and others. Whenever signing a key, ask to see the full public key fingerprint, and not just the shorter key ID. If you feel it's important to sign the key of someone you've just met, also ask them to show you their government identification, and make sure the name on the ID matches the name on the public key. 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>
+
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>Advanced</h4>
+ <dl>
+ <dt>Master the Web of Trust</dt>
+ <dd>Unfortunately, trust does not spread between users the way <a href="http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people think</a>. One of best ways to strengthen the GnuPG community is to deeply <a href="https://www.gnupg.org/gph/en/manual/x334.html">understand</a> the Web of Trust and to carefully sign as many people's keys as circumstances permit.</dd>
+ <dt>Set ownertrust</dt>
+ <dd>If you trust someone enough to validate other people's keys, you can assign them an ownertrust level through Enigmails's key management window. Right click on the other person's key, go to the "Select Owner Trust" menu option, select the trustlevel and click OK. Only do this once you feel you have a deep understanding of the Web of Trust.</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+ </div><!-- End .main -->
+
+ </div><!-- End #step-sign_real_keys .step-->
+
+
+ </div>
+ </section><!-- End #section4 -->
+
+ <!-- ~~~~~~~~~ Section 5: Use it well ~~~~~~~~~ -->
+ <section id="section5" class="row">
+ <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>
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-5a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well (1)" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3>When should I encrypt? When should I sign?</h3>
+
+ <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. 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>Unless you don't want to reveal your own identity (which requires other protective measures), there's no reason not to sign every message, whether or not you are encrypting. In addition to allowing those with GnuPG to verify that the message came from you, signing is a non-intrusive way to remind everyone that you use GnuPG and show support for secure communication. If you often send signed messages to people that aren't familiar with GnuPG, it's nice to also include a link to this guide in your standard email signature (the text kind, not the cryptographic kind).</p>
+
+ </div><!-- End .main -->
+ </div><!-- End #step-5a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-5b" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well (2)" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3>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 first encrypted email that Edward sent you. Because Edward encrypted it with your public key, it will have a message from Enigmail at the top, which most likely says "Enigmail: 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>
+ </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, not on a device you carry with you regularly.</p>
+ <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>
+ </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 or forge your signature. This guide doesn't cover how to revoke a key, but you can follow these <a href="https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">instructions</a>. After you're done revoking, make a new key and send an email to everyone with whom you usually use your key to make sure they know, including a copy of your new key.</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-lost_key .step-->
+
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <!---<div id="transfer-key" class="step">
+ <div class="main">
+ <h3>Transferring you key</h3>
+ <p>You can use Enigmail's <a href="https://www.enigmail.net/documentation/keyman.php">key management window</a> to import and export keys. If you want to be able to read your encrypted email on a different computer, you will need to export your secret key from here. Be warned, if you transfer the key without <a href="https://help.ubuntu.com/community/EncryptedFilesystemsOnRemovableStorage">encrypting</a> the drive it's on the transfer will be dramatically less secure.</p>
+ </div>--><!-- End .main -->
+ </div><!-- End #step-lost_key .step-->
+
+
+
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="webmail-and-GnuPG" class="step">
+ <div class="main">
+ <h3>Webmail and GnuPG</h3>
+ <p>When you use a web browser to access your email, you're using webmail, an email program stored on a distant website. Unlike webmail, your desktop email program runs on your own computer. Although webmail can't decrypt encrypted email, it will still display it in its encrypted form. If you primarily use webmail, you'll know to open your email client when you receive a scrambled email.</p>
+ </div><!-- End .main -->
+ </div><!-- End #webmail-and-GnuPG .step-->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~
+ <div id="step-5d" class="step">
+ <div class="main">
+ <h3>Make your public key part of your online identity</h3>
+ <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>
+
+ <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>
+ </div>--><!-- End .main
+</div> End #step-5d .step-->
+
+
+</section><!-- End #section5 -->
+
+
+
+<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
+<section class="row" id="section6">
+ <div id="step-click_here" class="step">
+ <div class="main">
+ <h2><a href="next_steps.html">Great job! Check out the next steps.</a></h2>
+
+ </div><!-- End .main -->
+ </div><!-- End #step-click_here .step-->
+
+</section><!-- End #section6 -->
+
+<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
+<!-- When un-commenting this section go to main.css and search
+for /* Guide Sections Background */ then add #faq to the desired color
+
+<section class="row" id="faq">
+<div>
+<div class="sidebar">
+<h2>FAQ</h2>
+</div>
+
+<div class="main">
+<dl>
+<dt>My key expired</dt>
+<dd>Answer coming soon.</dd>
+
+<dt>Who can read encrypted messages? Who can read signed ones?</dt>
+<dd>Answer coming soon.</dd>
+
+<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>
+<dd>Answer coming soon.</dd>
+</dl>
+</div>
+</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>Copyright © 2014-2016 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please support our work by <a href="https://u.fsf.org/yr">joining us as an associate member.</a></p>
+
+ <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>. Download the <a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">source code of Edward reply bot</a> by Andrew Engelbrecht <sudoman@ninthfloor.org> and Josh Drake <zamnedix@gnu.org>, available under the GNU Affero General Public License. <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
+
+ <p>Fonts used in the guide & 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ś, <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a> by Florian Cramer.</p>
+
+ <p>Download the <a href="emailselfdefense_source.zip">source package</a> for this guide, including fonts, image source files and the text of Edward's messages.</p>
+
+ <p>This site uses the Weblabels standard for labeling <a href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" rel="jslicense">source code and license information</a>.</p>
+ </div><!-- /#copyright -->
+ <p class="credits">
+ Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" alt="Journalism++" /></a>
+ </p><!-- /.credits -->
+ </div>
+</footer><!-- End #footer -->
+
+<script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
+<script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
+
+<!-- Piwik -->
+<script type="text/javascript" >
+// @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later
+var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");
+document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
+try {
+ var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13);
+ piwikTracker.trackPageView();
+ piwikTracker.enableLinkTracking();
+} catch( err ) {}
+// @license-end
+</script><noscript><p><img src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0" alt="" /></p></noscript>
+<!-- End Piwik Tracking Code -->
+
+
+
+</body>
+</html>
projects / enc.git / commitdiff