SSH: Difference between revisions
(Created page with "'''[https://en.wikipedia.org/wiki/Secure_Shell Secure Shell]''' @ Wikipedia is an encrypted remote access network protocol commonly used to access CSE login servers. See also <code>man ssh</code>.") |
No edit summary |
||
| Line 1: | Line 1: | ||
''' | '''Secure SHell''' (SSH) is both a program and an encrypted remote access network protocol commonly used to access [[CSE]] [[login server]]s. | ||
See also <code>man ssh</code> | It is also the most common transport mechanism used with <code>[[rsync]]</code>. | ||
SSH allows users to access remote computers using a secure, encrypted network connection. Very commonly in CSE, users will access our [[login server]]s using SSH. Once connected via SSH the users can run any command-line program or utility — such as compilers, text editors, debuggers, etc. | |||
More advanced users can take advantage of SSH's X11 forwarding so that they can run a program with a graphical interface on a CSE login server and have the program's window(s) appear on the user's own computer instead. | |||
Absent any other setup when SSH is run to connect to a CSE host this remote host will require the user to authenticate with a password&hellp; which quickly becomes tiresome when you keep having to type in your password every time you connect. | |||
== <code>authorized_keys</code> == | |||
SSH supports a private/public key pair that you can generate using the <code>ssh-keygen</code> program. When the public component of the pair is stored in the user's home directory under <code>.ssh/authorized_keys</code> file at CSE, the user can then use the private key component to authenticate future connections without needing to enter their password each time<ref>In this case the private key component is typically stored in the <code>.ssh</code> subdirectory of their home directory on their home/local/non-CSE Linux computer.</ref>. | |||
== See also == | |||
* [https://en.wikipedia.org/wiki/Secure_Shell Secure SHell] @ Wikipedia | |||
* <code>man ssh</code> | |||
== Footnotes == | |||
<references /> | |||
Revision as of 16:50, 5 September 2023
Secure SHell (SSH) is both a program and an encrypted remote access network protocol commonly used to access CSE login servers.
It is also the most common transport mechanism used with rsync.
SSH allows users to access remote computers using a secure, encrypted network connection. Very commonly in CSE, users will access our login servers using SSH. Once connected via SSH the users can run any command-line program or utility — such as compilers, text editors, debuggers, etc.
More advanced users can take advantage of SSH's X11 forwarding so that they can run a program with a graphical interface on a CSE login server and have the program's window(s) appear on the user's own computer instead.
Absent any other setup when SSH is run to connect to a CSE host this remote host will require the user to authenticate with a password&hellp; which quickly becomes tiresome when you keep having to type in your password every time you connect.
authorized_keys
SSH supports a private/public key pair that you can generate using the ssh-keygen program. When the public component of the pair is stored in the user's home directory under .ssh/authorized_keys file at CSE, the user can then use the private key component to authenticate future connections without needing to enter their password each time[1].
See also
- Secure SHell @ Wikipedia
man ssh
Footnotes
- ↑ In this case the private key component is typically stored in the
.sshsubdirectory of their home directory on their home/local/non-CSE Linux computer.