From: Daniel Santos <daniel.dlds@gmail.com>
To: git@vger.kernel.org
Subject: Re: Pulling from a linux box to a Solaris 9 OS
Date: Sun, 22 Oct 2023 10:31:24 +0100 [thread overview]
Message-ID: <CC739286-AEFC-4F97-A86F-7A129159F592@gmail.com> (raw)
In-Reply-To: <20231020062738.GA1642714@coredump.intra.peff.net>
Hello,
I set the environment variable GIT_SSH_VARIANT and it pulled with no issues.
Thanks for the help
Regards
Daniel Santos
> On 20 Oct 2023, at 07:27, Jeff King <peff@peff.net> wrote:
>
> On Fri, Oct 20, 2023 at 12:33:50AM +0000, brian m. carlson wrote:
>
>> By default, if the SSH binary is the default ("ssh"), Git assumes that
>> it's OpenSSH and sends certain options to enable protocol v2, including
>> -o SendEnv.
>>
>> If you don't want that, you can set "ssh.variant" to "simple", in which
>> case Git will send only the username and the host, but not -p port, -4,
>> -6, or -o. If you do need a different port, then you're out of luck,
>> and will either have to install Putty (in which case, the ssh.variant
>> value would need to be "putty") or upgrade OpenSSH. Otherwise, the
>> simple value should work fine.
>
> I think your suggestion is the most straight-forward one, but just in
> case the "out of luck" part is a problem, you should also be able to
> side-step the issue with:
>
> git -c protocol.version=0 fetch ...
>
> That would allow other features (assuming this older ssh version
> supports them!) without triggering the SendEnv option.
>
> -Peff
prev parent reply other threads:[~2023-10-22 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 21:49 Pulling from a linux box to a Solaris 9 OS Daniel Santos
2023-10-20 0:33 ` brian m. carlson
2023-10-20 6:27 ` Jeff King
2023-10-22 9:31 ` Daniel Santos [this message]
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=CC739286-AEFC-4F97-A86F-7A129159F592@gmail.com \
--to=daniel.dlds@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).