We will be using dbs2.cs.umb.edu for its Oracle database (CS634 only), and topcat.cs.umb.edu for its mysql database (for both classes), and as a place to run webapps (for CS637).
For security reasons, you cannot ssh directly from off-site systems to dbs2, because it is running old ssh software. Thus you need to ssh to topcat.cs.umb.edu or users.cs.umb.edu and then ssh to dbs2. For example:
To avoid the second password entry for ssh, you can follow the instructions in the next section. To avoid the first password entry, follow the instructions later in this file depending on your development system's OS.
Note that you will see all the same files in your login directory (or its subdirectories) on users or topcat as you do once you have logged in on dbs2, or any other host of our UNIX/Linux network. This is accomplished through a distributed filesystem (NFS, network file system). Thus to transfer files to dbs2, just transfer them to topcat.cs.umb.edu or users.cs.umb.edu (also named itserver6.cs.umb.edu). We will be using some disk resources that belong to topcat alone: /var/www for Apache's webserver in cs637 and /var/local/cs634 for mysql files in cs634.
Logging into cs.umb.edu hosts from other cs.umb.edu hosts with
ssh, without needing to enter a password (Optional procedure)
Access to cs.umb.edu hosts from offsite Linux or Mac systems: All Linux/Mac systems come with scp and ssh, available once you get a shell window working. For Mac, run the Terminal application. You can just use the same commands as on users.cs.umb.edu in the above instructions. For example, from your shell window on your development Linux/Mac system:
For file transfer from a Linux/Mac system:
scp myfile email@example.com:targetpath (where targetpath is relative to your login directory at cs.umb.edu)
To avoid the first password entry when you ssh or scp to cs.umb.edu, first follow the above instructions to avoid the second password entry, and then use scp to copy the resulting .ssh directory on users.cs.umb.edu to your Linux/Mac home directory. First use "cd" to get to your home directory on your system and then:
"scp -r firstname.lastname@example.org:.ssh ." (that's a dot at the end, for the current directory)
Access to cs.umb.edu hosts from offsite Windows systems using the free Windows tools putty and pscp.
Of course this is not the only way to do file transfers. There are GUI clients that allow drag and drop file transfers after one overall login. Download SSHSecureClient-3.2.9 for an installer for such a GUI client for Windows.
Download the Windows installer at putty home and install it, agreeing to all options. Then add the download directory c:\Program Files\PuTTY to your Path. You can use the path command to see all the directories on your path. Once this is set up, you will have a desktop icon for putty and you can use a new CMD window (to be sure to get the new Path setting) to do a file transfer as follows:
pscp myfile email@example.com:targetpath
Using putty and pscp for access to cs.umb.edu systems from your
Windows PC without entering passwords each time (Optional procedure)
These free and reliable tools work immediately on download, but expect you to enter a password for every use. With a little work, you can set up your environment to avoid the need to enter passwords so often. Note that the install of putty tools above has given you putty, pscp, puttygen, and pageant, used below. This procedure assumes you have already done the above procedure to eliminate second password entries, so you have a .ssh subdirectory of your home directory on the cs.umb.edu network. It also assumes you have all the putty tools on your Path, so you can run them from the command line.
ssh, scp, putty and pscp are client-server applications, with servers running on all the departmental systems, and also any other normally-deployed Mac. A Linux system may or may not have a ssh server installed: on Ubuntu Linux distributions, use "sudo apt-get install ssh openssh-server" to add it.
The system on which putty or pscp is run is the client end, and it connects to the server program on the server end, which must be running all the time to listen for new incoming client connections. Only the client end needs the private key, so for high security server systems (banks, etc.), should not have private key stored there, only the corresponding public key. And a passphrase should be used in this case. Note that by this logic, we should only need to bring the public key back from cs.umb.edu to a Windows client for putty/pscp to use, but this software seems only able to do the server-end protocol, which utilizes the private key. The Linux/Mac ssh/scp can do both ends.
One private key can be used for many client-server interactions with that server. So if you have two systems, say a Mac and a PC, you can use the same private key for transfers from each machine to and from cs.umb.edu.Transfers between your own machines If you have a Mac and a PC, you can use the Mac system at a server end of transfers between your two machines (without having to enter a password if you have set up the .ssh directory on the Mac). In other words, run pscp on the PC, making it the client end, addressing the Mac system by its IP address, obtainable on the Linux/Mac systems with the ifconfig command, for example 192.168.1.114 on a typical home network. Then, on the PC, use for example "pscp file firstname.lastname@example.org:dev" to transfer the file to the Mac system, into the dev subdirectory of the user's login directory.