mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
TSL&PRF
This commit is contained in:
Xingyu Wang
parent
296fc2aa26
commit
20f3262694
@ -1,268 +0,0 @@
|
||||
[#]: subject: "Using GPG to Encrypt and Decrypt Files on Linux [Hands-on for Beginners]"
|
||||
[#]: via: "https://itsfoss.com/gpg-encrypt-files-basic/"
|
||||
[#]: author: "Hunter Wittenborn https://itsfoss.com/author/hunter/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "wxy"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Using GPG to Encrypt and Decrypt Files on Linux [Hands-on for Beginners]
|
||||
======
|
||||
|
||||
[GnuPG][1], popularly known as GPG, is an extremely versatile tool, being widely used as the industry standard for encryption of things like emails, messages, files, or just anything you need to send to someone securely.
|
||||
|
||||
It’s easy to get started with GPG, and you can be on your way with using it in a matter of minutes.
|
||||
|
||||
In this tutorial, I’ll show you how to encrypt and decrypt files with GPG. _**This is a simple tutorial and you may try all of it to practice on your Linux system as well. This will help you practice the GPG commands and understand it when you are absolutely new to it.**_
|
||||
|
||||
Read the entire tutorial first and then start doing it on your own.
|
||||
|
||||
### How does GPG work for encryption?
|
||||
|
||||
![GPG encryption][2]
|
||||
|
||||
To start using GPG, you’ll first need to have a GPG key.
|
||||
|
||||
A GPG key is what you’ll use to encrypt (or decrypt) files later in the tutorial. It’s also what is used to identity you, with things like your name and email being tied to the key as well.
|
||||
|
||||
GPG keys work by using two files, a private key and a public key. These two keys are tied to each other, and are both needed to use all of GPG’s functionality, notably encrypting and decrypting files.
|
||||
|
||||
When you encrypt a file with GPG, it uses the private key. The new, encrypted file can then **only** be _decrypted_ with the paired public key.
|
||||
|
||||
The private key is meant to be stored in a fashion stated directly in its name – privately, and not given out to anyone.
|
||||
|
||||
The public key on the other hand is meant to be given to others, or anyone you want to be able to decrypt your files.
|
||||
|
||||
This is where GPG’s main approach for encryption comes into play. It allows you to encrypt files locally and then allow others to be ensured that the files they received were actually sent from you. As the only way they’ll be able to _decrypt_ the file is with _your_ public key, which would only work if the file was _encrypted_ using _your_ private key in the first place.
|
||||
|
||||
_**This also works in the opposite direction!**_ Other people can encrypt files using your public key, and the only way it’ll be able to be decrypted is with your private key. Thus allowing others to publicly post files without worry of people besides you being able to read them.
|
||||
|
||||
_**In other words, if a file was encrypted with a private key, it can only be decrypted with the corresponding public key. And if a file was encrypted with a public key, it can only be decrypted with the corresponding private key.**_
|
||||
|
||||
#### You are already using GPG without realizing
|
||||
|
||||
One of the most common example of using GPG is in Linux package manager, specially the [external repositories][3]. You add the public key of the developer into your system’s trusted keys. The developer signs the packages (generates a signature) with his/her private key. Since your Linux system has the public file, it understands that the package is actually coming from the trusted developer.
|
||||
|
||||
A number of encrypted services use some sort of GPG implementation underneath without you realizing it. But it’s better to not go in to those details right now.
|
||||
|
||||
Now that you are a bit familiar with the concept, let’s see how you can use GPG for encrypting a file and then use it to decrypt.
|
||||
|
||||
### Encrypting and decrypting files with GPG
|
||||
|
||||
![][4]
|
||||
|
||||
This is a very simplistic scenario. I presume that you have just one system and you want to see how GPG works. You are not sending the files to other system. You encrypt the file and then decrypt it on the same system.
|
||||
|
||||
Of course, this is not a practical use case but that’s also not the purpose of this tutorial. My aim is to get you acquainted with GPG commands and functioning. After that, you can use this knowledge in a real-world situation (if need be). And for that, I’ll show you how you can share your public key with others.
|
||||
|
||||
#### Step 1: Installing GPG
|
||||
|
||||
GPG can be found in most distribution’s repositories out of the box.
|
||||
|
||||
On Debian and Ubuntu-based systems, install the gpg package:
|
||||
|
||||
```
|
||||
|
||||
sudo apt install gpg
|
||||
|
||||
```
|
||||
|
||||
If you use [Arch based distributions][5], install the gnupg package with the [pacman command][6]:
|
||||
|
||||
```
|
||||
|
||||
sudo pacman -S gnupg
|
||||
|
||||
```
|
||||
|
||||
#### Step 2: Generating a GPG key
|
||||
|
||||
Generating a GPG key on your system is a simple one-command procedure.
|
||||
|
||||
Just run the following command, and your key will be generated (you can use the defaults for most questions as shown in the underlined sections below):
|
||||
|
||||
```
|
||||
|
||||
gpg --full-generate-key
|
||||
|
||||
```
|
||||
|
||||
![Generating GPG keys][7]
|
||||
|
||||
**Checking the GPG Key**
|
||||
|
||||
You can then see that the private key and public key are both tied to each other by that ID shown under **pub** by using the **–list-secret-keys** and **–list-public-keys** commands respectively:
|
||||
|
||||
![Listing GPG keys][8]
|
||||
|
||||
#### Step 3: Encrypting a file with GPG
|
||||
|
||||
Now that you’ve set up our GPG keys, you can start encrypting our files!
|
||||
|
||||
Use the following command to encrypt files:
|
||||
|
||||
```
|
||||
|
||||
gpg --encrypt --output file.gpg --recipient [email protected] file
|
||||
|
||||
```
|
||||
|
||||
Let’s go over what that command does real quick:
|
||||
|
||||
First you specified the **–encrypt** option. This simply tells GPG that we’ll be encrypting a file.
|
||||
|
||||
Next, you specified **–output file.gpg**. This can be anything, though it’s typically the name of the file you’re encrypting plus a **.gpg** extension (so **message.txt** would become **message.txt.gpg**).
|
||||
|
||||
Next, you type **–recipient [[email protected]][9]**. This specifies the email for a corresponding GPG key that actually doesn’t exist quite yet on this system.
|
||||
|
||||
Still confused?
|
||||
|
||||
The way this works is that the email you specify here must be tied to a public key on your local system.
|
||||
|
||||
Typically, this is going to be from the public GPG key of a different person, which is what you’re going to encrypt your file with. After such, the file will only be able to be decrypted with that user’s private key.
|
||||
|
||||
I’ll be using my previous GPG key with the **[[email protected]][9]** in this example. Thus, the logic would be that I am encrypting the file with the _public_ key of h**[[email protected]][9]**, which is then only going to be able to be decrypted with the _private_ key of **[[email protected]][9]**.
|
||||
|
||||
You’d only have the public key if you were encrypting a file for someone else, but since you’re encrypting the file for yourself, you have both keys on your system.
|
||||
|
||||
Lastly, you simply specify the file you’re going to encrypt. For this example, let’s use a file named **message.txt** with the following content:
|
||||
|
||||
```
|
||||
|
||||
We're encrypting with GPG!
|
||||
|
||||
```
|
||||
|
||||
![Sample text file][10]
|
||||
|
||||
Likewise, if the email was **[[email protected]][9]**, the new GPG command would be as follows:
|
||||
|
||||
```
|
||||
|
||||
gpg --encrypt --output message.txt.gpg --recipient [email protected] message.txt
|
||||
|
||||
```
|
||||
|
||||
![Encrypting file with GPG][11]
|
||||
|
||||
If you then try to read the file, you’ll see that it looks like gibberish. That is expected because the file is encrypted now:
|
||||
|
||||
![Reading the encrypted file generates gibberish text][12]
|
||||
|
||||
Let’s now delete the unencrypted message.txt file so that you can see that the message.txt.gpg file actually decrypts just fine without the original file:
|
||||
|
||||
![][13]
|
||||
|
||||
#### Step 4: Decrypting the encrypted file with GPG
|
||||
|
||||
Lastly, let’s actually decrypt the encrypted message. You can do such using the following command:
|
||||
|
||||
```
|
||||
|
||||
gpg --decrypt --output file file.gpg
|
||||
|
||||
```
|
||||
|
||||
Going through the argument here, we first specify **–decrypt**, which tells GPG that you’re going to be decrypting a file.
|
||||
|
||||
Next, you enter **–output** file, which simply tells GPG what file you’ll be saving the encrypted form of our file to after you decrypt it.
|
||||
|
||||
Lastly, you enter **file.gpg**, which is just the path to your encrypted file.
|
||||
|
||||
Following the example, the command I’d use would be as follows:
|
||||
|
||||
```
|
||||
|
||||
gpg --decrypt --output message.txt message.txt.gpg
|
||||
|
||||
```
|
||||
|
||||
![Decrypting file with GPG][14]
|
||||
|
||||
And voila, you’re done! That’s all there is to it when you want to encrypt and decrypt files with GPG.
|
||||
|
||||
The only other thing you may want to know is how to share your public keys with others so they can encrypt files before sending them to you.
|
||||
|
||||
### Sending and receiving GPG Keys
|
||||
|
||||
To send someone a GPG key, you’ll first need to export it from your **keychain**, which is what contains all of your public and private keys.
|
||||
|
||||
To export a key, simply find the key ID in your keychain, and then run the following command, replacing `id` with the key’s ID and **key.gpg** with the name of the file you want to save to:
|
||||
|
||||
```
|
||||
|
||||
gpg --output key.gpg --export id
|
||||
|
||||
```
|
||||
|
||||
![Export GPG public key][15]
|
||||
|
||||
To import a key, simply give the output file (from the previous command) to the other user and then have them run the following command:
|
||||
|
||||
```
|
||||
|
||||
gpg --import key.gpg
|
||||
|
||||
```
|
||||
|
||||
![][16]
|
||||
|
||||
To use the key normally though, you’ll need to verify the key so GPG properly trusts it.
|
||||
|
||||
This can be done by running the **–edit-key** command on the other user’s system, following by signing the key:
|
||||
|
||||
First run `gpg --edit-key id`:
|
||||
|
||||
![GPG edit key][17]
|
||||
|
||||
Next, run the **fpr** command, which will show the fingerprint for the key. The output of this command should be validated against the output on your own machine, which can be found by running the same **–edit-key** command on your system:
|
||||
|
||||
![Fingerprint of GPG key][18]
|
||||
|
||||
If everything matches up, just run the **sign** command and everything will be ready to go:
|
||||
|
||||
![Sign GPG key][19]
|
||||
|
||||
That’s it! The other user can now start encrypting files with your public key just as you did earlier, ensuring they’ll only be readable by you when you decrypt them with your private key.
|
||||
|
||||
And that’s all the basics to GPG!
|
||||
|
||||
### Wrapping Up
|
||||
|
||||
You’ve now gone over everything you need to start using GPG, including encrypting files for yourself and for others. As I mentioned earlier, this is just for understanding how GPG encryption and decryption process works. The basic GPG knowledge you just acquired can be taken to the next level when applied in real-world scenarios.
|
||||
|
||||
Need some help figuring out something still, or something just not working right? Feel free to leave any of it in the comments below.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/gpg-encrypt-files-basic/
|
||||
|
||||
作者：[Hunter Wittenborn][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/hunter/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://gnupg.org/
|
||||
[2]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2021/12/GPG-encryption-explained.png?resize=800%2C300&ssl=1
|
||||
[3]: https://itsfoss.com/adding-external-repositories-ubuntu/
|
||||
[4]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/12/GPG-encryption-basic.png?resize=800%2C450&ssl=1
|
||||
[5]: https://itsfoss.com/arch-based-linux-distros/
|
||||
[6]: https://itsfoss.com/pacman-command/
|
||||
[7]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-key-generation.png?resize=676%2C663&ssl=1
|
||||
[8]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-list-keys-1.png?resize=703%2C379&ssl=1
|
||||
[9]: https://itsfoss.com/cdn-cgi/l/email-protection
|
||||
[10]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-example-message.png?resize=665%2C277&ssl=1
|
||||
[11]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-example-message-encrypted-800x252.png?resize=800%2C252&ssl=1
|
||||
[12]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-example-message-encrypted-gibberish.png?resize=800%2C252&ssl=1
|
||||
[13]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-message-original-deleted.png?resize=800%2C252&ssl=1
|
||||
[14]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-message-decrypt.png?resize=800%2C252&ssl=1
|
||||
[15]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-key-export-800x218.png?resize=800%2C218&ssl=1
|
||||
[16]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-key-import.png?resize=800%2C221&ssl=1
|
||||
[17]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-edit-key-prompt.png?resize=800%2C351&ssl=1
|
||||
[18]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-edit-key-fingerprint-1.png?resize=800%2C317&ssl=1
|
||||
[19]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-edit-key-sign.png?resize=800%2C531&ssl=1
|
||||
@ -0,0 +1,248 @@
|
||||
[#]: subject: "Using GPG to Encrypt and Decrypt Files on Linux [Hands-on for Beginners]"
|
||||
[#]: via: "https://itsfoss.com/gpg-encrypt-files-basic/"
|
||||
[#]: author: "Hunter Wittenborn https://itsfoss.com/author/hunter/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "wxy"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
手把手指导：在 Linux 上使用 GPG 加解密文件
|
||||
======
|
||||
|
||||
[GnuPG][1]，俗称 GPG，是一个非常通用的工具，被广泛用作电子邮件、信息、文件或任何你需要安全地发送给别人的东西的加密行业标准。
|
||||
|
||||
学习使用 GPG 很容易，你可以在几分钟内就学会使用它。
|
||||
|
||||
在本教程中，我将告诉你如何用 GPG 加密和解密文件。这是一个简单的教程，你可以在你的 Linux 系统上尝试所有的练习。这将帮助你练习 GPG 命令，并在你完全陌生的情况下理解它。
|
||||
|
||||
先阅读整个教程，然后开始自己做。
|
||||
|
||||
### GPG 是如何进行加密的？
|
||||
|
||||
![GPG 加密][2]
|
||||
|
||||
要使用 GPG，你首先需要有一个 GPG 密钥。
|
||||
|
||||
GPG 密钥是你在后面的教程中用来加密（或解密）文件的东西。它也是用来识别你的身份的，你的名字和电子邮件也会与密钥绑定。
|
||||
|
||||
GPG 密钥的工作原理是使用两个文件，一个私钥和一个公钥。这两个密钥是相互联系的，并且 GPG 的所有功能都需要使用它们，特别是对文件加密和解密。
|
||||
|
||||
当你用 GPG 加密一个文件时，它使用的是私钥。然后，这个新的加密文件**只能**用配对的公钥进行解密。
|
||||
|
||||
私钥，顾名思义，是以私下的、不给任何人看的方式来存储的密钥。
|
||||
|
||||
另一方面，公钥是用来给其他人的，或者你希望能够解密你的文件的任何人。（LCTT 译注：更多的用例是用来验证你的签名。）
|
||||
|
||||
这就是 GPG 的主要加密方法的作用所在。它允许你对文件进行本地加密，然后允许其他人确保他们收到的文件实际上是由你发送的。因为他们能够解密文件的唯一方法是使用你的公钥，而这只有在文件首先使用你的私钥加密的情况下才有效。
|
||||
|
||||
**反之**，其他人可以用你的公钥对文件进行加密，而唯一能够解密的方法是用你的私钥。因此，允许其他人公开发布文件，而不用担心除了你以外的人能够阅读它们。
|
||||
|
||||
换句话说，如果一个文件是用私钥加密的，它只能用相应的公钥解密。而如果一个文件是用公钥加密的，它只能用相应的私钥解密。
|
||||
|
||||
#### 你已经在使用 GPG 而没有意识到
|
||||
|
||||
一个最常见的使用 GPG 的例子是在 Linux 软件包管理器中，特别是 [外部仓库][3]。你把开发者的公钥添加到你系统的可信密钥中。开发者用他/她的私钥签署软件包（生成签名）。由于你的 Linux 系统拥有该公钥文件，它就能理解该软件包实际上是来自受信任的开发者。
|
||||
|
||||
许多加密服务在你没有意识到的情况下使用了某种 GPG 的实现。但现在最好不要去研究这些细节。
|
||||
|
||||
现在你对这个概念有点熟悉了，让我们看看如何使用 GPG 来加密一个文件，然后用它来解密。
|
||||
|
||||
### 用 GPG 对文件进行加密和解密
|
||||
|
||||
![][4]
|
||||
|
||||
这是一个非常简单的场景。我假定你只有一个系统，你想看看 GPG 是如何工作的。你并没有把文件发送到其他系统。你对文件进行加密，然后在同一个系统上解密。
|
||||
|
||||
当然，这不是一个实际的用例，但这也不是本教程的目的。我的目的是让你熟悉 GPG 命令和功能。之后，你可以在现实世界中使用这些知识（如果需要的话）。为此，我将告诉你如何与他人分享你的公钥。
|
||||
|
||||
#### 第一步：安装 GPG
|
||||
|
||||
GPG 可以在大多数发行版的软件库中找到，开箱即用。
|
||||
|
||||
在基于 Debian 和 Ubuntu 的系统中，安装 `gpg` 包：
|
||||
|
||||
```
|
||||
sudo apt install gpg
|
||||
```
|
||||
|
||||
如果你使用 [基于 Arch 的发行版][5]，用 [pacman 命令][6] 安装 `gnupg` 软件包：
|
||||
|
||||
```
|
||||
sudo pacman -S gnupg
|
||||
```
|
||||
|
||||
#### 第二步：生成一个 GPG 密钥
|
||||
|
||||
在你的系统上生成一个 GPG 密钥只需要一条简单的命令。
|
||||
|
||||
只要运行下面的命令，就会生成你的密钥（你可以对大多数问题使用默认值，如下面的下划线部分所示）。
|
||||
|
||||
```
|
||||
gpg --full-generate-key
|
||||
```
|
||||
|
||||
![生成 GPG 密钥][7]
|
||||
|
||||
**检查 GPG 密钥**
|
||||
|
||||
然后你可以通过使用 `--list-secret-keys` 和 `--list-public-keys` 参数，分别看到私钥和公钥都是通过 `pub` 下显示的那个 ID 相互绑定的。
|
||||
|
||||
![列出 GPG 密钥][8]
|
||||
|
||||
#### 第三步：用 GPG 加密一个文件
|
||||
|
||||
现在你已经设置了 GPG 密钥，你可以开始对我们的文件进行加密了。
|
||||
|
||||
使用下面的命令来加密文件：
|
||||
|
||||
```
|
||||
gpg --encrypt --output file.gpg --recipient user@example.com file
|
||||
```
|
||||
|
||||
让我们快速浏览一下该命令的内容：
|
||||
|
||||
首先，你指定了 `—encrypt` 选项。这只是告诉 GPG，我们将对一个文件进行加密。
|
||||
|
||||
接下来，你指定了 `--output file.gpg`。这可以是任何名字，不过惯例是给你要加密的文件的名称加上 `.gpg` 扩展名（所以 `message.txt` 会变成 `message.txt.gpg`）。
|
||||
|
||||
接下来，你输入 `—recipient user@example.com`。这指定了一个相应的 GPG 密钥的电子邮件，这个密钥实际上在这个系统上还不存在。
|
||||
|
||||
有点迷惑？
|
||||
|
||||
工作原理是，你在这里指定的电子邮件必须与你本地系统中的公钥相联系。
|
||||
|
||||
通常情况下，这将是来自一个另外的人的 GPG 公钥，你要用它来加密你的文件。之后，该文件将只能用该用户的私钥进行解密。
|
||||
|
||||
在这个例子中，我将使用我以前的与 `user@example.com` 关联的 GPG 密钥。因此，其逻辑是，我用 `user@example.com` 的 _公钥_ 对文件进行加密，然后只能用 `user@example.com` 的 _私钥_ 进行解密。
|
||||
|
||||
如果你是为别人加密文件，你只有该公钥，但由于你是为自己加密文件，你的系统上有这两个密钥。
|
||||
|
||||
最后，你只需指定你要加密的文件。在这个例子中，让我们使用一个名为 `message.txt` 的文件，内容如下：
|
||||
|
||||
```
|
||||
We're encrypting with GPG!
|
||||
```
|
||||
|
||||
![文本文件样本][10]
|
||||
|
||||
同样地，如果电子邮件是 `user@example.com`，新的 GPG 命令将如下所示：
|
||||
|
||||
```
|
||||
gpg --encrypt --output message.txt.gpg --recipient user@example.com message.txt
|
||||
```
|
||||
|
||||
![用 GPG 加密文件][11]
|
||||
|
||||
如果你尝试阅读该文件，你会看到它看起来像乱码。这是预料之中的，因为该文件现在已经被加密了。
|
||||
|
||||
![读取加密文件会产生乱码][12]
|
||||
|
||||
现在让我们删除未加密的 `message.txt` 文件，这样你就可以看到 `message.txt.gpg` 文件实际上在没有原始文件的情况下也能正常解密。
|
||||
|
||||
![][13]
|
||||
|
||||
#### 第四步：用 GPG 解密加密的文件
|
||||
|
||||
最后，让我们来实际解密加密的信息。你可以用下面的命令来做。
|
||||
|
||||
```
|
||||
gpg --decrypt --output file file.gpg
|
||||
```
|
||||
|
||||
通过这里的参数，我们首先指定 `—decrypt`，它告诉 GPG 你将会解密一个文件。
|
||||
|
||||
接下来，你输入 `—output` 文件，这只是告诉 GPG，在你解密后，你将把我们文件的解密形式保存到哪个文件。
|
||||
|
||||
最后，你输入 `file.gpg`，这是你的加密文件的路径。
|
||||
|
||||
按照这个例子，我使用的命令是这样的。
|
||||
|
||||
```
|
||||
gpg --decrypt --output message.txt message.txt.gpg
|
||||
```
|
||||
|
||||
![用GPG解密文件][14]
|
||||
|
||||
然后就完成了！当你想用 GPG 加密和解密文件时，这就是全部内容了。
|
||||
|
||||
剩下你可能想知道的是如何与他人分享你的公钥，以便他们在将文件发送给你之前对其进行加密。
|
||||
|
||||
### 发送和接收 GPG 密钥
|
||||
|
||||
要给别人发送一个 GPG 密钥，你首先需要从你的**钥匙链**中导出它，它包含了你所有的公钥和私钥。
|
||||
|
||||
要导出一把钥匙，只需在你的钥匙链中找到钥匙的 ID，然后运行以下命令，用钥匙的 ID 替换 `id`，用你想保存的文件名替换 `key.gpg`。
|
||||
|
||||
```
|
||||
gpg --output key.gpg --export id
|
||||
```
|
||||
|
||||
![导出 GPG 公钥][15]
|
||||
|
||||
要导入一个密钥，只需把输出文件（来自前面的命令）给其他用户，然后让他们运行下面的命令。
|
||||
|
||||
```
|
||||
gpg --import key.gpg
|
||||
```
|
||||
|
||||
![][16]
|
||||
|
||||
但要正常使用该钥匙，你需要验证该钥匙，以便 GPG 正确地信任它。
|
||||
|
||||
这可以通过在其他用户的系统上使用 `--edit-key` 参数来完成，然后对钥匙进行签名。
|
||||
|
||||
首先运行 `gpg --edit-key id`：
|
||||
|
||||
![GPG 编辑密钥][17]
|
||||
|
||||
接下来，使用 `—fpr` 参数，它将显示钥匙的指纹。这个命令的输出应该与你自己机器上的输出进行验证，这可以通过在你的系统上运行同样的 `--edit-key` 参数来找到。
|
||||
|
||||
![GPG 密钥的指纹][18]
|
||||
|
||||
如果一切吻合，只需使用 `—sign` 参数，一切就可以开始了。
|
||||
|
||||
![签署 GPG 密钥][19]
|
||||
|
||||
就是这样！其他用户现在可以开始用你的公钥加密文件了，就像你之前做的那样，确保它们只有在你用你的私钥解密时才能被你读取。
|
||||
|
||||
这就是使用 GPG 的所有基础知识！
|
||||
|
||||
### 总结
|
||||
|
||||
现在你已经了解了开始使用 GPG 所需要的一切，包括为自己和他人加密文件。正如我前面提到的，这只是为了了解 GPG 的加密和解密过程是如何工作的。你刚刚获得的基本 GPG 知识在应用于真实世界的场景中时可以更上一层楼。
|
||||
|
||||
还需要一些帮助来弄清楚一些东西，或者一些不正常的东西？欢迎在下面的评论中留下任何内容。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/gpg-encrypt-files-basic/
|
||||
|
||||
作者：[Hunter Wittenborn][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[wxy](https://github.com/wxy)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/hunter/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://gnupg.org/
|
||||
[2]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2021/12/GPG-encryption-explained.png?resize=800%2C300&ssl=1
|
||||
[3]: https://itsfoss.com/adding-external-repositories-ubuntu/
|
||||
[4]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/12/GPG-encryption-basic.png?resize=800%2C450&ssl=1
|
||||
[5]: https://itsfoss.com/arch-based-linux-distros/
|
||||
[6]: https://itsfoss.com/pacman-command/
|
||||
[7]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-key-generation.png?resize=676%2C663&ssl=1
|
||||
[8]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-list-keys-1.png?resize=703%2C379&ssl=1
|
||||
[9]: https://itsfoss.com/cdn-cgi/l/email-protection
|
||||
[10]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-example-message.png?resize=665%2C277&ssl=1
|
||||
[11]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-example-message-encrypted-800x252.png?resize=800%2C252&ssl=1
|
||||
[12]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-example-message-encrypted-gibberish.png?resize=800%2C252&ssl=1
|
||||
[13]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-message-original-deleted.png?resize=800%2C252&ssl=1
|
||||
[14]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-message-decrypt.png?resize=800%2C252&ssl=1
|
||||
[15]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-key-export-800x218.png?resize=800%2C218&ssl=1
|
||||
[16]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-key-import.png?resize=800%2C221&ssl=1
|
||||
[17]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-edit-key-prompt.png?resize=800%2C351&ssl=1
|
||||
[18]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-edit-key-fingerprint-1.png?resize=800%2C317&ssl=1
|
||||
[19]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2021/11/gpg-edit-key-sign.png?resize=800%2C531&ssl=1
|
||||
Loading…
Reference in New Issue
Block a user