From: Andreas Schwab <schwab@linux-m68k.org>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: "'SZEDER Gábor'" <szeder.dev@gmail.com>,
"'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>,
git@vger.kernel.org
Subject: Re: [BUG] GIT_SSH_COMMAND is not being decomposed
Date: Mon, 15 Apr 2019 23:14:26 +0200 [thread overview]
Message-ID: <87ef63ezt9.fsf@igel.home> (raw)
In-Reply-To: <004d01d4f3c0$3ff358d0$bfda0a70$@nexbridge.com> (Randall S. Becker's message of "Mon, 15 Apr 2019 15:20:07 -0400")
On Apr 15 2019, "Randall S. Becker" <rsbecker@nexbridge.com> wrote:
> on virtually any platform at my disposal (Windows, Ubuntu, MacOS, the
> older NonStop variant), and have that work with no problem. Somewhere
> after get_ssh_command(), the command is being interpreted it its parts
> either as a shell or something else (still trying to find that).
See run-command.c:prepare_shell_cmd, if the command contains shell meta
characters it is passed to sh -c without further quoting.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2019-04-15 21:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 20:27 [BUG] GIT_SSH_COMMAND is not being decomposed Randall S. Becker
2019-04-13 20:39 ` Ævar Arnfjörð Bjarmason
2019-04-13 20:57 ` Randall S. Becker
2019-04-13 21:47 ` SZEDER Gábor
2019-04-14 14:34 ` Randall S. Becker
2019-04-15 19:20 ` Randall S. Becker
2019-04-15 21:14 ` Andreas Schwab [this message]
2019-04-15 22:34 ` Randall S. Becker
2019-04-16 4:24 ` Junio C Hamano
2019-04-15 21:30 ` Johannes Sixt
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=87ef63ezt9.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.com \
--cc=szeder.dev@gmail.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).