<!DOCTYPE html>
<html lang="zh-Hans">
<head>
- <meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>电子邮件加密指南 - 使用 GnuPG 加密对抗大规模监控</title>
+<meta name="keywords" content="GnuPG, GPG, openpgp, 监控, 隐私, 电子邮件, 安全, GnuPG2, 加密" />
+<meta name="description" content="电子邮件监控侵犯了我们的基本权利，威胁了言论自由。本指南将在四十分钟里教会你如何使用 GnuPG 加密。" />
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link rel="stylesheet" href="../static/css/main.css" />
+<link rel="stylesheet" href="../static/css/main.zh-hans.css" />
+<link rel="shortcut icon"
+href="../static/img/favicon.ico" />
+</head>
+<body>
- <title>Email Self-Defense - a guide to fighting surveillance with GnuPG encryption</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>Email Self-Defense</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>大规模监控侵犯了我们的基本权利，并给言论自由带来风险。本指南将会教你一些基本的监控防护技巧：电子邮件加密。一旦你学会了，监控代理即使拦截了你的邮件也无法阅读其中的内容。你所需要的是一台带网络连接的计算机，一个电子邮件账号和大约 40 分钟的时间。</p>
-
- <p>即使你没有什么秘密好隐藏的，使用加密能够保护与你交流的人的隐私，并让大规模监控变得困难。If you do have something important to hide, you're in good company; 告密者在揭发人权侵犯，贪污腐败和犯罪行为时，也是用着相同的工具来保护他们自己的身份。</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）来的更安全。你可以在 <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> Make your keys</h2>
- <p>To use the GnuPG system, you'll need a public key and a private key (known together as a keypair). Each is a long string of randomly generated numbers and letters that are unique to you. Your public and private keys are linked together by a special mathematical function.</p>
-
- <p>Your public key isn't like a physical key, because it's stored in the open in an online directory called a keyserver. People download it and use it, along with GnuPG, to encrypt emails they send to you. You can think of the keyserver as a phonebook; people who want to send you encrypted email can look up your public key.</p>
-
- <p>Your private key is more like a physical key, because you keep it to yourself (on your computer). You use GnuPG and your private key together to descramble encrypted emails other people send to you. <span style="font-weight: bold;">You should never share you private key with anyone, under any circumstances.</span></p>
- <p>In addition to encryption and decryption, you can also use these keys to sign messages and check the authenticity of other people's signatures. We'll discuss this more in the next section.</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> Make a keypair</h3>
- <p>The Enigmail Setup wizard may start automatically. If it doesn't, select Enigmail → Setup Wizard from your email program's menu. You don't need to read the text in the window that pops up unless you'd like to, but it's good to read the text on the later screens of the wizard. Click Next with the default options selected, except in these instances, which are listed in the order they appear:</p>
- <ul>
- <li>On the screen titled "Encryption," select "Encrypt all of my messages by default, because privacy is critical to me."</li>
- <li>On the screen titled "Signing," select "Don't sign my messages by default."</li>
- <li>On the screen titled "Key Selection," select "I want to create a new key pair for signing and encrypting my email."</li>
- <li>On the screen titled "Create Key," pick a strong password! You can do it manually, or you can use the Diceware method. Doing it manually is faster but not as secure. Using Diceware takes longer and requires dice, but creates a password that is much harder for attackers figure out. To use it, read the section "Make a secure passphrase with Diceware" in <a href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">this article</a> by Micah Lee.</li>
- </ul>
-
- <p>If you'd like to pick a password manually, come up with something you can remember which is at least twelve characters long, and includes at least one lower case and upper case letter and at least one number or punctuation symbol. Never pick a password you've used elsewhere. Don't use any recognizable patterns, such as birthdays, telephone numbers, pets' names, song lyrics, quotes from books, and so on.</p>
-
- <p class="notes">The program will take a little while to finish the next step, the "Key Creation" screen. While you wait, do something else with your computer, like watching a movie or browsing the Web. The more you use the computer at this point, the faster the key creation will go.</p>
- <p><span style="font-weight: bold;">When the "Key Generation Completed" screen pops up, select Generate Certificate and choose to save it in a safe place on your computer (we recommend making a folder called "Revocation Certificate" in your home folder and keeping it there). This step is essential for your email self-defense, as you'll learn more about in <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 ~~~~~~~~~ -->
+<!--<div style="text-align: center; padding: 2.5px; background-color: #a94442; color:#fcf8e3;">
+<p>Due to Enigmail's PGP functionality being migrated into Icedove and Thunderbird, steps 2 and 3 of the guide are currently out of date.</p><p> Thank you for your patience while we're working on a new round of updates.</p></div>-->
+<!-- PLACE FUNDRAISER MODAL WINDOW HERE -->
+<!-- ~~~~~~~~~ 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><strong><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide">
+帮助翻译！</a></strong></li>
+</ul>
+
+<ul id="menu" class="os">
+<li class="spacer"><a href="index.html" class="current">安装指南</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="http://hhldo3tnt5solzj2bwfvh7xm4slk2forpjwjyemhcfrlob5gq75gioid.onion/zh-hans"
+target="_blank">本站洋葱暗网服务</a></li>
+<li class="spacer"><a
+href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email%20encryption%20for%20everyone%20via%20%40fsf">
+分享
+<img src="../static/img/gnu-social.png" class="share-logo"
+alt="[GNU Social]" />
+<img src="../static/img/mastodon.png" class="share-logo"
+alt="[Mastodon]" />
+<img src="../static/img/reddit-alien.png" class="share-logo"
+alt="[Reddit]" />
+<img src="../static/img/hacker-news.png" class="share-logo"
+alt="[Hacker News]" /></a></li>
+</ul>
+
+
+<!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
+<div id="fsf-intro">
+
+<h3><a href="https://u.fsf.org/ys"><img
+alt="自由软件基金会"
+src="../static/img/fsf-logo.png" />
+</a></h3>
+
+<div class="fsf-emphasis">
+
+<p>我们为计算机用户争取权利，促进自由软件发展，对抗大规模监控对我们至关重要。</p>
+
+<p><strong>捐款支持本指南。我们将一直改进它，使其充实，让普通人迈出隐私保护的第一步，并从中获益。</strong></p>
+
+</div>
+
+<div style="text-align: center;">
+<p><a
+href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&mtm_campaign=email_self_defense&mtm_kwd=guide_donate"><img alt="捐款" src="../static/img/zh-hans/donate.png" /></a></p>
+
+<h5>注册</h5>
+<form action="https://my.fsf.org/civicrm/profile/create?reset=1&gid=31" method="post">
+<p>输入电子邮箱以获取我们每月新闻简报<br /><a href="https://www.fsf.org/free-software-supporter/">《自由软件支持者》</a></p>
+
+<p><input id="frmEmail" type="text" name="email-Primary" size="18"
+maxlength="80" /></p>
+<p><input type="submit" name="_qf_Edit_next" value="订阅" /></p>
+<div><input name="postURL" type="hidden" value="" /> <input type="hidden"
+name="group[25]" value="1" /> <input name="cancelURL" type="hidden"
+value="https://my.fsf.org/civicrm/profile?reset=1&gid=31" /> <input
+name="_qf_default" type="hidden" value="Edit:cancel" />
+</div>
+</form></div>
+
+</div>
+
+
+<!-- End #fsf-intro -->
+<!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
+<div class="intro">
+
+<p><a id="infographic" href="infographic.html"><img
+src="../static/img/zh-hans/infographic-button.png"
+alt="查看并分享我们的信息图" /></a>
+大规模监控侵犯了我们的基本权利，威胁了言论自由。本指南将会教授一个基本的监控自我保护技巧：加密电子邮件。学会后，你将能够收发其他人（包括截获邮件的监控代理和窃贼）无法阅读的电子邮件。你需要的是一台带网络连接的计算机，一个电子邮箱账户和大约四十分钟时间。</p>
+
+<p>即使你没有不可告人的秘密，使用加密可以保护对方的隐私，使得大规模监控系统变得难以运作。如果你确实有重要的东西需要保护，那么你并不孤独；告密者在揭发人权侵犯、腐败和其他犯罪问题时，也是使用同样的工具保护他们身份。</p>
+
+<p>除了使用加密技术，对抗监控还需要我们作政治斗争，以减少政府<a
+href="https://www.gnu.org/philosophy/surveillance-vs-democracy.zh-cn.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.zh-cn.html">自由许可</a>的软件；自由软件是完全透明的，任何人都可以复制它，制作自己的版本。这使得它比专有软件（比如
+Windows 和 macOS）更难受到监控。在 <a href="https://u.fsf.org/ys">fsf.org</a>
+上了解更多关于自由软件的信息。</p>
+
+<p>大多数 GNU/Linux 操作系统自带 GnuPG，如果你正在使用这类系统，你不必下载 GnuPG。如果你使用的是 macOS 和
+Windows，请按以下步骤下载 GnuPG。在配置 GnuPG 前，你需要一款桌面电子邮件程序。大多数 GNU/Linux 发行版已经安装好
+IceDove 了，它可能叫另一个名字 Thunderbird。电子邮件程序提供了访问邮箱账户的新途径（当然你也可以像 Gmail
+那样通过浏览器访问），但它拥有更多的功能。</p>
+
+</div>
+
+
+<!-- End .section-intro -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-1a" class="step">
+<div class="sidebar">
+
+<p class="large"><img
+src="../static/img/zh-hans/screenshots/step1a-install-wizard.png"
+alt="第 1.A 步：安装向导" /></p>
+
+</div>
+<!-- /.sidebar -->
+<div class="main">
+
+<h3><em>第 1.a 步</em> 配置电子邮件账户</h3>
+
+<p>打开电邮程序，按照向导一步一步配置好电邮账户。通常第一步是从“账户设置” →
+“添加邮件账户”开始的。从系统管理员和电邮账户帮助页面可以获得电邮服务器设置信息。</p>
+
+
+
+<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+<div class="troubleshooting">
+
+<h4>疑难解答</h4>
+
+<dl>
+<dt>向导程序没有启动</dt>
+<dd>你可以手动启动它，但不同邮件程序的菜单选项不尽相同。启动它的按钮在程序的主菜单里，“新建”或者类似的，标题类似于“添加账号”或“新建/已有电子邮件帐户”。</dd>
+
+<dt>向导程序找不到我的账户或无法下载邮件</dt>
+<dd>在网上搜索解决方案之前，我们建议你问问你身边使用相同邮件系统的人，以检查设置是否正确。</dd>
+
+<dt>我找不到菜单</dt>
+<dd>在许多新型电子邮件程序中，主菜单是用三横杠图标表示的。</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>第 1.b 步</em> 安装 GnuPG</h3>
+
+<p>如果使用的是 GNU/Linux，或是已经安装了 GnuPG，请跳至<a href="#step-1b">第 2 节</a>。</p>
+
+<p>如果你使用的是 macOS 或 Windows，你首先需要安装 GnuPG
+程序。根据你自己的操作系统完成下述操作。在本指南后面的篇幅，所有操作系统的步骤都是相同的。 </p>
+
+
+<!-- ~~~~~~~~~ MACOS ~~~~~~~~~ -->
+<div class="troubleshooting">
+
+<h4>macOS</h4>
+
+<dl>
+<dt>使用第三方包管理器安装 GnuPG</dt>
+<dd>
+<p>macOS 的默认包管理器安装 GnuPG 和其他自由软件非常困难（比如安装 Emacs、GIMP 和 Inkscape）。我们推荐安装叫
+Homebrew 的第三方包管理器，用它安装
+GnuPG，能够使安装过程变得简单。对此，我们需要用到一个叫“终端”（Terminal）的程序，它已经预安装在 macOS 上了。</p>
+
+<p># 在 <a href="https://brew.sh/">Homebrew</a>
+主页点击剪贴板图标复制第一条命令，把它粘贴在终端里。按回车键，等待安装完成。</p>
+<p># 在终端输入如下命令安装 GnuPG：<br/>
+<code>brew install gnupg gnupg2</code></p>
+</dd>
+</dl>
+
+</div>
+
+
+<!-- /.troubleshooting -->
+<!-- ~~~~~~~~~ WINDOWS ~~~~~~~~~ -->
+<div class="troubleshooting">
+
+<h4>Windows</h4>
+
+<dl>
+<dt>下载 GPG4Win 获取 GnuPG</dt>
+<dd><p><a href="https://www.gpg4win.org/">GPG4Win</a> 是一个包含 GnuPG
+的电邮文件加密的软件包。下载安装它的最新版本，所有步骤都选择默认选项。安装结束后，你可以关闭程序创建的窗口。</p>
+</dd>
+</dl>
+
+</div>
+<!-- /.troubleshooting -->
+</div>
+<!-- End .main -->
+</div>
+
+
+<!-- End #step1-b .step -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="terminology" class="step">
+<div class="main">
+
+<h3>GnuPG 和 OpenPGP 有何区别？</h3>
+
+<p>通常，术语 GnuPG, GPG, GNU Privacy Guard, OpenPGP 和 PGP
+可以互换其称呼。技术上说，OpenPGP（Pretty Good Privacy）是一种加密标准， GNU Privacy Guard（常被缩写为
+GPG 和 GnuPG）是实现该标准的程序。大多数电邮程序提供了 GnuPG 接口，GnuPG 也有叫 GnuPG2 的新版本。</p>
+
+</div>
+<!-- End .main -->
+</div>
+
+<!-- End #terminology.step-->
+</div></section>
+
+
+<!-- End #section1 -->
+<!-- ~~~~~~~~~ Section 2: Make your keys ~~~~~~~~~ -->
+<section id="section2" class="row"><div>
+
+
+<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+<div class="section-intro">
+
+<h2><em>#2</em> 生成密钥</h2>
+<p class="float medium"><img src="../static/img/zh-hans/screenshots/step2a-01-make-keypair.png" alt="大头机器人手里握着私钥和公钥"/></p>
+
+<p>要使用 GnuPG
+系统，你将会用到一把公钥和一把私钥，他们合称为密钥对。每一把都是由随机字母数字组成的长字符串，并且独一无二。你的公钥和私钥是由一种特殊的数学函数联系在一起。</p>
+
+<p>你的公钥不像现实中的钥匙，它被公开储存在被称之为密钥服务器的在线目录上。人们可以下载使用它，借助
+GnuPG，人们向你发送加密邮件。你可以把密钥服务器想象成一本电话簿；想要给你发送加密邮件的人能够找到你的公钥。</p>
+
+<p>你的私钥更像是现实中的钥匙，你需要自行保管（在你的计算机中）。你使用 GnuPG
+和你的私钥来解密他人发给你的加密邮件。<strong>无论如何，你都不应该向他人分享你的私钥。</strong></p>
+
+<p>除了加密和解密，你可以使用这些密钥对消息进行签名，并验证其他人签名的真实性。我们将在下一节里详细探讨它。</p>
+
+</div>
+
+
+<!-- End .section-intro -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-2a" class="step">
+<div class="sidebar">
+<p class="large"><img
+src="../static/img/zh-hans/screenshots/step2a-02-make-keypair.png"
+alt="第 2.A 步：生成密钥对" /></p>
+
+<p class="large"><img
+src="../static/img/zh-hans/screenshots/step2a-03-make-keypair.png"
+alt="第 2.A 步：设置密码" /></p>
+
+</div>
+<!-- /.sidebar -->
+<div class="main">
+
+<h3><em>第 2.a 步</em> 生成密钥对</h3>
+
+<h4>生成密钥对</h4>
+
+<p>我们将在终端里使用 GnuPG 程序的命令完成创建密钥对。</p>
+
+<p class="notes">无论在 GNU/Linux、macOS 还是 Windows 系统，你都能够使用终端（macOS 叫 Termial，Windows 叫
+PowerShell），一些 GNU/Linux 发行版可以通过快捷键 <kbd>Ctrl + Alt + T</kbd> 打开终端。</p>
+
+<p># 输入 <code>gpg --full-generate-key</code> 开始生成密钥。</p>
+<p># 创建何种类型的密钥，请选择默认选项： <samp>1 RSA and RSA</samp>.</p>
+<p># 输入以下密钥长度： <code>4096</code> 来得到强壮的密钥。</p>
+<p># 选择失效日期；我们建议 <code>2y</code> （两年）。</p>
+<p>按照提示继续设置个人信息。</p>
+<p class="notes"> 使用 <code>--gen-key</code> 还是 <code>--full-generate-key</code> 视使用的 GPG
+版本而定。</p>
+
+<h4>设置密码</h4>
+<p>在“密码”界面，取一个强壮的密码吧！你可以自行取密码，也可以使用 Diceware 方法。自己取密码虽然快捷，但不安全。使用 Diceware
+需要更长时间，并要求掷骰子，但它能生成攻击者难以猜测的密码。要使用它，请阅读 Micah Lee 写的<a
+href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">这篇文章</a>的“使用
+Diceware 生成安全密码 ”章节。</p>
+
+
+<p>如果你喜欢自己取密码，想一个能记住的至少十二字符长的东西，包含至少一个小写和一个大写字母，至少一个数字或标点符号。永远不要使用你在其他地方使用过的密码。不用使用任何可辨认的规律，诸如生日、电话号码、宠物名字、歌词或书中的名言等等。</p>
+
+
+<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+<div class="troubleshooting">
+
+<h4>疑难解答</h4>
+<dl>
+<dt>未安装 GnuPG</dt>
+<dd>
+通过命令 <code>gpg --version</code> 可以检查是否安装了 GnuPG。如果未安装，在 GNU/Linux
+操作系统下会有类似提示：<samp>Command 'gpg' not found, but can be installed with: sudo
+apt install gnupg</samp>。使用这条命令安装 GnuPG。</dd>
+
+<dt><i>gpg --full-generate-key</i> 命令没用</dt>
+<dd>一些发行版的 GPG 版本不同。当你看到类似 <samp>gpg: Invalid option
+"--full-generate-key"</samp> 错误提示时，请尝试： <br />
+<code>sudo apt update</code><br />
+<code>sudo apt install gnupg2</code><br />
+<code>gpg2 --full-generate-key</code><br />
+如果问题得以解决，你将在下面使用 gpg2 而非 gpg 完成本指南的下列步骤。
+<p class="notes"> 使用 <code>--gen-key</code> 还是 <code>--full-generate-key</code> 视使用的 GPG
+版本而定。</p>
+</dd>
+
+<dt>太难想一个好密码了</dt>
+<dd>没关系。想一个好密码很重要。当你准备好了，请从头开始按照步骤生成密钥。</dd>
+
+<dt>怎么才能看到我的密钥？</dt>
+<dd>
+使用命令 <code>gpg --list-keys</code> 查看所有密钥。你的密钥将会显示在上面，在稍后的<a
+href="#section3">第 3 节</a>，爱德华的密钥也会显示出来。<br />
+如果只想查看自己的密钥，使用命令 <code>gpg --list-key [你的邮箱]</code>。<br />
+你也可以使用 <code>gpg --list-secret-key</code> 查看自己的私钥。</dd>
+
+<dt>更多资源</dt>
+<dd>更多信息，请参考文档 <a href="https://www.gnupg.org/gph/en/manual/c14.html#AEN25">GNU
+隐私手册</a>。请确保选择的是"RSA and RSA" (the default)，它比文档中推荐的算法更新更安全。如果你想更安全，你的密钥至少应当
+4096 bits。</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>进阶指南</h4>
+<dl>
+<dt>高级密钥对</dt>
+<dd>当 GnuPG 创建一个新的密钥对时，加密函数和签名函数会通过<a
+href="https://wiki.debian.org/Subkeys">子密钥</a>分离开来。如果你谨慎地使用子密钥，GPG
+身份安全性会越高，能够迅速从密钥泄漏中恢复过来。如何安全配置子密钥，推荐阅读 <a
+href="https://alexcabal.com/creating-the-perfect-gpg-keypair/">Alex
+Cabal</a> 和 <a href="http://keyring.debian.org/creating-key.html">Debian
+wiki</a> 的文档。</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="sidebar">
+<p class="large"><img
+src="../static/img/zh-hans/screenshots/step2b-04-upload-and-certificate.png"
+alt="第 2.B 步：上传公钥和生成吊销证书" /></p>
+
+</div>
+<!-- /.sidebar -->
+<div class="main">
+
+<h3><em>第 2.b 步</em> 生成密钥的一些重要步骤</h3>
+
+<h4>上传公钥到密钥服务器</h4>
+<p>我们将公钥上传到密钥服务器，想给你发送加密信息的人现在可以从因特网上下载到你的公钥了。上传时菜单中有多个密钥服务器可供选择，它们拥有彼此的完整副本，所以你选择哪一个无关紧要，但最好记住上传密钥的原始服务器。请注意，新密钥上传后，服务器间可能要数小时才能完成同步。</p>
+<p># 复制 KeyID：<code>gpg --list-key [你的邮箱]</code> 这条命令将列出公钥信息，它包括
+KeyID，这是一串由数字字母组成的独一无二的字符。复制 KeyID，你将在下面命令中使用它。</p>
+<p># 上传密钥到服务器：<code>gpg --send-key [keyID]</code></p>
+
+<h4>导出密钥</h4>
+<p>使用下面命令导出私钥，并在下一步中导入到电邮客户端中。将它储存在安全的地方，如果需要转移密钥，请保证以可信的方式传输，避免泄露私钥。使用下面命令导出密钥：</p>
+<p><code> $ gpg --export-secret-keys -a [keyID] > my_secret_key.asc<br/>
+$ gpg --export -a [keyID] > my_public_key.asc </code></p>
+
+<h4>创建吊销证书</h4>
+<p>你需要生成吊销证书，并把它保存在安全的地方（请参考<a href="#step-6c">第 6.C
+步</a>了解如何安全保存吊销证书）。它能够在发生密钥丢失或密钥泄露时用到。此步骤是本指南的重要步骤，您将在<a href="#section5">第
+5 节</a>里了解原因。</p>
+
+<p># 复制 KeyID：<code>gpg --list-key [你的邮箱]</code> 这条命令将列出公钥信息，它包括
+KeyID，这是一串由数字字母组成的独一无二的字符。复制 KeyID，你将在下面命令中使用它。</p>
+<p># 生成吊销证书： <code>gpg --gen-revoke --output revoke.asc [keyID]</code></p>
+<p># 它将引导你输入吊销原因，我们建议选择 <samp>1 = key has been compromised</samp>。</p>
+<p># 但你也可以不输入原因；将它留空，按回车键，确认选择。</p>
+
+
+
+<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+<div class="troubleshooting">
+
+<h4>疑难解答</h4>
+
+<dl>
+<dt>无法上传密钥到服务器</dt>
+<dd>除了使用常规的命令上传密钥，你可以使用特定的命令，将密钥服务器加进你的命令之中： <code>gpg --keyserver
+keys.openpgp.org --send-key [keyID]</code></dd>
+
+<dt>无法使用密钥或是“权限拒绝”</dt>
+<dd><p>像其他文件和目录一样，gpg 密钥是权限的主体。如果权限没有正确设置，系统可能无法接受你的密钥。下面步骤将帮助你排查问题，更正权限设置。</p>
+
+<p># 检查权限： <code>ls -l ~/.gnupg/*</code></p>
+<p># 设置权限为只有你可以读、写和执行。这是该目录的推荐权限设置。 <br/>
+使用此命令设置：<code>chmod 700 ~/.gnupg</code></p>
+<p># 设置权限为只有你可以读和写。这是目录里密钥文件的推荐权限设置。 <br/>
+使用此命令设置： <code>chmod 600 ~/.gnupg/*</code></p>
+
+<p class="notes">如果需要在 ~/.gnupg 里创建目录，你必须对这个目录给予执行权限。打开目录需要执行权限。关于权限的更多信息，请查看<a
+href="https://helpdeskgeek.com/linux-tips/understanding-linux-permissions-chmod-usage/">这篇指南</a>。</p>
+</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>进阶指南</h4>
+
+<dl>
+<dt>关于密钥服务器</dt>
+<dd>你可以在<a
+href="https://www.gnupg.org/gph/en/manual/x457.html">这篇手册中</a>了解关于密钥服务器的更多信息。你也可以<a
+href="https://www.gnupg.org/gph/en/manual/x56.html#AEN64">直接导出公钥文件</a>到你的计算机中。</dd>
+
+<dt>转移密钥</dt>
+<dd>
+<p>使用下面命令转移密钥。将它保存在安全的地方，以可信的方式进行传输，避免密钥泄露。如下是导入和导出密钥的命令：</p>
+
+<p><code> $ gpg --export-secret-keys -a [keyID] > my_private_key.asc<br />
+$ gpg --export -a [keyID] > my_public_key.asc<br />
+$ gpg --import my_private_key.asc<br />
+$ gpg --import my_public_key.asc </code></p>
+
+<p>确认 KeyID 是正确的，将它添加到完全信任之中：</p>
+
+<p><code> $ gpg --edit-key [你的邮箱] </code></p>
+
+<p>因为这是你的密钥，你应当选择 <code>ultimate</code>。你不应该对他人的密钥选择完全信任。</p>
+
+<p class="notes"> 参考<a href="#step-2b">第 2.B
+步的疑难解答</a>有关权限的信息。当传输密钥时，权限设置可能会变得混乱，提示出现一些错误。这是一些简单的避免方法</p>
+</dd>
+</dl>
+
+</div>
+<!-- /.troubleshooting -->
+</div>
+<!-- End .main -->
+</div>
+<!-- End #step-2b .step -->
+</div></section>
+
+
+<!-- End #section2 -->
+<!-- ~~~~~~~~~ Section 3: Set up email encryption ~~~~~~~~~ -->
+<section id="section3" class="row"><div>
+
+
+<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+<div class="section-intro">
+
+<h2><em>#3</em> 设置邮件加密</h2>
+<p class="notes">Icedove（或 Thunderbird）电邮程序集成了 PGP 功能，这让它非常便于使用。我们将在下面一系列步骤中带你在电邮客户端里使用密钥。</p>
+
+</div>
+
+
+<!-- End .section-intro -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-3a" class="step">
+<div class="sidebar">
+
+<p class="large"><img src="../static/img/zh-hans/screenshots/step3a-open-key-manager.png"
+alt="第 3.A 步：电子邮件菜单" /></p>
+
+<p class="large"><img src="../static/img/zh-hans/screenshots/step3a-import-from-file.png"
+alt="第 3.A 步：从文件中导入" /></p>
+
+<p class="large"><img src="../static/img/zh-hans/screenshots/step3a-success.png"
+alt="第 3.A 步：成功" /></p>
+
+<p class="large"><img src="../static/img/zh-hans/screenshots/step3a-troubleshoot.png"
+alt="第 3.A 步：疑难解答" /></p>
+</div>
+<!-- /.sidebar -->
+<div class="main">
+
+<h3><em>第 3.a 步</em> 配置电子邮件账户</h3>
+
+<p>完成邮件加密设置后，你就帮助增加了因特网上的加密流量。首先我们把密钥导入到电邮客户端，我们也将学习如何从服务器导入其他人的公钥，这样你就可以发送和接收加密邮件。</p>
+
+<p># 打开电邮客户端，选择“工具” → <i>OpenPGP 密钥管理器</i></p>
+<p># 选择“文件” → <i>从文件导入私钥</i></p>
+<p># 选择你在<a href="#step-2b">第 2.B 步</a>导出保存的私钥文件</p>
+<p># 使用密码解锁</p>
+<p># 你会看到 “已成功导入 OpenPGP 密钥！” 的窗口确认导入成功</p>
+<p># 在 “账户设置” → “端到端加密”里，确认你的密钥已经导入，并选择 <i>将此密钥视为个人密钥</i>。</p>
+
+</div>
+
+
+<!-- End .main -->
+<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+<div class="main">
+<div class="troubleshooting">
+<h4>疑难解答</h4>
+<dl>
+<dt>我不知道是否已正确导入密钥</dt>
+<dd>
+在 “账户设置” → “端到端加密”里查看。在这里你可以看到与此电邮账户相关的密钥是否存在。如果没有，请重试 <i>添加密钥</i>
+选项。确保你有正确、未过期的私钥文件。
+</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 #step3-a .step -->
+</div></section>
+
+
+<!-- End #section3 -->
+<!-- ~~~~~~~~~ Section 4: Try it out ~~~~~~~~~ -->
+<section class="row" id="section4"><div>
+
+
+<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+<div class="section-intro">
+
+<h2><em>#4</em> 试一试！</h2>
+<p class="float small"><img src="../static/img/zh-hans/screenshots/section3-try-it-out.png" alt="插图说明：房子里有一个人和一只猫，房间连接到服务器"/></p>
+<p>现在你将要尝试与名为爱德华（Edward）的 FSF 计算机程序进行通信，它掌握了如何加密。除非另有说明，你与真人通信时也遵循同样的步骤。</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 style="clear: both"></div>
+</div>
+
+
+<!-- End .section-intro -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-4a" class="step">
+<div class="sidebar">
+
+<p class="large"><img
+src="../static/img/zh-hans/screenshots/step4a-send-key-to-Edward.png"
+alt="第 4.A 步 向爱德华发送公钥" /></p>
+
+</div>
+<!-- /.sidebar -->
+<div class="main">
+
+<h3><em>第 4.a 步</em> 发送公钥给爱德华</h3>
+
+<p>这一步很特别，因为你和真人通信时不需要做。在你的邮件程序菜单中，选择“工具” →
+“OpenPGP密钥管理器”。你应当看到你的密钥在弹窗的列表中。在你的密钥处右键，选择“通过电子邮件发送公钥”。这会创建一封草稿消息，就好像你点击了“撰写”按钮，在附件中会看到你的公钥。</p>
+
+<p>收信人地址填写 <a
+href="mailto:edward-zh@fsf.org">edward-zh@fsf.org</a>。在邮件主题栏和正文里任意撰写内容。先别发送。</p>
+
+<p>我们希望爱德华能够打开你的密钥文件，因此我们需要第一封特别邮件是未经加密的。请下拉菜单“安全”，选择
+<i>不加密</i>，将加密关闭。加密关闭后，点击发送。</p>
+
+<p class="notes">爱德华可能需要两三分钟回复邮件。在这期间，你可以跳过前面的部分并阅读本指南<a
+href="#section6">善用加密</a>章节。爱德华回复后，继续下面的步骤。从这里开始，你所要做的与真人通信时相同。</p>
+
+<p>你打开爱德华的回复邮件，在使用私钥解密消息时，GnuPG 可能会提示要求输入密码。</p>
+
+</div>
+<!-- End .main -->
+</div>
+
+
+<!-- End #step-4a .step -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-4b" class="step">
+<div class="sidebar">
+
+<p class="large"><img
+src="../static/img/zh-hans/screenshots/step4b-option1-verify-key.png"
+alt="第 4.B 步 选项一 验证密钥" /></p>
+
+<p class="large"><img
+src="../static/img/zh-hans/screenshots/step4b-option2-import-key.png"
+alt="第 4.B 步 选项二 导入密钥" /></p>
+</div>
+
+<!-- /.sidebar -->
+<div class="main">
+
+<h3><em>第 4.b 步</em> 发送一封测试加密邮件</h3>
+
+<h4>获取爱德华的密钥</h4>
+
+<p>你需要爱德华的公钥才能给他发送加密邮件，因此你需要从密钥服务器下载它。有两种不同方式可以做到：</p>
+<p><strong>选项一</strong> 爱德华的公钥在它回复你的第一封邮件里。在邮件右侧，撰写区域的上方，你能够找到 OpenPGP
+按钮，旁边有锁和齿轮图标。点击它，选择“此消息是用您没有的密钥所签名的”旁边的 <i>寻找</i>。爱德华密钥的细节将会显示。</p>
+
+<p><strong>选项二</strong> 打开 OpenPGP 密钥管理器，在密钥服务器选择
+<i>在网上寻找密钥</i>。输入爱德华电子邮箱，导入密钥。</p>
+
+<p><i>接受 (未验证)</i> 选项将这个你要添加到密钥管理器，现在它将用于向爱德华发送加密电邮和验证数字签名。</p>
+
+<p class="notes">弹出窗口将确认是否导入爱德华密钥，你会看到这个密钥关联了许多邮箱。这没问题，你可以安全导入密钥。</p>
+
+<p class="notes">因为你使用了爱德华的公钥加密邮件，解密则就要求爱德华的私钥。爱德华是唯一有它私钥的人，因此除了他，没人能解密。</p>
+
+<h4>给爱德华发送一封加密邮件</h4>
+
+<p> 在你的邮件程序中写一封新的邮件，收信人地址填写 <a
+href="mailto:edward-zh@fsf.org">edward-zh@fsf.org</a>。在主题中填写“加密测试”或类似的词语，并在正文中写一些内容。</p>
+
+<p>这次，在下拉菜单“安全”里选择 <i>要求加密</i> 将加密开启。加密开启后，点击发送。</p>
+
+
+
+<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+<div class="troubleshooting">
+
+<h4>疑难解答</h4>
+
+<dl>
+<dt>“收件人不合法，不受信任或未找到”</dt>
+<dd>你可能会遇到上述错误提示，或是“由于下列收件人的密钥有问题，无法用端到端加密的方式发送此消息：……”这种情况很可能是由于你还没有收件人的公钥，根据上面步骤将密钥导入密钥管理器。打开
+OpenPGP 密钥管理器，确认收件人密钥在上面。</dd>
+
+<dt>无法发送消息</dt>
+<dd>当你尝试发送加密邮件时可能会遇到下列问题：“由于下列收件人的密钥有问题，无法用端到端加密的方式发送此消息：edward-zh@fsf.org。”则通常是导入密钥时选择了
+<i>不接受 (未决定) 选项</i>。到 OpenPGP 密钥管理器里选择此密钥，右键“密钥属性”，在窗口底部的“接受”选项中选择
+<i>接受，但我未验证过是否为正确密钥</i> 。重新发送邮件。</dd>
+
+<dt>我找不到爱德华的公钥</dt>
+<dd>关闭点击发送时的弹窗，确保你已经连接上因特网并再试一次。如果仍然无效，请手动在<a
+href="https://keys.openpgp.org/search?q=edward-en%40fsf.org">密钥服务器</a>下载密钥，并在
+OpenPGP 密钥管理器中选择 <i>从文件导入公钥</i> 选项导入密钥。</dd>
+
+<dt>已发送文件夹中解密的消息</dt>
+<dd>即便你无法解密用其他人公钥加密过的消息，你的邮件程序会自动用你的公钥保存一份副本，这就使得你能够在已发送文件夹像查看普通邮件一样查看它。这是正常的，它并不代表你已发的邮件没有被加密。</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>进阶指南</h4>
+
+<dl>
+<dt>使用命令行加密消息</dt>
+<dd>如果你喜欢，你也可以用<a
+href="https://www.gnupg.org/gph/en/manual/x110.html">命令行</a>加解密消息和文件。命令选项
+--armor 能够使加密输出显示为常规字符集。</dd>
+</dl>
+
+</div>
+<!-- /.troubleshooting -->
+</div>
+<!-- End .main -->
+</div>
+
+
+<!-- End #step-4b .step -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-headers_unencrypted" class="step">
+<div class="main">
+
+<h3><em>重要：</em> 安全提示</h3>
+
+<p>即便你加密了邮件，主题行是不受加密的，因此不要在主题里填写私人信息。发送人和接收人的邮件地址也是不经过加密的，因此监控系统可以知道你在和谁通信。同时，监控代理将会知道你使用了
+GnuPG，即便它不知道你在说什么。当你发送附件时，可以选择是否加密，加密附件是独立于真实邮件的。</p>
+
+<p>为了防范潜在的攻击，你可以关闭 HTML 格式，使用纯文本渲染正文。在 Icedove 和 Thunderbird 里，到 “查看” →
+“消息体为” → <i>纯文本</i> 可以做到这一点。</p>
+
+</div>
+<!-- End .main -->
+</div>
+
+
+<!-- End #step-headers_unencrypted .step-->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-4c" class="step">
+<div class="sidebar">
+
+<p class="large"><img
+src="../static/img/zh-hans/screenshots/step4c-Edward-response.png"
+alt="第 4.C 步 爱德华的回复" /></p>
+
+</div>
+
+<!-- /.sidebar -->
+<div class="main">
+
+<h3><em>第 4.c 步</em> 接收回信</h3>
+
+<p>当爱德华收到你的邮件，它会使用它的私钥去解密消息，并给你回复。 </p>
+
+<p class="notes">爱德华可能需要两三分钟回复邮件。在这期间，你可以跳过前面的部分并查阅本指南<a href="#section6">善用加密</a>章节。</p>
+
+<p>爱德华将用加密邮件给你回信，告知你的邮件已经收到并被解密。你的邮件客户端会自动解密爱德华的消息。</p>
+
+<p class="notes">邮件里的 OpenPGP
+将会在锁形图标上显示绿色标记，表明消息已经加密。橙色警告表明密钥已经被接受但未经验证。如果你未接受密钥，你会看到小问号标记。点击提示按钮将引导你设置密钥属性。</p>
+
+</div>
+<!-- End .main -->
+</div>
+
+
+<!-- End #step-4c .step -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-4d" class="step">
+<div class="main">
+
+<h3><em>第 4.d 步</em> 发送一封测试签名邮件</h3>
+
+<p>GnuPG
+提供了对消息或文件签名的方式，验证它们的确来自于你，并且始终未被篡改。这些签名比笔头签名更强有力——因为无法被伪造，没有你的私钥就无法签名（这是保护私钥安全另一个的原因）。</p>
+
+<p>你可以向任何人签名消息，因此让对方意识到你在使用 GnuPG——他们可以和你进行安全的通信——是个不错的主意。如果他们没有
+GnuPG，他们仍将有能力阅读你的消息并查看你的签名。如果他们有 GnuPG，他们将有能力验证你签名的真实性。</p>
+
+<p>要想对发给爱德华的邮件签名，并撰写一些消息给他，点击紧邻锁形图标的铅笔图标，它会变成金黄色。你要是对消息签名，GnuPG
+可能会在你点击发送消息前询问你密码，这是因为签名需要解锁私钥。</p>
+
+<p>在“账户设置” → “端到端加密”，你可以选择 <i>默认添加我的数字签名</i>。</p>
+
+</div>
+<!-- End .main -->
+</div>
+
+
+<!-- End #step-4d .step -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-4e" class="step">
+<div class="main">
+
+<h3><em>第 4.e 步</em> 接收回信</h3>
+
+<p>当爱德华收到你的邮件，他将会使用你的公钥（你在<a href="#step-3a">第 3.A
+步</a>发给他了）验证你发送的消息未经篡改，并以加密形式给你回复。</p>
+
+<p class="notes">爱德华可能需要两三分钟回复邮件。在这期间，你可以跳过前面的部分并查阅本指南<a href="#section6">善用加密</a>章节。</p>
+
+<p>爱德华的回复会是加密的，因为他应加密尽加密。如果一切顺利，他会回复“你的签名已被验证”。如果你的测试签名邮件也是加密的，他会优先提及。</p>
+
+<p>当你接收爱德华的邮件并打开它时，电邮程序会自动检测它是否使用你的公钥加密，接下来使用你的私钥解密消息。</p>
+
+</div>
+<!-- End .main -->
+</div>
+<!-- End #step-4e .step -->
+</div></section>
+
+
+<!-- ~~~~~~~~~ Section 5: Learn About the Web of Trust ~~~~~~~~~ -->
+<section class="row" id="section5"><div>
+
+
+<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+<div class="section-intro">
+
+<h2><em>#5</em> 了解信任网</h2>
+<p class="float small"><img src="../static/img/zh-hans/screenshots/section5-web-of-trust.png" alt="插图说明：各种密钥由交错的线网彼此连接在一起"/></p>
+
+<p>邮件加密是一种强有力的技术，但它有弱点：它要求验证某人的公钥的确是属于他的。否则，无法阻止攻击者使用你朋友姓名和邮件地址，生成密钥，进行冒充。这就是为什么自由软件程序员开发出密钥签名和信任网。</p>
+
+<p>当你签署了某人的公钥，相当于你公开声称这把公钥经你验证是属于他的，而不是其他人。</p>
+
+<p>签署密钥和消息签名使用了同种类型的数学运算，但有着不同的含义。通常，对自己邮件进行签名是一种良好实践，但随意签署别人的公钥，最终你会意外地为冒充者做了担保。</p>
+
+<p>使用你的公钥的人可以看到谁签署了此公钥。长期使用 GnuPG
+后，你的密钥可能有数百支签名。你可以认为，值得信任的人对这支公钥签名的数量越多，那么这支公钥越可信。信任网是 GnuPG
+用户的聚集地，他们用签名传递着信任链，连接彼此。</p>
+
+</div>
+
+
+<!-- End .section-intro -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-5a" class="step">
+<div class="sidebar">
+
+<p class="large"><img
+src="../static/img/zh-hans/screenshots/step5a-key-properties.png"
+alt="第 5 节：信任密钥" /></p>
+
+</div>
+<!-- /.sidebar -->
+<div class="main">
+
+<h3><em>第 5.a 步</em> 签署密钥</h3>
+
+<p>在电邮菜单中，找到 OpenPGP 密钥管理器，右键爱德华的密钥，选择<i>密钥属性</i>。</p>
+
+<p>在“您是否要接受”里，选择 <i>“接受，但我还未验证过是否为正确密钥”</i>。</p>
+
+<p class="notes">你刚刚有力地表达了“我信任爱德华的公钥，它的确属于爱德华”。由于爱德华是一个机器人，这对它并不意味着什么，但这是一个良好的实践。但对于真人，这很重要。在<a
+href="#check-ids-before-signing">签名前检查 ID</a> 章节阅读更多有关对其他人密钥签名的信息。</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" value="xD41A008"
+name="FROM"></p>
+
+<p><strong>To:</strong><input type="text" value="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-5a .step -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-identify_keys" class="step">
+<div class="main">
+
+<h3>验证密钥：指纹和 ID</h3>
+
+<p>密钥的指纹可以确认其对应使用的公钥，指纹是像 F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8
+（这是爱德华的密钥）的数字串。电邮程序菜单的 OpenPGP
+密钥管理，右键选择密钥属性，可以查看当前计算机中你和其他人的公钥指纹。在告诉他人你邮箱地址的同时，分享你的指纹是一个不错的实践，这样人们可以在从服务器下载你公钥的时候，再次检查下载的公钥是否正确。</p>
+
+<p class="notes">你可能已经看到有人使用短 key ID 表示公钥。密钥管理窗口中，你可以直接看到 key
+ID。这八位字符曾经用于表示身份，现已经不再安全可靠。你需要检查完整的指纹，以验证你拥有对方正确的密钥。不幸的是，有人故意生成的后六位指纹与另一支密钥相同的指纹进行伪造欺骗，这种情况是很常见的。</p>
+
+</div>
+<!-- End .main -->
+</div>
+
+
+<!-- End #step-identify_keys .step-->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="check-ids-before-signing" class="step">
+<div class="main">
+
+<h3><em>重要：</em> 签署密钥时需要考虑什么</h3>
+
+<p>在签署密钥前，你需要严格确认密钥是属于他的，的确是他自己所声称的那个人。这种确信来自逐步地沟通交流，以及目睹了他与其他人的交流过程。任何时候签署密钥都应该要求查看完整的公钥指纹，而不只是短
+key ID。如果你认为，所要签署人的公钥相当重要，可以要求他出示身份证明，确保身份证上的姓名与公钥的姓名相符。</p>
+
+
+<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+<div class="troubleshooting">
+
+<h4>进阶指南</h4>
+
+<dl>
+<dt>精通信任网</dt>
+<dd>不幸地是，信任并不是像<a
+href="http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">大多数人想象的</a>那样在用户之间传递。深入<a
+href="https://www.gnupg.org/gph/en/manual/x334.html">理解</a>信任网是如何运作的，并在条件允许的情况下，谨慎地对尽可能多的人的密钥进行签名，是增强
+GnuPG 社区的最佳方式之一。</dd>
+</dl>
+
+</div>
+<!-- /.troubleshooting -->
+</div>
+<!-- End .main -->
+</div>
+<!-- End #check-ids-before-signing .step-->
+</div></section>
+
+
+<!-- End #section5 -->
+<!-- ~~~~~~~~~ Section 6: Use it well ~~~~~~~~~ -->
+<section id="section6" class="row"><div>
+
+
+<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+<div class="section-intro">
+
+<h2><em>#6</em> 善用加密</h2>
+
+<p>每个人使用 GnuPG 方法不尽相同，遵循一些基本实践是保护邮件安全的重要方式。一旦不遵守，你便是拿着通信双方的隐私做冒险，并且危及信任网。</p>
+
+</div>
+
+
+<!-- End .section-intro -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-6a" class="step">
+<div class="sidebar">
+
+<p class="medium"><img
+src="../static/img/zh-hans/screenshots/section6-01-use-it-well.png"
+alt="第 6 节：善用加密（1）" /></p>
+
+</div>
+<!-- /.sidebar -->
+<div class="main">
+
+<h3>何时该加密？何时该签名？</h3>
+
+<p>加密消息是多多益善的。如果你只是偶然加密邮件，突兀的加密消息就像给监控系统发出警报。如果全部邮件都是加密的，监控人员将不知道从何处开始——这不是说加密部分邮件毫无帮助——它使大规模监控变得困难，这是重要的开始。</p>
+
+<p>除非你不想暴露身份（这还要求其他保护措施），每一封邮件都不签名是没有理由的，无论你是否加密。除了允许 GnuPG
+验证消息确实来自于你，签名是一种非侵入性的方式，提醒别人你在使用 GnuPG，并表示对安全通信的支持。如果你经常给不熟悉 GnuPG
+的人发送签名消息，在你的标准邮件签名（这里的签名指的是文字，而非密码学签名）中附上本指南的链接将会不错。</p>
+
+</div>
+<!-- End .main -->
+</div>
+
+
+<!-- End #step-6a .step -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-6b" class="step">
+<div class="sidebar">
+
+<p class="medium"><img
+src="../static/img/zh-hans/screenshots/section6-02-use-it-well.png"
+alt="第 6 节：善用加密（2）" /></p>
+
+</div>
+<!-- /.sidebar -->
+<div class="main">
+
+<h3>警惕非法密钥</h3>
+
+<p>GnuPG 能够使邮件更安全，但仍要小心非法密钥，它可能导致消息落入坏人之手。使用非法密钥加密的邮件可能能被监控程序读取。</p>
+
+<p>在邮件程序里，回到爱德华发给你的第一封加密邮件。因为爱德华用你的公钥加密了它，在 OpenPG 按钮上方会有一个绿色标记。</p>
+
+<p><strong>使用 GnuPG 时，要养成看通知条的习惯。如果你收到的邮件是用不受信任的密钥签名的，程序会提醒你。</strong></p>
+
+</div>
+<!-- End .main -->
+</div>
+
+
+<!-- End #step-6b .step -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-6c" class="step">
+<div class="main">
+
+<h3>备份吊销证书到安全的地方</h3>
+
+<p>还记得你何时生成密钥和保存 GnuPG
+生成的吊销证书的吗？该将证书备份到安全的数字储存设备上了——理想的地方是闪存盘、磁盘和硬盘，它们存放在家中安全的地方——而不是你随身携带的设备。我们已知的最安全方式是将吊销证书打印出来，保存在安全地方。</p>
+
+<p>如果你的私钥丢失或失窃，你需要这张证书文件让人们知道你不再使用这对密钥对。</p>
+
+</div>
+<!-- End .main -->
+</div>
+
+
+<!-- End #step-6c .step -->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-lost_key" class="step">
+<div class="main">
+
+<h3><em>重要：</em> 如果某人获得了你的私钥，要迅速行动</h3>
+
+<p>如果你丢失了私钥或是某人取得了它（比如你的计算机失窃或是被入侵），在其他人使用你私钥阅读你的加密邮件或是伪造签名前，立即吊销是非常重要的。本指南不包含如何吊销密钥，但你可以遵循这些<a
+href="https://www.hackdiary.com/2004/01/18/revoking-a-gpg-key/">指示</a>。在你吊销完成后，生成新的密钥对，并给所有使用你的密钥的人发送邮件，并附上新密钥的拷贝，确保他们知道发生了什么。</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>网页邮箱和 GnuPG</h3>
+
+<p>当你使用网页浏览器获取你的邮件，那么你使用的是网页邮箱，它是一个直接储存在网站里的电子邮件程序。和网页邮箱不同，你的桌面邮件程序是运行在你自己的计算机上。即使网页邮箱无法解密加密过的邮件，它仍然会以加密形式显示出来。如果你常用的是网页邮箱，当你收到一封混乱的电子邮件时，你应当知道去打开自己的电子邮件客户端。</p>
+
+</div>
+<!-- End .main -->
+</div>
+
+
+<!-- End #webmail-and-GnuPG .step-->
+<!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+<div id="step-6d" class="step">
+<div class="main">
+
+<h3>将公钥作为网络身份的组成部分</h3>
+
+<p> 在电子邮件签名里加入你的公钥指纹，给至少五位朋友撰写邮件，告诉他们你刚刚完成了 GnuPG
+的设置，以及你的公钥指纹是什么。将本指南链接发送给他们，让他们加入你的队伍。别忘了还有一幅很棒的<a
+href="infographic.html">信息图</a>值得分享。</p>
+
+<p class="notes">在所有显示你邮箱地址的地方，附上公钥指纹。这里有一些好地方：你的电子邮件签名（这里的签名指的是文字，而非密码学签名）、社交媒体简历、博客、网站和商务名片。在自由软件基金会，我们把它放在了<a
+href="https://fsf.org/about/staff">雇员页面</a>。我们需要创造一种文化：当我们看到电子邮箱地址却没有看到公钥指纹，就好像缺少了某样东西。</p>
+
+</div>
+<!-- End .main-->
+</div>
+<!-- End #step-6d .step-->
+</div></section>
+
+
+<!-- End #section6 -->
+<!-- ~~~~~~~~~ Section 7: Next steps ~~~~~~~~~ -->
+<section class="row" id="section7">
+<div id="step-click_here" class="step">
+<div class="main">
+
+<h2><a href="next_steps.html">很不错！继续查看下一步。</a></h2>
+
+</div>
+<!-- End .main -->
+</div>
+<!-- End #step-click_here .step-->
+</section>
+
+
+
+
+
+<!-- End #section7 -->
+<!-- ~~~~~~~~~ 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>
<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>
+<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>
+</section> -->
+<!-- End #faq -->
+<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
+<footer class="row" id="footer"><div>
+<div id="copyright">
+
+<h4><a href="https://u.fsf.org/ys"><img
+alt="自由软件基金会"
+src="../static/img/fsf-logo.png" /></a></h4>
+
+<p>Copyright © 2014-2021 <a href="https://u.fsf.org/ys">Free Software
+Foundation</a>, Inc. <a
+href="https://my.fsf.org/donate/privacypolicy.html">隐私政策</a>. <a
+href="https://u.fsf.org/yr">成为会员</a>，支持我们的工作。</p>
+
+<p>翻译：何旭鑫 <a href="mailto:hxxtom@gmail.com"><hxxtom@gmail.com> </a>,
+2017-2020, 2022. </p><p>此页面上的图片采用<a
+href="https://creativecommons.org/licenses/by/4.0/">知识共享 署名 4.0
+许可协议（或较新版本）</a>进行许可，其余部分以<a
+href="https://creativecommons.org/licenses/by-sa/4.0">知识共享 署名-相同方式 4.0
+许可协议（或较新版本）</a>进行许可。下载<a
+href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">爱德华自动回复机器人的源代码</a>，它由
+Andrew Engelbrecht <andrew@engelbrecht.io> 和 Josh Drake
+<zamnedix@gnu.org> 编写，采用 GNU Affero General Public License 许可证进行许可。<a
+href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">为什么使用这种许可协议？</a></p>
+
+<p>本指南和信息图所使用的字体：<a
+href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo
+Impallari, <a
+href="https://www.google.com/fonts/specimen/Signika">Signika</a> by Anna
+Giedryś, <a
+href="https://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>下载本指南（含字体、图片和爱德华邮件文本）的<a href="emailselfdefense_source.zip">源码包</a>。</p>
+
+<p>本站使用 Weblabels 标准标记<a href="https://www.fsf.org/campaigns/freejs">自由的
+JavaScript</a>。 查看 JavaScript <a
+href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
+rel="jslicense">源代码和许可证信息</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>
+</div>
- <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>
+<!-- /#copyright -->
+<p class="credits">信息图和指南由<a rel="external"
+href="http://jplusplus.org"><strong>Journalism++</strong>设计<img
+src="../static/img/jplusplus.png"
+alt="Journalism++" /></a></p>
+<!-- /.credits -->
+</div></footer>
- <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>
+<!-- End #footer -->
+<script type="text/javascript"
+src="../static/js/jquery-1.11.0.min.js"></script>
+<script type="text/javascript"
+src="../static/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 -->
-
-
-
+<script type="text/javascript">
+ // @license magnet:?xt=urn:btih:cf05388f2679ee054f2beb29a391d25f4e673ac3&dn=gpl-2.0.txt GPL-2.0-or-later
+ var _paq = _paq || [];
+ _paq.push(["trackPageView"]);
+ _paq.push(["enableLinkTracking"]);
+
+ (function() {
+ var u = (("https:" == document.location.protocol) ? "https" : "http") + "://"+"piwik.fsf.org//";
+ _paq.push(["setTrackerUrl", u+"piwik.php"]);
+ _paq.push(["setSiteId", "13"]);
+ var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
+ g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
+ })();
+ // @license-end
+</script>
+
+
+<!-- End Piwik Code -->
+<!-- Piwik Image Tracker -->
+<noscript><img src="https://piwik.fsf.org//piwik.php?idsite=13&rec=1" style="border:0" alt="" /></noscript>
+
+<!-- End Piwik -->
</body>
</html>
projects / enc.git / blobdiff