# 签名密钥

所有带 Tag 的 ZFS on Linux [RELEASE](https://github.com/zfsonlinux/zfs/releases) 都由该分支的官方维护者签名。这些签名会被 GitHub 自动验证，也可以通过下载维护者的公钥在本地进行验证。

## 维护者

### 发布分支 (spl/zfs-\*-release)

**维护者：** [Ned Bass](https://github.com/nedbass)

**下载：** [pgp.mit.edu](http://pgp.mit.edu/pks/lookup?op=vindex\&search=0xB97467AAC77B9667\&fingerprint=on)

**密钥 ID：** C77B9667

**指纹：** 29D5 610E AE29 41E3 55A2 FE8A B974 67AA C77B 9667

**维护者：** [Tony Hutter](https://github.com/tonyhutter)

**下载：** [pgp.mit.edu](http://pgp.mit.edu/pks/lookup?op=vindex\&search=0x6ad860eed4598027\&fingerprint=on)

**密钥 ID：** D4598027

**指纹：** 4F3B A9AB 6D1F 8D68 3DC2 DFB5 6AD8 60EE D459 8027

### 主分支 (master)

**维护者：** [Brian Behlendorf](https://github.com/behlendorf)

**下载：** [pgp.mit.edu](http://pgp.mit.edu/pks/lookup?op=vindex\&search=0x0AB9E991C6AF658B\&fingerprint=on)

**密钥 ID：** C6AF658B

**指纹：** C33D F142 657E D1F7 C328 A296 0AB9 E991 C6AF 658B

## 检查 Git 标签的签名

首先将上面列出的公钥导入到你的密钥环中。

```sh
$ gpg --keyserver pgp.mit.edu --recv C6AF658B
gpg: requesting key C6AF658B from hkp server pgp.mit.edu
gpg: key C6AF658B: "Brian Behlendorf <behlendorf1@llnl.gov>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
```

导入公钥后，可以按如下方式验证 git 标签的签名。

```sh
$ git tag --verify zfs-0.6.5
object 7a27ad00ae142b38d4aef8cc0af7a72b4c0e44fe
type commit
tag zfs-0.6.5
tagger Brian Behlendorf <behlendorf1@llnl.gov> 1441996302 -0700

ZFS Version 0.6.5
gpg: Signature made Fri 11 Sep 2015 11:31:42 AM PDT using DSA key ID C6AF658B
gpg: Good signature from "Brian Behlendorf <behlendorf1@llnl.gov>"
gpg:                 aka "Brian Behlendorf (LLNL) <behlendorf1@llnl.gov>"
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://book.bsdcn.org/zfs/xiang-mu-yu-she-qu/signingkeys.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.