You will authenticate yourself using your Cornell NedId and Kerberos password. If you can run SideCar, please do so (on Windows, Start -> Run -> sidecar -> Ok), it will be the most convenient. If you cannot (for example, you are behind a strict firewall or IPMasquerading), you can use CIT's web-based authentication. This will happen automatically if SideCar authentication fails.
You may upload your file(s) at any time up until the deadline. You will have the opportunity to overwrite existing files with new ones up until that time, so don't hesitate to submit early. Everything is logged, so don't worry if your evil roommate ties you up and overwrites your code with the lyrics to the Barney Song. (Note that this means you should definitely not keep submitting your file every single time you change a single line; this will fill up the disk. And since everything is very carefully logged...)
For a given problem set, you may be permitted or required to submit multiple files. (Perhaps your code is broken down into separate files, or maybe we want to see a screen capture.) The submission page lists the files we allow you to submit with a brief description. If you have uploaded anything already, it shows the size and submission date of the most recent version.
You must select which file you are uploading on the CMS page, then locate the file on your disk, and submit the form. The local name of the file you are submitting does not matter, CMS will rename it appropriately during submission. Results will be displayed immediately, showing you your current uploads or giving an error message.
(The next two paragraphs are slightly less important.)
The submission site requires SSL-based authentication. Your NetID will be taken from the authorization information. Note that your browser will complain about the "certificate" being used. SSL has two purposes, identity verification and encryption. We are using it mostly to provide encryption; for proper verification our "certificate" would have to be digitally signed by third parties (for a hefty fee). Therefore, we signed it ourselves, which causes the web browser to notify you that something may be up. If you'd like to manually verify the certificate, our fingerprint is 9D:04:05:18:C1:88:BC:C9:36:A9:64:E6:11:67:DF:B4.
In Netscape, the warning about the certificate will allow you to accept it either temporarily or permanently (until it expires); feel free to accept it permanently so that you don't have to deal with it every time. In Internet Explorer, it looks like you have to use some sort of certificate install wizard to get it to be saved permanently; take a look around and ask in the newsgroup if you can't figure it out.