Logging In Through TerminalUsers can also logon into the Prime server from their computers at home or at their dorm by using a Secure Shell (SSH) client. Many programs are available for this purpose. Eg. Tera Term Pro (ver 2.3 for WIN 95/NT users) which users can down load here (or) PuTTY, an SSH Client for any version of windows can be downloaded from this site. Users usually prefer PuTTY over Tera Term because of its easy to use window interface. However both these software programs are very similar in the way they work and in their other features.
Users can transfer files between pc's and the server in several ways. The easiest way is to use winscp which you can get from winscp.org. This program allows you to open a window on your pc and browse the files on the server just like it was a local disk. Drag-and-drop copy between machines is supported, as well as advanced features such as automatically syncing the files on the server to your pc - great for backing up critical directories. Note that you have to log into p1 or p2 or p3 and not prime itself to transfer files.
Users who are using the CNS version of ssh (Oak SSH, or SSH Secure Shell) must set the Authentication method to Keyboard interactive when logging onto one of the prime machines.
Logging On:
Users can type “ p1.cs.ohiou.edu “ at the text box provided for the host name and hit the <return> key. The system then prompts user to enter their username and the appropriate password to logon to Prime. Once they are logged on, users can access their accounts with all their directories and programs as usual. Eg. for using Telnet: The following is a example of a Telnet session.
TELNET [host]
or
TELNET [cr] followed by OPEN [host] at the prompt.The basic command set is simple. Additionally, users also need to know either the machine domain name or the machine Internet address (a series of numbers). While the numbers always work, the names will work depending on the software used.
Logging Off :
At the Prompt, typeExit.
Example:<machine>% exit(or) “ CTRL ” + “ d ”.
This is a very secure way of closing an open connection. Logging off the remote system may return user to their primary operating environment (out of Telnet), or they may be left in Telnet.
If the latter happens, the user has to type "quit”. Because Telnet lacks security features, at OU, the use of SSh or Secure shell is required on most machines.
Secure Shell:
SSh is a program for logging into a remote machine and for executing commands on a remote machine. It is intended to replace rlogin, telnet and rsh, and provide secure encrypted communications between two untrusted hosts over an insecure network. SSh connects and logs into the specified hostname.
NAME: Open SSh SSh client (remote login program)
SYNOPSIS: ssh [-l login_name] hostname | user@hostname [command]
For example, if the user wishes to log-in into Prime server, the user types the following at the prompt,
<machine>% ssh <login_id>@p2.cs.ohiou.edu
The user would be logged-on to the prime server under the username given by 'uname'. It will then prompt for the password. To log-in to the server, the user has to type the correct password.
<machine>% p2
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX.
Please contact your system administrator.
Add correct host key in /home/<login_id>/.ssh/known_hosts to get rid of this message.
Offending key in /home/<login_id>/.ssh/known_hosts:X
RSA host key for <host_machine_name> has changed and you have requested strict checking.
Host key verification failed.
The above example is a ssh login to a server that does not receive correct authentication. When this happens, it may be evidence of an attack, but also may just be the server being reset. In order to remedy this problem, just remove the line number indicated in the known hosts file and login again.