From: Jerzy Kozera <jerzy.kozera@gmail.com>
To: git@vger.kernel.org
Cc: Jerzy Kozera <jerzy.kozera@gmail.com>
Subject: [PATCH] gpg-interface: Strip CR chars for Windows gpg2
Date: Sat, 11 Nov 2017 16:06:57 +0000 [thread overview]
Message-ID: <20171111160657.11016-1-jerzy.kozera@gmail.com> (raw)
This fixes the issue with newlines reported at
https://github.com/git-for-windows/git/issues/1249
Issues with non-ASCII characters remain for further investigation.
Signed-off-by: Jerzy Kozera <jerzy.kozera@gmail.com>
---
The patch applies cleanly on top of maint as well as master.
gpg-interface.c | 25 ++++++++++++++++---------
1 file changed, 16 insertions(+), 9 deletions(-)
diff --git a/gpg-interface.c b/gpg-interface.c
index 4feacf16e5..a92fb2f3b9 100644
--- a/gpg-interface.c
+++ b/gpg-interface.c
@@ -145,6 +145,18 @@ const char *get_signing_key(void)
return git_committer_info(IDENT_STRICT|IDENT_NO_DATE);
}
+/* Strip CR from the line endings, in case we are on Windows. */
+static void strip_cr(struct strbuf *buffer, size_t bottom) {
+ size_t i, j;
+ for (i = j = bottom; i < buffer->len; i++)
+ if (buffer->buf[i] != '\r') {
+ if (i != j)
+ buffer->buf[j] = buffer->buf[i];
+ j++;
+ }
+ strbuf_setlen(buffer, j);
+}
+
/*
* Create a detached signature for the contents of "buffer" and append
* it after "signature"; "buffer" and "signature" can be the same
@@ -155,7 +167,7 @@ int sign_buffer(struct strbuf *buffer, struct strbuf *signature, const char *sig
{
struct child_process gpg = CHILD_PROCESS_INIT;
int ret;
- size_t i, j, bottom;
+ size_t bottom;
struct strbuf gpg_status = STRBUF_INIT;
argv_array_pushl(&gpg.args,
@@ -180,14 +192,7 @@ int sign_buffer(struct strbuf *buffer, struct strbuf *signature, const char *sig
if (ret)
return error(_("gpg failed to sign the data"));
- /* Strip CR from the line endings, in case we are on Windows. */
- for (i = j = bottom; i < signature->len; i++)
- if (signature->buf[i] != '\r') {
- if (i != j)
- signature->buf[j] = signature->buf[i];
- j++;
- }
- strbuf_setlen(signature, j);
+ strip_cr(signature, bottom);
return 0;
}
@@ -230,6 +235,8 @@ int verify_signed_buffer(const char *payload, size_t payload_size,
sigchain_push(SIGPIPE, SIG_IGN);
ret = pipe_command(&gpg, payload, payload_size,
gpg_status, 0, gpg_output, 0);
+ strip_cr(gpg_status, 0);
+ strip_cr(gpg_output, 0);
sigchain_pop(SIGPIPE);
delete_tempfile(&temp);
--
2.14.2.windows.3
next reply other threads:[~2017-11-11 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 16:06 Jerzy Kozera [this message]
2017-11-12 1:51 ` [PATCH] gpg-interface: Strip CR chars for Windows gpg2 Junio C Hamano
2017-11-12 1:53 ` Junio C Hamano
2017-11-12 5:58 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171111160657.11016-1-jerzy.kozera@gmail.com \
--to=jerzy.kozera@gmail.com \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).