From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_LOW, SPF_HELO_PASS,SPF_PASS,URIBL_SBL,URIBL_SBL_A shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id F26531F5AE for ; Sat, 5 Jun 2021 21:57:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230036AbhFEV6s (ORCPT ); Sat, 5 Jun 2021 17:58:48 -0400 Received: from elephants.elehost.com ([216.66.27.132]:26915 "EHLO elephants.elehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230025AbhFEV6s (ORCPT ); Sat, 5 Jun 2021 17:58:48 -0400 X-Virus-Scanned: amavisd-new at elehost.com Received: from gnash (cpe00fc8d49d843-cm00fc8d49d840.cpe.net.cable.rogers.com [173.33.197.34]) (authenticated bits=0) by elephants.elehost.com (8.15.2/8.15.2) with ESMTPSA id 155LutPj075495 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 5 Jun 2021 17:56:56 -0400 (EDT) (envelope-from rsbecker@nexbridge.com) From: "Randall S. Becker" To: "'Junio C Hamano'" Cc: "'Git Mailing List'" References: <011f01d73dd0$ecf91e00$c6eb5a00$@nexbridge.com> <012601d73ddf$3d0cf660$b726e320$@nexbridge.com> <012901d73de6$c25a4ff0$470eefd0$@nexbridge.com> <01dd01d745b0$875c6920$96153b60$@nexbridge.com> <00f101d75978$0074c840$015e58c0$@nexbridge.com> In-Reply-To: Subject: RE: [Patch 1/3] connect.c: add nonstopssh variant to the sshVariant set. Date: Sat, 5 Jun 2021 17:56:49 -0400 Message-ID: <011b01d75a55$b315a860$1940f920$@nexbridge.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQIWGYGttp5Jdx88vf9L/5ZtrxnlMwG55eaXAXoXgPoC7mL63QI2zlGUAkuPwtwCEzMldQHDJRNoqhL0OYCAAamuEA== Content-Language: en-ca Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On June 4, 2021 4:35 PM, I wrote: >To: 'Junio C Hamano' >Cc: 'Git Mailing List' >Subject: RE: [Patch 1/3] connect.c: add nonstopssh variant to the sshVariant set. > >On June 4, 2021 3:52 PM, Junio C Hamano wrote: >>"Randall S. Becker" writes: >>> The primary >>> problem is supplying -S $ZSSH0 on the command line causes $ZSSH0 to >>> be resolved as a shell variable. It is not. >> >>I think we've heard that one before, and the whole thing sounds like >>you are saying that a command line >> >> $ cmd $ZSSH0 >> >>expects ZSSH0 to be a variable and tries to interpolate its value >>before passing it to "cmd" while you want "cmd" to see a literal string that begins with a dollar sign. >> >>And the standard solution to that problem obviously is to tell the >>shell that the dollar-sign is not a reference to a variable by quoting, by using any variant of e.g. >> >> $ cmd \$ZSSH0 >> $ cmd '$ZSSH0' >> $ cmd "\$ZSSH0" > >I'm going to have to retest this, but, when I last tried this, admittedly around git 2.0, what happened was that one level of escaping the $ >worked for ls-remote, but we needed two levels for upload-pack which seemed to have two shells processing the command. I might be >wrong about the specifics (been 4 years), but there was an inconsistency with the number of required escapes. The single quote did not >work for upload-pack at the time. It is entirely possible that the second level indirection happened because the execution of the sshoss >command itself cross over a platform boundary between the POSIX and non-POSIX file systems (it lives in the non-POSIX side). > >>As far as I can tell, the code in connect.c that spawns ssh via >>GIT_SSH_COMMAND uses the pretty vanilla run_command() interface, and that ought to be capable of producing such a command line, >so I am lost as to where the need to have special case comes from. > >>"cmd" here may be "ssh" but run_command() should not care what exact >>command is being invoked. I am puzzled why a simple quoting like the >>following cannot be adjusted for this particular case, for >>example: >> >> $ cat >>.git/config <<\EOF >> [alias] >> cmdtest0 = "!echo ..\\$ZSSH0.." >> cmdtest1 = "!echo ..$ZSSH0.." >> EOF >> $ ZSSH0=foo git cmdtest0 >> ..$ZSSH0.. >> $ ZSSH0=foo git cmdtest1 >> ..foo.. > >The multi-level resolution that I experienced is not covered in this situation. Still going to investigate this. I'm working on a different >approach to extend my wrapper script to parse out the port, to supply to sshoss, which is not complaint with the standard ssh. If I have to >stick with that script, there's no point going further on this variant. Without a variant (when simple is used), obviously ports cannot be specified. When using the following URL: git clone ssh://git@bitbucket.org:22/myproj/repo.git repo The arguments appended using the auto-detected ssh variant that end up being passed to the GIT_SSH_COMMAND command string are: -o SendEnv=GIT_PROTOCOL -p 22 git@bitbucket.org git-upload-pack '/myproj/repo.git' which is part of the way there, but the -o SendEnv=GIT_PROTOCOL is OpenSSH specific. There is no such argument for the SSHOSS program. This becomes somewhat problematic. Of course, a sufficiently smart wrapper can detect this and strip off the -o SendEnv, which I have working. This just does not seem like a general solution, leading me back down the nonstopssh variant path. Sigh. Randall