You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
What's the plan going forward, to marshall all commands natively over ssh (#93), or to use SSH merely to run a shell command on the host that opens a Node socket, and then connect to that socket from Atom (as occurs today)?
My server's ssh settings have changed, and I can no longer connect with Nuclide. My key is ecdsa-sha2-nistp256, and ssh2-streams doesn't seem to support that.
If the plan is to continue using the 9090 sockets, can we decouple the remote execution of nuclide-start-server from the actual connection? Because of an unusually hardened sshd, I will probably always have to open a shell myself to connect to my server, and then forward the relevant ports over that connection. Since I can do that myself, there shouldn't be a requirement that Nuclide is also responsible for the SSH connection. It's convenient for simple cases, but I should be able to connect to nuclide-server:9090 from Atom independently, so I can still use Nuclide even if my SSH settings aren't supported by ssh2-streams.
What's the plan going forward, to marshall all commands natively over ssh (#93), or to use SSH merely to run a shell command on the host that opens a Node socket, and then connect to that socket from Atom (as occurs today)?
My server's ssh settings have changed, and I can no longer connect with Nuclide. My key is
ecdsa-sha2-nistp256
, and ssh2-streams doesn't seem to support that.If the plan is to continue using the 9090 sockets, can we decouple the remote execution of
nuclide-start-server
from the actual connection? Because of an unusually hardened sshd, I will probably always have to open a shell myself to connect to my server, and then forward the relevant ports over that connection. Since I can do that myself, there shouldn't be a requirement that Nuclide is also responsible for the SSH connection. It's convenient for simple cases, but I should be able to connect to nuclide-server:9090 from Atom independently, so I can still use Nuclide even if my SSH settings aren't supported by ssh2-streams.cc: @ssorallen
The text was updated successfully, but these errors were encountered: