threads / discuss / 60404

Pulling from a linux box to a Solaris 9 OS

Subject: Pulling from a linux box to a Solaris 9 OS

## tl;dr

4 messages between Oct 19, 2023 and Oct 22, 2023.

replies: 3people: 3as markdown or json

Daniel Santos· Oct 19, 2023, 21:49 UTC · lore

Hello,

I have a bare repo on a linux box. I can push and pull from a modern macOS X. But I also have a Solaris 9 box with a checkout of that same repo. when I try to pull I get the messages:

bash-2.05$ git pull command-line: line 0: Bad configuration option: SendEnv fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

The cause maybe the ‘old-ness’ of solaris software. Is there any way to get around this ?

Thanks, Regards Daniel Santos

brian m. carlson· Oct 20, 2023, 00:33 UTC · re: Daniel Santos · lore

Re: Pulling from a linux box to a Solaris 9 OS

On 2023-10-19 at 21:49:53, Daniel Santos wrote:

Show 14 quoted lines

> Hello,
> 
> I have a bare repo on a linux box. I can push and pull from a modern macOS X.
> But I also have a Solaris 9 box with a checkout of that same repo. when I try to pull I get the messages:
> 
> bash-2.05$ git pull
> command-line: line 0: Bad configuration option: SendEnv
> fatal: Could not read from remote repository.
> 
> Please make sure you have the correct access rights
> and the repository exists.
> 
> The cause maybe the ‘old-ness’ of solaris software.
> Is there any way to get around this ?

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.

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

Jeff King· Oct 20, 2023, 06:27 UTC · re: brian m. carlson · lore

Re: Pulling from a linux box to a Solaris 9 OS

On Fri, Oct 20, 2023 at 12:33:50AM +0000, brian m. carlson wrote:

Show 10 quoted lines

> 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

Daniel Santos· Oct 22, 2023, 09:31 UTC · re: Jeff King · lore

Re: Pulling from a linux box to a Solaris 9 OS

Hello,

I set the environment variable GIT_SSH_VARIANT and it pulled with no issues. Thanks for the help

Regards Daniel Santos

Show 25 quoted lines

> 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