ssh signing: clarify trustlevel usage in docs
facca53ac added verification for ssh signatures but incorrectly described the usage of gpg.minTrustLevel. While the verifications trustlevel is stil set to fully or undefined depending on if the key is known or not it has no effect on the verification result. Unknown keys will always fail verification. This commit updates the docs to match this behaviour. Signed-off-by: Fabian Stelzer <fs@gigacodes.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Fabian Stelzer committed
Oct 13, 2021 at 09:51 UTC
9fb391bff9258dd83b7c218fd9bb6ddb6e7b425e
1 file changed
+1
-3
Documentation/config/gpg.txt
+1
-3
@@ -52,9 +52,7 @@ gpg.ssh.allowedSignersFile::
52
SSH has no concept of trust levels like gpg does. To be able to differentiate
53
between valid signatures and trusted signatures the trust level of a signature
54
verification is set to `fully` when the public key is present in the allowedSignersFile.
55
-Therefore to only mark fully trusted keys as verified set gpg.minTrustLevel to `fully`.
56
-Otherwise valid but untrusted signatures will still verify but show no principal
57
-name of the signer.
55
+Otherwise the trust level is `undefined` and git verify-commit/tag will fail.
56
+
57
This file can be set to a location outside of the repository and every developer
58
maintains their own trust store. A central repository server could generate this