I never had to specify $MOSH_KEY and lack of UTF-8 is fatal error with verbose message in mosh. On 29.05.2017 21:41, Alistair Crooks wrote: > cvs log tells me I added the MESSAGE file when I imported the package. > > I'm not well-placed to speak to how confusing it is, and I think I > must have added it because I was unsure of how to set it up, and > didn't find details easy to come by. > > If you find the message is confusing, please feel free to delete it. > > Best, > Alistair > > On 29 May 2017 at 10:52, Benny Siegert <bsiegert%gmail.com@localhost> wrote: >> When installing net/mosh, the following message appears: >> >> =========================================================================== >> $NetBSD: MESSAGE,v 220.127.116.11 2012/07/20 03:15:29 agc Exp $ >> =========================================================================== >> >> To invoke the server, you need to use a UTF-8 character set, and >> a hard-coded string of "new" (to make mosh-server use getopt). e.g. >> >> % env LC_CTYPE="en_US.UTF-8" mosh-server new -i 192.168.98.130 >> MOSH CONNECT 60001 2zDOoujUVJ1AW4YFYw36sg >> % >> >> and to connect to that server, the invocation is >> >> % env LC_CTYPE="en_US.UTF-8" MOSH_KEY=2zDOoujUVJ1AW4YFYw36sg \ >> mosh-client 192.168.98.130 60001 >> >> Please note that this package uses UDP, and so packets may be filtered >> in certain environments. >> =========================================================================== >> >> I feel like this message is more confusing than anything else. AIUI, the intended use of mosh is as a drop-in replacement of ssh, i.e. you run „mosh hostname“. This logs in via ssh and sets up the server connection. >> >> How about just removing the message? >> >> —Benny.
Description: OpenPGP digital signature