Changes between Version 5 and Version 6 of User Guide/Remote Access/Ssh Tips

Timestamp:

May 19, 2020, 9:23:17 PM (5 years ago)

Author:

msherman

Comment:

—

User Guide/Remote Access/Ssh Tips

@@ -54 +54 @@
 * !StrictHostKeyChecking: disables the warning message. SSH complains when host keys for a dns name change. This is a useful security feature, but is inconvenient within the testbed, where the operating system on a trusted machine changes frequently. Do not set it as a wildcard default for public endpoints, or you will be vulnerable to spoofing or man in the middle attacks.
 * ForwardX11: allows the forwarding of graphical applications running the X11 protocol from a node back to your machine
+
+=== Tips for working on a remote system
+
+==== Handling sessions and disconnections
+
+To avoid losing your place if disconnected, use something like [https://github.com/tmux/tmux/wiki Tmux]. This will allow you to have multiple tabs, or windows, with a single ssh connection. In addition, you'll be able to reconnect to this set-up if your connection drops.
+
+Warning: On the consoles, when your reservation ends, all of your processes will be killed, including tmux sessions.
+
+==== File management
+To move files between your machine and the consoles, the simplest method is something like SCP.
+For a graphical client, one example is !FileZilla, over scp or sftp.
+
+To move files to a node, this is normally a two step process. Local -> Console, Console -> node.
+
+By using a !ProxyJump directive in your local machine's `~/.ssh/config` file, you can do this in "1" step, but this is an advanced method. When accessing the node, your ssh client with automatically proxy the connection via the console.
+
+An example file is:
+{{{
+Host node1.cosmos-lab.org
+User root
+ProxyJump console.cosmos-lab.org
+}}}
+
+
+For development on nodes, we recommend using git, and having both your local machine and the console or node pull from the repo.