Network Questions

What network storage is available to me?

All CS users have home directory on the department file server to store files. Anything you place in your home directory is backed up nightly, with revisions stored going back six months.

Linux Systems

On department linux systems, your home directory is automatically mounted as $HOME. The full path of your home directory can be found using the finger command on any linux host.

finger testacct
Login: testacct       			Name: Testing Tester
Directory: /home/t/testacct         	Shell: /bin/bash
Never logged in.
No mail.
No Plan.

In this case, testacct's home directory is /home/t/testacct.

Windows Systems

On department Windows systems, your home directory should be mounted as the U:\ drive. If you are manually mounting a drive, use the URI \\files.cs.ksu.edu\<username> where <username> is your eID.

Transient Storage

If you need a large amount of space temporarily, you can request space in the transient volume (send an email to help@cs.ksu.edu). There are no quotas on directories in this volume, but there are also no backups made of files here. Support staff may also ask you to clean files out periodically to make room for others. On department linux systems, your transient directory will be found in /transient/<username>. On department Windows systems, you can mount the share \\files.cs.ksu.edu\transient\<username> to a drive letter of your choosing.

How do I setup CGI on my web page?

Please see the page on Personal Web Pages.

Why don't you have an FTP server?

FTP is a very old protocol. It was designed before security considerations were a major part of protocol design. As such, passwords to the FTP server are sent in plain text---any clever user on the network can snoop your packets and steal your password. This would allow that user to gain access to your account, which is an unacceptable violation of our security.

If you need to access your home directory from a remote location, there are two different methods for doing so. See the documentation in the CS Systems UserGuide for Remote Access or in the FrequentlyAskedQuestions about how to access your home directory from a non-CS computer.

How do I use HTTP authentication?

To setup password authentication for a directory in your personal web space follow these steps from a linux shell (you will want to change passwordProtectedDir to whatever name you want and use your own usernames). <your_home_dir_path> is the full path to your home directory. If you don't know what this is, use the finger command from the command prompt of any linux host ("finger <eid>", where <eid> is your eID).

cd ~/public_html/
mkdir passwordProtectedDir
cd passwordProtectedDir
htpasswd -c .htpasswd user_who_gets_access
htpasswd .htpasswd other_user
cat << EOF > ~/public_html/passwordProtectedDir/.htaccess
AuthType Basic
AuthName "Checking Password"
AuthUserFile <your_home_dir_path>/public_html/passwordProtectedDir/.htpasswd
Require valid-user
EOF

Now create any files you want in the directory and set permissions appropriately.

chmod o+rx ~/public_html/passwordProtectedDir
chmod o+r ~/public_html/passwordProtectedDir/*.*

If you would like your files to only be password protected off-campus, use this command to make your htaccess file.

cat << EOF > ~/public_html/passwordProtectedDir/.htaccess
AuthType Basic
AuthName "Checking Password"
AuthUserFile <your_home_dir_path>/public_html/passwordProtectedDir/.htpasswd
Require valid-user
Order Allow,Deny
# This restricts access without a password to the KSU network
Allow from 12# 130.0.0/16
# This restricts access without a password to the CS network
#Allow from 12# 130.8.0/22
Satisfy any
EOF

Why am I getting 500 Interal Server Error on all my scripts?

We use programs named suexec and suphp to make sure that all of your scripts run as you. This allows your scripts to access files that would normally be private and inaccessible by the web server. However, for security these programs will not allow your scripts to run unless the permissions set on your files and on the directories containing them are safe.

For CGI scripts, you must make sure the following are true:

Your script must be stored in your home directory in the subdirectory named public_html/cgi-bin. You cannot place your scripts anywhere else.
You must make sure that your home directory, the public_html directory, and the cgi-bin directory are not group or other writable:
Finally, you must make sure your scripts are executable, but not group or other writable:
If you have problems, try checking the end of the logs for additional information while pressing reload on your browser:

For PHP scripts, you must make sure the following are true:

Your script must be stored in your home directory under the directory named public_html or a subdirectory of that directory.
You must make sure that your home directory, the public_html directory, and every directory above your PHP script is accessible but not group or other writable:
Finally, you must make sure your scripts are readable, but not group or other writable:
If you have problems, try checking the end of the logs for additional information while pressing reload on your browser:

How do I setup ssh keys?

Linux/MacOS & Powershell

Note: If you can run the command ssh-keygen.exe in powershell without receiving an error you can follow these instructions, just be sure to replace any "~" with "$HOME" and "/" with "\" when you seem them. Otherwise follow the putty instructions below.

Open a terminal and run the command ssh-keygen -t rsa.
You will be asked to specify the keys file path, the default will likely be/home/username/.ssh/id_rsa . If you specify a different path it must be global.
Next you will be asked for a password to encrypt your key with. If you don't want to encrypt your key you can leave the filed blank and press enter, if you use a password it should be different from your users password.
There should now be two new files id_rsa and id_rsa.pubin the folder ~/.ssh/. (This document will assume you used default file paths)
Next you will need to run the command ssh-copy-id -i ~/.ssh/id_rsa.pub username@cslinux.cs.ksu.edu, you will be prompted for your password and after that you should be done. If you have issues with this command you can follow step 5, otherwise you can skip to step 6.
You will need to copy the contents of your public key (the .pub file) from your local machine into the file ~/.ssh/authorized_keys on the server you want to ssh into, this should just be one long string on a single line. You can use scp to copy the file over and append it to the authorized_keys file, or you can copy it to your clipboard and paste it with a text editor.
With your public key copied over as long as you have your private key in the folder ~/.ssh/. Close and reopen your terminal and you should be able to login as normal but without entering your password, or only entering your specified decryption password.
If you gave your key a non default path you will need to tell your SSH client where to find your key by editing or creating the file ~/.ssh/config and adding the line IdentityFile /path/to/private_key. For more information on SSH client configurations check the man page for ssh_config.

Putty

To set up ssh keys on windows hosts first make sure you have both putty and puttygen installed here.

Open puttygen, make sure RSA is selected at the bottom and click generate.
Click Save private key and click yes when it asks if its okay to create a key without a password. Put this file away somewhere (Do not just drop it on your desktop).
Then select everything in the text box labeled "Public key for pasting into OpenSSH authorized_key file" and copy it to a file somewhere near your private key.

You are done working on your windows host for now, you will need to ssh into the machine you want to set up keys on.
Open the file ~/.ssh/authorized_keys (if this file doesn't exist you can make it). The key should just be one very long string on a single line.
Run the commands chmod 700 ~/.ssh/ and chmod 600 ~/.ssh/authorized_keys You are now done setting up the keys and you can log out of this machine. The only thing you need to do from here on is specify which private key to use next time you log on.
Open putty and select auth under the ssh drop down on the left.
Select browse at the bottom of the list and navigate to you the .ppk file you made in step 2
Return to the session tab on the left, enter the address of the machine you want to connect to and click the open button.
You should be prompted for your username but you should not need to type your password and you should be authenticated.