Assignment/Exercise Submission Instructions

Start by creating a submit directory off of your home directory in your Unix account (on hobbes). Type the following at the Unix prompt (do not type the percentage symbol):
```
% cd
% mkdir submit
% chmod a+rx submit
```
Next create a directory for this class:
```
% cd
% mkdir cs141
```
Make sure you do not allow outside access to this directory.
Inside this "class" directory is where you will create one subdirectory for each assignment or exercise.
For Exercise 1, the name of the subdirectory is your username followed by the number "1". Example: if your username is beavis your subdirectory will be called beavis1 To create this:
```
% cd
% cd cs141
% mkdir beavis1
```
Note: don't forget to use YOUR username instead of beavis above. We will use the username beavis as an example for the remainder of these instructions.
Next, all your Exercise 1 files need to be in the beavis1 directory. Check that they are:
```
% cd
% cd cs141/beavis1
% ls
```
You should see a list of files in this directory.
When you are ready to submit all the files for Exercise 1, first create a so-called "jar" file:
```
% cd
% cd cs141
% jar cvf beavis1.jar beavis1
```
This will create a file called beavis1.jar in the directory cs141. This "jar" file is really a zip file containing everything that was in the beavis1 directory.
Next, you will encrypt your jar file. Note that the jar file, if acquired by anyone, can be unpacked and so, before making it available, it needs to be encrypted. To encrypt the jar file, follow these steps:
- First, select an 8-letter encryption key and mail that to the TA's (all the TA's for the course, if more than one).
- You will use THIS SAME encryption key for all submissions this semester. So, treat it like a password. Do NOT reveal it to anyone else other than the TA's or the instructor.
- For example, suppose the encryption key is qfgk9816. Now, encrypt the file by typing:
```
     % java -jar ~simha/submit/submit.jar -e qfgk9816 beavis1.jar beavis1.jar.crypt
     
```
  Of course, you should use your crypt key above. Here, the -e option specifies encryption (as opposed to decryption with the -d option).
The above encryption step creates an encrypted file. Copy this file to your submit directory:
```
     % cp beavis1.jar.crypt ~/submit/.
     
```
Make the encrypted file accessible:
```
     % cd
     % chmod a+rx submit
     % cd submit
     % chmod a+r beavis1.jar.crypt
     
```
At this point, the TA will be able to copy over your encrypted file, decrypt it, and un-jar it to test your code. Anyone else can copy over your crypt file, but should not be able to decrypt it.
Important: You should follow the instructions closely - your encrypted jar file will be copied, decrypted, compiled and tested automatically by a new grading tool we've developed. This tool will crash on your assignment if not properly submitted.
Important: Use the same key for future submissions. Do NOT make other directories/files accessible. (Points may be taken off if this occurs).
If specified, submit a printout (hardcopy) of your code before the due date either in my mailbox, in class, or slip it under my door.
In your submissions, please include only your Java source files (not class files, since we will compile). You may include other files only if directed to do so in a specific assignment/exercise.
Naming convention: for Exercise 2, use a subdirectory called beavis2; for Exercise 3, use a subdirectory called beavis3 ... and so on. Assignments are named differently: for Assignment 1, use a subdirectory called beavis_a1, for Assignment 2, use beavis_a2 ... and so on. Thus, for example, the encrypted jar file for Assignment 3 will be called beavis_a3.jar.crypt.