417 Announcements
Breaking news about the course
- May 10
- I put exams 1-3 from this semester and exam 3 from last semester onto the old exams page.
- May 7
- I've updated the following lecture slides:
- May 7
- If you're planning to take the final, I posted information about the forthcoming final exam.
- April 25
-
I've updated the firewalls lecture slides to remove two extra slides at the start and to fix a typo in the title. No need to re-download unless you want a clean copy.
I also added more material to the pre-exam study guide. Additions include discussions of PAP and CHAP, smart cards, security, signed software, sandboxes. I've also elaborated a bit aboutapplication proxies, HPC clustering, and added system area networks and a mention of RAID 0.
- April 25
-
The following lecture slides have been updated to reflect those covered in class.
I broke some of them up into multiple sets if a lecture covered multiple topics.
Please be sure to go through the security slides carefully since I didn't project
them in class. Make sure you understand PAP and CHAP since I didn't cover them
by name.
- Authentication
- Smart Cards
- Biometrics & CAPTCHA
- Stegranography
- System Security
- Firewalls
- VPNs
- Virtualization
- Clusters
- April 24
- The fault tolerance section was accidentally repeated in the study guide. You can download a clean copy.
- April 23
- The third exam will take place this coming Monday, April 28. Information on what you should know for the exam is posted here. I put together a study guide for the exam.
- April 17
- Assignment 6 is posted. If you grabbed it before this announcement, download it again since I removed one question and added another.
- April 14
- I've updated assignment 2 grades. Somee of you will see increased grades due to the extra credit work.
- April 13
- I will be flying back to New Jersey on Monday afternoon. While the weather is supposed to be good and I don't anticipate delays, please check your email before class. If there is any delay, I'll post a notice advising of a delayed start of class. Class is unlikely to be canceled.
- April 12
- I posted an FAQ for assignment 5. Please check it periodically. I also simplified step 3 in the Implementation Advice section of the assignment a bit.
- April 7
- It looks like some of you are just starting assignment 4 last night or today. Please check the FAQ before mailing me if you have any questions.
- March 25
- The second exam will take place this coming Monday, March 31. Information on what you should know for the exam is posted here. I put together a study guide (pdf version) for the exam. I'll post a notice if I modify/embellish these.
- March 24
- Assignment 5 is posted. This is a simple Java RMI assignment.
- March 24
- I posted solutions to Assignment 3.
- March 14
- Assignment 1 has a maximum grade of 26. Other written assignments will have different maximum grades. This is just done for the convenience of grading and I normalize the grades in my roster. If you feel better seeing your grade on a 100-point, just compute 100*your_grade/26.
- March 14
- Assignment 4 is posted. This is an RPC programming assignment and it's due on April 7. Please realize that I will post another programming assignment before then and we have an exam on March 31. Budget your time accordingly.
- March 12
- If you cannot submit your assingment electronically, then you can either put it in Saman's mailbox or leave it under the door of his office (Hill 203). If you submit a paper copy, please send him email informing him that you have done so and where you put it.
- March 12
- Correction about Lamport timestamps: An observant student points out that there's an error in my notes. The system clock is set to (message timestamp + 1) if the receiver's clock ≤ message timestamp, not just if the receiver's clock < message timestamp. You never want two causally related events to have the same Lamport timestamp.
- March 12
- Please submit your assignment on-line via handin. The project name is Assignment 3. Please do not submit Microsoft Word or Latex files. Plain text files are best. Otherwise, pdf files are acceptable as well. You can download this template file if you want a formatting guide. You may submit your assignment by 9:00 pm tonight.
- March 12
- Tonight's recitation is canceled.
- March 5
- Item f in question 2 in assignment 3 should state "to event d" instead of "from event d."
- March 5
- I fixed a mistake in assignment 3. If you already downloaded it, please re-download.
- March 5
- The third assignment is posted. This is a written assignment about clocks and multicast. The assignment is due in recitation on March 12.
- March 5
- If you were unable to complete assignment 2 by the deadline, you may email the tar file to me before 5:00 pm on Friday, March 7 for 50% credit. I will not do this for future assignments.
- February 27
- I posted an FAQ for assignment 2. So far it's only one question/answer pair.
- February 22
- I've added last semester's exam to the list of old exams.
- February 20
- I've moved assignment 2's due date to Monday, March 3 at 5pm. If you want to procrastinate starting it until that weekend, do so at your own risk.
- February 19
- The first exam will take place this coming Monday, February 25. Information on what you should know for the exam is posted here. Be sure to read the study guide (pdf version).
- February 16
- Assignment 2 is posted. This is a simple sockets program to get and put files. I'll be posting some advice and further clarifications over the next few days. Please send me mail if anything is unclear.
- February 5
- The first assignment is posted. This is a written assignment comprising 14 questions (including sub-parts). Pay attention to the links in each of the questions – I tell you exactly where to go for the answers. The assignment is due in recitation on February 13.
- January 23
- Tonight's recitation is canceled.
- January 23
-
If you don't have am account on the iLab machines, you can now create one at:
https://www.cs.rutgers.edu/resources/systems/ilab/newaccount/
After accounts are created there is a five minute delay before account information is pushed to the client machines. If you have problems creating your account, have them email help@cs.rutgers.edu - January 23
- Welcome!