2017-12-10 07:53:58 +01:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
|
|
test_description='pull signature verification tests'
|
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
. "$TEST_DIRECTORY/lib-gpg.sh"
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'create repositories with signed commits' '
|
|
|
|
|
echo 1 >a && git add a &&
|
|
|
|
|
test_tick && git commit -m initial &&
|
|
|
|
|
git tag initial &&
|
|
|
|
|
|
|
|
|
|
git clone . signed &&
|
|
|
|
|
(
|
|
|
|
|
cd signed &&
|
|
|
|
|
echo 2 >b && git add b &&
|
|
|
|
|
test_tick && git commit -S -m "signed"
|
|
|
|
|
) &&
|
|
|
|
|
|
|
|
|
|
git clone . unsigned &&
|
|
|
|
|
(
|
|
|
|
|
cd unsigned &&
|
|
|
|
|
echo 3 >c && git add c &&
|
|
|
|
|
test_tick && git commit -m "unsigned"
|
|
|
|
|
) &&
|
|
|
|
|
|
|
|
|
|
git clone . bad &&
|
|
|
|
|
(
|
|
|
|
|
cd bad &&
|
|
|
|
|
echo 4 >d && git add d &&
|
|
|
|
|
test_tick && git commit -S -m "bad" &&
|
|
|
|
|
git cat-file commit HEAD >raw &&
|
tests: make forging GPG signed commits and tags more robust
A couple of test scripts create forged GPG signed commits or tags to
check that such forgery can't fool various git commands' signature
verification. All but one of those test scripts are prone to
occasional failures because the forgery creates a bogus GPG signature,
and git commands error out with an unexpected error message, e.g.
"Commit deadbeef does not have a GPG signature" instead of "... has a
bad GPG signature".
't5573-pull-verify-signatures.sh', 't7510-signed-commit.sh' and
't7612-merge-verify-signatures.sh' create forged signed commits like
this:
git commit -S -m "bad on side" &&
git cat-file commit side-bad >raw &&
sed -e "s/bad/forged bad/" raw >forged &&
git hash-object -w -t commit forged >forged.commit
On rare occasions the given pattern occurs not only in the commit
message but in the GPG signature as well, and after it's replaced in
the signature the resulting signature becomes invalid, GPG will report
CRC error and that it couldn't find any signature, which will then
ultimately cause the test failure.
Since in all three cases the pattern to be replaced during the forgery
is the first word of the commit message's subject line, and since the
GPG signature in the commit object is indented by a space, let's just
anchor those patterns to the beginning of the line to prevent this
issue.
The test script 't7030-verify-tag.sh' creates a forged signed tag
object in a similar way by replacing the pattern "seventh", but the
GPG signature in tag objects is not indented by a space, so the above
solution is not applicable in this case. However, in the tag object
in question the pattern "seventh" occurs not only in the tag message
but in the 'tag' header as well. To create a forged tag object it's
sufficient to replace only one of the two occurences, so modify the
sed script to limit the pattern to the 'tag' header (i.e. a line
beginning with "tag ", which, because of the space character, can
never occur in the base64-encoded GPG signature).
Note that the forgery in 't7004-tag.sh' is not affected by this issue:
while 't7004' does create a forged signed tag kind of the same way,
it replaces "signed-tag" in the tag object, which, because of the '-'
character, can never occur in the base64-encoded GPG signarute.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-06-04 15:39:26 +02:00
|
|
|
sed -e "s/^bad/forged bad/" raw >forged &&
|
2017-12-10 07:53:58 +01:00
|
|
|
git hash-object -w -t commit forged >forged.commit &&
|
|
|
|
|
git checkout $(cat forged.commit)
|
|
|
|
|
) &&
|
|
|
|
|
|
|
|
|
|
git clone . untrusted &&
|
|
|
|
|
(
|
|
|
|
|
cd untrusted &&
|
|
|
|
|
echo 5 >e && git add e &&
|
|
|
|
|
test_tick && git commit -SB7227189 -m "untrusted"
|
|
|
|
|
)
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'pull unsigned commit with --verify-signatures' '
|
2017-12-15 20:42:36 +01:00
|
|
|
test_when_finished "git reset --hard && git checkout initial" &&
|
2017-12-10 07:53:58 +01:00
|
|
|
test_must_fail git pull --ff-only --verify-signatures unsigned 2>pullerror &&
|
|
|
|
|
test_i18ngrep "does not have a GPG signature" pullerror
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'pull commit with bad signature with --verify-signatures' '
|
2017-12-15 20:42:36 +01:00
|
|
|
test_when_finished "git reset --hard && git checkout initial" &&
|
2017-12-10 07:53:58 +01:00
|
|
|
test_must_fail git pull --ff-only --verify-signatures bad 2>pullerror &&
|
|
|
|
|
test_i18ngrep "has a bad GPG signature" pullerror
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'pull commit with untrusted signature with --verify-signatures' '
|
2017-12-15 20:42:36 +01:00
|
|
|
test_when_finished "git reset --hard && git checkout initial" &&
|
2017-12-10 07:53:58 +01:00
|
|
|
test_must_fail git pull --ff-only --verify-signatures untrusted 2>pullerror &&
|
|
|
|
|
test_i18ngrep "has an untrusted GPG signature" pullerror
|
|
|
|
|
'
|
|
|
|
|
|
gpg-interface: add minTrustLevel as a configuration option
Previously, signature verification for merge and pull operations checked
if the key had a trust-level of either TRUST_NEVER or TRUST_UNDEFINED in
verify_merge_signature(). If that was the case, the process die()d.
The other code paths that did signature verification relied entirely on
the return code from check_commit_signature(). And signatures made with
a good key, irregardless of its trust level, was considered valid by
check_commit_signature().
This difference in behavior might induce users to erroneously assume
that the trust level of a key in their keyring is always considered by
Git, even for operations where it is not (e.g. during a verify-commit or
verify-tag).
The way it worked was by gpg-interface.c storing the result from the
key/signature status *and* the lowest-two trust levels in the `result`
member of the signature_check structure (the last of these status lines
that were encountered got written to `result`). These are documented in
GPG under the subsection `General status codes` and `Key related`,
respectively [1].
The GPG documentation says the following on the TRUST_ status codes [1]:
"""
These are several similar status codes:
- TRUST_UNDEFINED <error_token>
- TRUST_NEVER <error_token>
- TRUST_MARGINAL [0 [<validation_model>]]
- TRUST_FULLY [0 [<validation_model>]]
- TRUST_ULTIMATE [0 [<validation_model>]]
For good signatures one of these status lines are emitted to
indicate the validity of the key used to create the signature.
The error token values are currently only emitted by gpgsm.
"""
My interpretation is that the trust level is conceptionally different
from the validity of the key and/or signature. That seems to also have
been the assumption of the old code in check_signature() where a result
of 'G' (as in GOODSIG) and 'U' (as in TRUST_NEVER or TRUST_UNDEFINED)
were both considered a success.
The two cases where a result of 'U' had special meaning were in
verify_merge_signature() (where this caused git to die()) and in
format_commit_one() (where it affected the output of the %G? format
specifier).
I think it makes sense to refactor the processing of TRUST_ status lines
such that users can configure a minimum trust level that is enforced
globally, rather than have individual parts of git (e.g. merge) do it
themselves (except for a grace period with backward compatibility).
I also think it makes sense to not store the trust level in the same
struct member as the key/signature status. While the presence of a
TRUST_ status code does imply that the signature is good (see the first
paragraph in the included snippet above), as far as I can tell, the
order of the status lines from GPG isn't well-defined; thus it would
seem plausible that the trust level could be overwritten with the
key/signature status if they were stored in the same member of the
signature_check structure.
This patch introduces a new configuration option: gpg.minTrustLevel. It
consolidates trust-level verification to gpg-interface.c and adds a new
`trust_level` member to the signature_check structure.
Backward-compatibility is maintained by introducing a special case in
verify_merge_signature() such that if no user-configurable
gpg.minTrustLevel is set, then the old behavior of rejecting
TRUST_UNDEFINED and TRUST_NEVER is enforced. If, on the other hand,
gpg.minTrustLevel is set, then that value overrides the old behavior.
Similarly, the %G? format specifier will continue show 'U' for
signatures made with a key that has a trust level of TRUST_UNDEFINED or
TRUST_NEVER, even though the 'U' character no longer exist in the
`result` member of the signature_check structure. A new format
specifier, %GT, is also introduced for users that want to show all
possible trust levels for a signature.
Another approach would have been to simply drop the trust-level
requirement in verify_merge_signature(). This would also have made the
behavior consistent with other parts of git that perform signature
verification. However, requiring a minimum trust level for signing keys
does seem to have a real-world use-case. For example, the build system
used by the Qubes OS project currently parses the raw output from
verify-tag in order to assert a minimum trust level for keys used to
sign git tags [2].
[1] https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob;f=doc/doc/DETAILS;h=bd00006e933ac56719b1edd2478ecd79273eae72;hb=refs/heads/master
[2] https://github.com/QubesOS/qubes-builder/blob/9674c1991deef45b1a1b1c71fddfab14ba50dccf/scripts/verify-git-tag#L43
Signed-off-by: Hans Jerry Illikainen <hji@dyntopia.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-12-27 14:55:57 +01:00
|
|
|
test_expect_success GPG 'pull commit with untrusted signature with --verify-signatures and minTrustLevel=ultimate' '
|
|
|
|
|
test_when_finished "git reset --hard && git checkout initial" &&
|
|
|
|
|
test_config gpg.minTrustLevel ultimate &&
|
|
|
|
|
test_must_fail git pull --ff-only --verify-signatures untrusted 2>pullerror &&
|
|
|
|
|
test_i18ngrep "has an untrusted GPG signature" pullerror
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'pull commit with untrusted signature with --verify-signatures and minTrustLevel=marginal' '
|
|
|
|
|
test_when_finished "git reset --hard && git checkout initial" &&
|
|
|
|
|
test_config gpg.minTrustLevel marginal &&
|
|
|
|
|
test_must_fail git pull --ff-only --verify-signatures untrusted 2>pullerror &&
|
|
|
|
|
test_i18ngrep "has an untrusted GPG signature" pullerror
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'pull commit with untrusted signature with --verify-signatures and minTrustLevel=undefined' '
|
|
|
|
|
test_when_finished "git reset --hard && git checkout initial" &&
|
|
|
|
|
test_config gpg.minTrustLevel undefined &&
|
|
|
|
|
git pull --ff-only --verify-signatures untrusted >pulloutput &&
|
|
|
|
|
test_i18ngrep "has a good GPG signature" pulloutput
|
|
|
|
|
'
|
|
|
|
|
|
2017-12-10 07:53:58 +01:00
|
|
|
test_expect_success GPG 'pull signed commit with --verify-signatures' '
|
2017-12-15 20:42:36 +01:00
|
|
|
test_when_finished "git reset --hard && git checkout initial" &&
|
2017-12-10 07:53:58 +01:00
|
|
|
git pull --verify-signatures signed >pulloutput &&
|
|
|
|
|
test_i18ngrep "has a good GPG signature" pulloutput
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'pull commit with bad signature without verification' '
|
2017-12-15 20:42:36 +01:00
|
|
|
test_when_finished "git reset --hard && git checkout initial" &&
|
2017-12-10 07:53:58 +01:00
|
|
|
git pull --ff-only bad 2>pullerror
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'pull commit with bad signature with --no-verify-signatures' '
|
2017-12-15 20:42:36 +01:00
|
|
|
test_when_finished "git reset --hard && git checkout initial" &&
|
2017-12-10 07:53:58 +01:00
|
|
|
test_config merge.verifySignatures true &&
|
|
|
|
|
test_config pull.verifySignatures true &&
|
|
|
|
|
git pull --ff-only --no-verify-signatures bad 2>pullerror
|
|
|
|
|
'
|
|
|
|
|
|
2018-11-06 08:52:13 +01:00
|
|
|
test_expect_success GPG 'pull unsigned commit into unborn branch' '
|
gpg-interface: add minTrustLevel as a configuration option
Previously, signature verification for merge and pull operations checked
if the key had a trust-level of either TRUST_NEVER or TRUST_UNDEFINED in
verify_merge_signature(). If that was the case, the process die()d.
The other code paths that did signature verification relied entirely on
the return code from check_commit_signature(). And signatures made with
a good key, irregardless of its trust level, was considered valid by
check_commit_signature().
This difference in behavior might induce users to erroneously assume
that the trust level of a key in their keyring is always considered by
Git, even for operations where it is not (e.g. during a verify-commit or
verify-tag).
The way it worked was by gpg-interface.c storing the result from the
key/signature status *and* the lowest-two trust levels in the `result`
member of the signature_check structure (the last of these status lines
that were encountered got written to `result`). These are documented in
GPG under the subsection `General status codes` and `Key related`,
respectively [1].
The GPG documentation says the following on the TRUST_ status codes [1]:
"""
These are several similar status codes:
- TRUST_UNDEFINED <error_token>
- TRUST_NEVER <error_token>
- TRUST_MARGINAL [0 [<validation_model>]]
- TRUST_FULLY [0 [<validation_model>]]
- TRUST_ULTIMATE [0 [<validation_model>]]
For good signatures one of these status lines are emitted to
indicate the validity of the key used to create the signature.
The error token values are currently only emitted by gpgsm.
"""
My interpretation is that the trust level is conceptionally different
from the validity of the key and/or signature. That seems to also have
been the assumption of the old code in check_signature() where a result
of 'G' (as in GOODSIG) and 'U' (as in TRUST_NEVER or TRUST_UNDEFINED)
were both considered a success.
The two cases where a result of 'U' had special meaning were in
verify_merge_signature() (where this caused git to die()) and in
format_commit_one() (where it affected the output of the %G? format
specifier).
I think it makes sense to refactor the processing of TRUST_ status lines
such that users can configure a minimum trust level that is enforced
globally, rather than have individual parts of git (e.g. merge) do it
themselves (except for a grace period with backward compatibility).
I also think it makes sense to not store the trust level in the same
struct member as the key/signature status. While the presence of a
TRUST_ status code does imply that the signature is good (see the first
paragraph in the included snippet above), as far as I can tell, the
order of the status lines from GPG isn't well-defined; thus it would
seem plausible that the trust level could be overwritten with the
key/signature status if they were stored in the same member of the
signature_check structure.
This patch introduces a new configuration option: gpg.minTrustLevel. It
consolidates trust-level verification to gpg-interface.c and adds a new
`trust_level` member to the signature_check structure.
Backward-compatibility is maintained by introducing a special case in
verify_merge_signature() such that if no user-configurable
gpg.minTrustLevel is set, then the old behavior of rejecting
TRUST_UNDEFINED and TRUST_NEVER is enforced. If, on the other hand,
gpg.minTrustLevel is set, then that value overrides the old behavior.
Similarly, the %G? format specifier will continue show 'U' for
signatures made with a key that has a trust level of TRUST_UNDEFINED or
TRUST_NEVER, even though the 'U' character no longer exist in the
`result` member of the signature_check structure. A new format
specifier, %GT, is also introduced for users that want to show all
possible trust levels for a signature.
Another approach would have been to simply drop the trust-level
requirement in verify_merge_signature(). This would also have made the
behavior consistent with other parts of git that perform signature
verification. However, requiring a minimum trust level for signing keys
does seem to have a real-world use-case. For example, the build system
used by the Qubes OS project currently parses the raw output from
verify-tag in order to assert a minimum trust level for keys used to
sign git tags [2].
[1] https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob;f=doc/doc/DETAILS;h=bd00006e933ac56719b1edd2478ecd79273eae72;hb=refs/heads/master
[2] https://github.com/QubesOS/qubes-builder/blob/9674c1991deef45b1a1b1c71fddfab14ba50dccf/scripts/verify-git-tag#L43
Signed-off-by: Hans Jerry Illikainen <hji@dyntopia.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-12-27 14:55:57 +01:00
|
|
|
test_when_finished "rm -rf empty-repo" &&
|
2018-11-06 08:52:13 +01:00
|
|
|
git init empty-repo &&
|
|
|
|
|
test_must_fail \
|
|
|
|
|
git -C empty-repo pull --verify-signatures .. 2>pullerror &&
|
|
|
|
|
test_i18ngrep "does not have a GPG signature" pullerror
|
|
|
|
|
'
|
|
|
|
|
|
gpg-interface: add minTrustLevel as a configuration option
Previously, signature verification for merge and pull operations checked
if the key had a trust-level of either TRUST_NEVER or TRUST_UNDEFINED in
verify_merge_signature(). If that was the case, the process die()d.
The other code paths that did signature verification relied entirely on
the return code from check_commit_signature(). And signatures made with
a good key, irregardless of its trust level, was considered valid by
check_commit_signature().
This difference in behavior might induce users to erroneously assume
that the trust level of a key in their keyring is always considered by
Git, even for operations where it is not (e.g. during a verify-commit or
verify-tag).
The way it worked was by gpg-interface.c storing the result from the
key/signature status *and* the lowest-two trust levels in the `result`
member of the signature_check structure (the last of these status lines
that were encountered got written to `result`). These are documented in
GPG under the subsection `General status codes` and `Key related`,
respectively [1].
The GPG documentation says the following on the TRUST_ status codes [1]:
"""
These are several similar status codes:
- TRUST_UNDEFINED <error_token>
- TRUST_NEVER <error_token>
- TRUST_MARGINAL [0 [<validation_model>]]
- TRUST_FULLY [0 [<validation_model>]]
- TRUST_ULTIMATE [0 [<validation_model>]]
For good signatures one of these status lines are emitted to
indicate the validity of the key used to create the signature.
The error token values are currently only emitted by gpgsm.
"""
My interpretation is that the trust level is conceptionally different
from the validity of the key and/or signature. That seems to also have
been the assumption of the old code in check_signature() where a result
of 'G' (as in GOODSIG) and 'U' (as in TRUST_NEVER or TRUST_UNDEFINED)
were both considered a success.
The two cases where a result of 'U' had special meaning were in
verify_merge_signature() (where this caused git to die()) and in
format_commit_one() (where it affected the output of the %G? format
specifier).
I think it makes sense to refactor the processing of TRUST_ status lines
such that users can configure a minimum trust level that is enforced
globally, rather than have individual parts of git (e.g. merge) do it
themselves (except for a grace period with backward compatibility).
I also think it makes sense to not store the trust level in the same
struct member as the key/signature status. While the presence of a
TRUST_ status code does imply that the signature is good (see the first
paragraph in the included snippet above), as far as I can tell, the
order of the status lines from GPG isn't well-defined; thus it would
seem plausible that the trust level could be overwritten with the
key/signature status if they were stored in the same member of the
signature_check structure.
This patch introduces a new configuration option: gpg.minTrustLevel. It
consolidates trust-level verification to gpg-interface.c and adds a new
`trust_level` member to the signature_check structure.
Backward-compatibility is maintained by introducing a special case in
verify_merge_signature() such that if no user-configurable
gpg.minTrustLevel is set, then the old behavior of rejecting
TRUST_UNDEFINED and TRUST_NEVER is enforced. If, on the other hand,
gpg.minTrustLevel is set, then that value overrides the old behavior.
Similarly, the %G? format specifier will continue show 'U' for
signatures made with a key that has a trust level of TRUST_UNDEFINED or
TRUST_NEVER, even though the 'U' character no longer exist in the
`result` member of the signature_check structure. A new format
specifier, %GT, is also introduced for users that want to show all
possible trust levels for a signature.
Another approach would have been to simply drop the trust-level
requirement in verify_merge_signature(). This would also have made the
behavior consistent with other parts of git that perform signature
verification. However, requiring a minimum trust level for signing keys
does seem to have a real-world use-case. For example, the build system
used by the Qubes OS project currently parses the raw output from
verify-tag in order to assert a minimum trust level for keys used to
sign git tags [2].
[1] https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob;f=doc/doc/DETAILS;h=bd00006e933ac56719b1edd2478ecd79273eae72;hb=refs/heads/master
[2] https://github.com/QubesOS/qubes-builder/blob/9674c1991deef45b1a1b1c71fddfab14ba50dccf/scripts/verify-git-tag#L43
Signed-off-by: Hans Jerry Illikainen <hji@dyntopia.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-12-27 14:55:57 +01:00
|
|
|
test_expect_success GPG 'pull commit into unborn branch with bad signature and --verify-signatures' '
|
|
|
|
|
test_when_finished "rm -rf empty-repo" &&
|
|
|
|
|
git init empty-repo &&
|
|
|
|
|
test_must_fail \
|
|
|
|
|
git -C empty-repo pull --ff-only --verify-signatures ../bad 2>pullerror &&
|
|
|
|
|
test_i18ngrep "has a bad GPG signature" pullerror
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'pull commit into unborn branch with untrusted signature and --verify-signatures' '
|
|
|
|
|
test_when_finished "rm -rf empty-repo" &&
|
|
|
|
|
git init empty-repo &&
|
|
|
|
|
test_must_fail \
|
|
|
|
|
git -C empty-repo pull --ff-only --verify-signatures ../untrusted 2>pullerror &&
|
|
|
|
|
test_i18ngrep "has an untrusted GPG signature" pullerror
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'pull commit into unborn branch with untrusted signature and --verify-signatures and minTrustLevel=ultimate' '
|
|
|
|
|
test_when_finished "rm -rf empty-repo" &&
|
|
|
|
|
git init empty-repo &&
|
|
|
|
|
test_config_global gpg.minTrustLevel ultimate &&
|
|
|
|
|
test_must_fail \
|
|
|
|
|
git -C empty-repo pull --ff-only --verify-signatures ../untrusted 2>pullerror &&
|
|
|
|
|
test_i18ngrep "has an untrusted GPG signature" pullerror
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'pull commit into unborn branch with untrusted signature and --verify-signatures and minTrustLevel=marginal' '
|
|
|
|
|
test_when_finished "rm -rf empty-repo" &&
|
|
|
|
|
git init empty-repo &&
|
|
|
|
|
test_config_global gpg.minTrustLevel marginal &&
|
|
|
|
|
test_must_fail \
|
|
|
|
|
git -C empty-repo pull --ff-only --verify-signatures ../untrusted 2>pullerror &&
|
|
|
|
|
test_i18ngrep "has an untrusted GPG signature" pullerror
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success GPG 'pull commit into unborn branch with untrusted signature and --verify-signatures and minTrustLevel=undefined' '
|
|
|
|
|
test_when_finished "rm -rf empty-repo" &&
|
|
|
|
|
git init empty-repo &&
|
|
|
|
|
test_config_global gpg.minTrustLevel undefined &&
|
|
|
|
|
git -C empty-repo pull --ff-only --verify-signatures ../untrusted >pulloutput &&
|
|
|
|
|
test_i18ngrep "has a good GPG signature" pulloutput
|
|
|
|
|
'
|
|
|
|
|
|
2017-12-10 07:53:58 +01:00
|
|
|
test_done
|