I'm now unsubscribing from this thread because I'm fed up of spam updates for the last two years. Instead of whineing, write some damn code. There is no need to constantly spam the bug with "+1" or offering to test it. Others, it is known there is demand for a Windows mosh client, but there is nobody with sufficient knowledge to step up and finish this work. The code there is written by so unfortunately I cannot shed further light on how it's works or it's style. I wrote a pull request for this, mobile-shell/moshweb#36. It has matured greatly in the last couple of years to the point that I wouldn't bother using You may wish to edit the original bug posting to mention the Chrome app version, and maybe amend the website to indicate that the Chrome app is the easiest way to run it on Windows. I suspect there may be an issue with some compiler flags, but it is something I need to have more of a look If you want to use mosh on Windows today, easily, I would strongly encourage you to look at mosh-chrome. Mosh.exe!_tmainCRTStartup() Line 547 + 0x2c bytes C Mosh.exe!wWinMain(HINSTANCE_ * hInstance, HINSTANCE_ * hPrevInstance, wchar_t * lpCmdLine, int nCmdShow) Line 129 C++ Mosh.exe!STMClient::main_init() Line 145 + 0x52 bytes C++ Mosh.exe!Network::Transport::Transport(Network::UserStream & initial_state, Terminal::Complete & initial_remote, const char * key_str, const char * ip, int port) Line 66 + 0x59 bytes C++ Mosh.exe!Network::Connection::Connection(const char * key_str, const char * ip, int port) Line 343 + 0xd0 bytes C++ Mosh.exe!Crypto::Session::Session(Crypto::Base64Key s_key) Line 191 + 0x1b bytes C++ ![]() Mosh.exe!ae_init(_ae_ctx * ctx, const void * key, int key_len, int nonce_len, int tag_len) Line 672 + 0x20 bytes C++
0 Comments
Leave a Reply. |