对于PostgreSQL 12： 1. hostssl giteadb gitea 192.0.2.10/32 scram-sha-256 clientcert=verify-full 对于PostgreSQL 11及更早版本： 1. hostssl giteadb gitea 192.0.2.10/32 scram-sha-256 .key ~/.postgresql/root.crt 8. 测试与数据库的连接： 1. psql "postgres://gitea@example.db/giteadb?sslmode=verify-full" 您将被提示输入数据库用户的密码，然后连接到数据库。 虽然 Gitea 使用的MySQL驱动程序也支持双向 TLS，但目前 Gitea 仅支持单向 TLS。有关详细信息，请参见工 的一致性。 1. gpg --keyserver keys.openpgp.org --recv 7C9E68152594688862D62AF62D9AE806EC1592E2 2. gpg --verify gitea-1.21.1-linux-amd64.asc gitea-1.21.1-linux-amd64 校验正确时的信息为 Good signature from "Teabot

0 码力 | 303 页 | 3.88 MB | 1 年前

3

version is on the GitHub page, but the kernel.org page also has release signatures if you want to verify your download. Then, compile and install: $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure that it was, it stages the file to mark it as resolved for you. You can run git status again to verify that all conflicts have been resolved: $ git status On branch master All conflicts fixed but you merge) Changes to be committed: modified: index.html If you’re happy with that, and you verify that everything that had conflicts has been staged, you can type git commit to finalize the merge

version is on the GitHub page, but the kernel.org page also has release signatures if you want to verify your download. Then, compile and install: $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure that it was, it stages the file to mark it as resolved for you. You can run git status again to verify that all conflicts have been resolved: $ git status On branch master All conflicts fixed but you merge) Changes to be committed: modified: index.html If you’re happy with that, and you verify that everything that had conflicts has been staged, you can type git commit to finalize the merge

version is on the GitHub page, but the kernel.org page also has release signatures if you want to verify your download. Then, compile and install: $ tar -zxf git-2.8.0.tar.gz $ cd git-2.8.0 $ make configure that it was, it stages the file to mark it as resolved for you. You can run git status again to verify that all conflicts have been resolved: $ git status On branch master All conflicts fixed but you merge) Changes to be committed: modified: index.html If you’re happy with that, and you verify that everything that had conflicts has been staged, you can type git commit to finalize the merge

2006 PDT using DSA key ID F3119B9A gpg: Can't check signature: public key not found error: could not verify the tag 'v1.4.2.1' 签署提交 在最新版本的 Git 中（v1.7.9 及以上），也可以签署个人提交。 如果相对于标签而言你对直接签署到提交更感兴 趣的话，所有要做的只是增加一个 3 及以后的版本中，git merge 与 git pull 可以使用 --verify-signatures 选项来检查并拒绝没有携带可信 GPG 签名的提交。 如果使用这个选项来合并一个包含未签名或有效的提交的分支时，合并不会生效。 $ git merge --verify-signatures non-verify fatal: Commit ab06180 does not have a a GPG signature. 如果合并包含的只有有效的签名的提交，合并命令会提示所有的签名它已经检查过了然后会继续向前。 $ git merge --verify-signatures signed-branch Commit 13ad65e has a good GPG signature by Scott Chacon (Git signing key)

2006 PDT using DSA key ID F3119B9A gpg: Can't check signature: public key not found error: could not verify the tag 'v1.4.2.1' 签署提交 在最新版本的 Git 中（v1.7.9 及以上），也可以签署个人提交。 如果相对于标 签而言你对直接签署到提交更感兴趣的话，所有要做的只是增加一个 及以后的版本中，git merge 与 git pull 可以使用 --verify- signatures 选项来检查并拒绝没有携带可信 GPG 签名的提交。 如果使用这个选项来合并一个包含未签名或有效的提交的分支时，合并不会生 效。 $ git merge --verify-signatures non-verify fatal: Commit ab06180 does not have have a GPG signature. 如果合并包含的只有有效的签名的提交，合并命令会提示所有的签名它已经检 查过了然后会继续向前。 $ git merge --verify-signatures signed-branch Commit 13ad65e has a good GPG signature by Scott Chacon (Git signing key)

0 码力 | 670 页 | 13.59 MB | 1 年前

3