From: "Michał Górny" <mgorny@gentoo.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4] gpg-interface.c: detect and reject multiple signatures on commits
Date: Mon, 22 Oct 2018 08:04:48 +0000 [thread overview]
Message-ID: <7C705597-7AA9-4C4E-904B-CE8C4F01AD24@gentoo.org> (raw)
In-Reply-To: <xmqqin1wyxvz.fsf@gitster-ct.c.googlers.com>
Dnia October 20, 2018 11:57:36 PM UTC, Junio C Hamano <gitster@pobox.com> napisał(a):
>Michał Górny <mgorny@gentoo.org> writes:
>
>> GnuPG supports creating signatures consisting of multiple signature
>> packets. If such a signature is verified, it outputs all the status
>> messages for each signature separately. However, git currently does
>not
>> account for such scenario and gets terribly confused over getting
>> multiple *SIG statuses.
>>
>> For example, if a malicious party alters a signed commit and appends
>> a new untrusted signature, git is going to ignore the original bad
>> signature and report untrusted commit instead. However, %GK and %GS
>> format strings may still expand to the data corresponding
>> to the original signature, potentially tricking the scripts into
>> trusting the malicious commit.
>>
>> Given that the use of multiple signatures is quite rare, git does not
>> support creating them without jumping through a few hoops, and
>finally
>> supporting them properly would require extensive API improvement, it
>> seems reasonable to just reject them at the moment.
>>
>> Signed-off-by: Michał Górny <mgorny@gentoo.org>
>> ---
>> gpg-interface.c | 90
>+++++++++++++++++++++++++++-------------
>> t/t7510-signed-commit.sh | 26 ++++++++++++
>> 2 files changed, 87 insertions(+), 29 deletions(-)
>>
>> Changes in v4:
>> * switched to using skip_prefix(),
>> * renamed the variable to seen_exclusive_status,
>> * made the loop terminate early on first duplicate status seen.
>
>Thanks for sticking to the topic and polishing it further. Looks
>very good.
>
>Will replace.
>
>> + int seen_exclusive_status = 0;
>> +
>> + /* Iterate over all lines */
>> + for (line = buf; *line; line = strchrnul(line+1, '\n')) {
>> + while (*line == '\n')
>> + line++;
>> + /* Skip lines that don't start with GNUPG status */
>> + if (!skip_prefix(line, "[GNUPG:] ", &line))
>> + continue;
>> +
>> + /* Iterate over all search strings */
>> + for (i = 0; i < ARRAY_SIZE(sigcheck_gpg_status); i++) {
>> + if (skip_prefix(line, sigcheck_gpg_status[i].check, &line)) {
>> + if (sigcheck_gpg_status[i].flags & GPG_STATUS_EXCLUSIVE) {
>> + if (++seen_exclusive_status > 1)
>> + goto found_duplicate_status;
>
>Very minor point but by not using pre-increment, i.e.
>
> if (seen_exclusive_status++)
> goto found_duplicate_status;
>
>you can use the expression as a "have we already seen?" boolean,
>whic may probably be more idiomatic.
>
>The patch is good in the way written as-is, and this is so minor
>that it is not worth rerolling to only update this part.
Please don't merge it yet. I gave it some more thought and I think the loop refactoring may cause TRUST_* to override BADSIG (i.e. upgrade from 'bad' to 'untrusted'). I'm going to verify this when I get home.
>
>Thanks.
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2018-10-22 8:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 19:30 [PATCH v4] gpg-interface.c: detect and reject multiple signatures on commits Michał Górny
2018-10-20 23:57 ` Junio C Hamano
2018-10-21 7:10 ` Michał Górny
2018-10-22 0:58 ` Junio C Hamano
2018-10-22 8:04 ` Michał Górny [this message]
2018-10-22 15:25 ` Michał Górny
2018-11-03 15:17 ` Duy Nguyen
2018-11-03 15:32 ` Michał Górny
2018-11-03 15:36 ` Duy Nguyen
2018-11-03 15:58 ` Michał Górny
2018-11-03 15:42 ` Duy Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7C705597-7AA9-4C4E-904B-CE8C4F01AD24@gentoo.org \
--to=mgorny@gentoo.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).