git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Default ssh command

From
AHAaron Hall <aaronchallmba@gmail.com>
Date
Jul 7, 2021, 01:35 UTC
Message-ID
<CADrEZfE+LuDnhWkRHPMwHq7aGYcvDeqken8uZzPgHREtf0iqjA@mail.gmail.com>

I was trying to push some binary files (PNGs) over ssh and found some files inexplicably wouldn't successfully push.

I set, in my .gitconfig file:
[core]
        sshCommand = ssh -e none
And it works now for all files (that I can tell).

From a close examination of the output where I noted escape codes showing up, I believe the problem to be ssh escape codes.

`\n~.` for example closes the ssh client.

Therefore I think the default ssh command should be `ssh -e none` instead of `ssh` for the benefit of users who won't recognize the problem, unless `git` is expected to make use of ssh escape codes.

I'm new to the mailing list, sorry if I missed some protocol here.
Thank you so much for working on `git` and making your work
 available to the rest of the world. Cheers!
Next: Junio C Hamano
Message 1 of 5 in “Default ssh command”
  1. Aaron HallJul 7, 2021
  2. Junio C HamanoJul 7, 2021
  3. Aaron HallJul 7, 2021
  4. brian m. carlsonJul 7, 2021
  5. Aaron HallJul 8, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.