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

Re: support git+mosh for unreliable connections

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Apr 16, 2015, 09:29 UTC
Message-ID
<552F8106.2060806@drmicha.warpmail.net>
In-Reply-To
<20150415185907.GC21768@tsaunders-iceball.corp.tor1.mozilla.com>
Trevor Saunders venit, vidit, dixit 15.04.2015 20:59:
Show 39 quoted lines
> On Wed, Apr 15, 2015 at 07:46:15PM +0200, Johannes Schindelin wrote:
>> Hi Trevor,
>>
>> On 2015-04-15 17:33, Trevor Saunders wrote:
>>> On Wed, Apr 15, 2015 at 04:41:42PM +0200, Johannes Schindelin wrote:
>>>>
>>>> On 2015-04-15 16:18, Pirate Praveen wrote:
>>>>> On Wednesday 15 April 2015 07:22 PM, Michael J Gruber wrote:
>>>>>> What would that require git to do, beyond taking whatever you tell it
>>>>>> (using GIT_SSH or _GIT_SSH_COMMAND) to use as a drop in replacement for ssh?
>>>>>
>>>>> May be support git+mosh as a protocol, since it is not a drop in
>>>>> replacement. It is redesigned remote shell. The ideas it uses for
>>>>> session resumption needs to be reimplemented. This will need support
>>>>> from git, because it needs server side to be modified. Use SSP to return
>>>>> the the current progress for a particular session (it uses AES session ids).
>>>>
>>>> It will need support from Git alright, but not as much as from mosh, see my other reply: Mosh was not designed for non-interactive use. That support would have to be added before we can go any further.
>>>
>>> is that really relevent? mosh doesn't support things like X forwarding
>>> or port forwarding, but it certainly does support ssh <host> <command>
>>> and then doing IO.
>>
>> Ah, so mosh's README lied to me!
> 
> I wouldn't say it lied, its just not really clear what is "interactive"
> I'd say git's use of ssh is kind of interactive compared to things like
> port forwarding.
> 
>> If `mosh <user>@<host> <command>` works, then a simple `GIT_SSH=mosh` should work out of the box, too. Have you tried it?
> 
> it does work, I just tried mosh $host cat and then typing stuff and
> having it printed back at me.  However it clears the terminal before
> hand and prints a message on exit.  I tried GIT_SSH=mosh git clone and
> it failed, but I haven't really dug into why.  SO I suspect this can be
> made to work with some work on the mosh side, but I'm not sure exactly
> how ssh and mosh are behaving differently here.
> 
> Trev
First thing you see on mosh.mit.edu:
"Mosh is a replacement for SSH."
I guess that needs a footnote...
Michael
Previous: Trevor SaundersNext: Dennis Kaarsemaker
Message 9 of 15 in “support git+mosh for unreliable connections”
  1. Pirate PraveenApr 15, 2015
  2. Dennis KaarsemakerApr 15, 2015
  3. Michael J GruberApr 15, 2015
  4. Pirate PraveenApr 15, 2015
  5. Johannes SchindelinApr 15, 2015
  6. Trevor SaundersApr 15, 2015
  7. Johannes SchindelinApr 15, 2015
  8. Trevor SaundersApr 15, 2015
  9. Michael J GruberApr 16, 2015
  10. Dennis KaarsemakerApr 15, 2015
  11. Andreas KreyApr 22, 2015
  12. Johannes SchindelinApr 15, 2015
  13. Pirate PraveenApr 15, 2015
  14. Ilari LiusvaaraApr 15, 2015
  15. Pirate PraveenApr 20, 2015

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.