CS 600.443: Security and Privacy in Computing
Paperback - 384 pages (June, 2001)
White-Hat Security Arsenal: Tackling the Threats
by Aviel Rubin
Addison-Wesley ISBN: 0-201-71114-1
Grades will be determined as follows:
The project description is available here.
- Homeworks: 20%
- Project: 30%
- Midterm: 25%
- Final: 25%
Homeworks must be done individually, without any collaboration
with others in the class. The project may be done in groups of
2 to 4. Everybody within each group will receive the same grade on
the project. In cases where some members of the group feel that
a group member did not participate enough, please report this to
the professor, who will deal with this on a case by case basis.
Howeworks and projects are due at the beginning of class, 9:00 a.m.
on the stated due date. Late homeworks will be penalized 5 points
per weekday. Late projects will not be accepted, barring very serious
circumstances. Each phase of the project will build on previous
phases, and some will depend on work done by other groups, so
they must be turned in on time.
There is no collaboration allowed on exams. You must do only
your own work. There are no textbooks, notes, or computers allowed
during exams. Exams will be based on any material presented in
lecture and any material in the assigned readings.
Lecture slides and notes will not generally be available,
so please come to class and make sure to take notes.
Course Mailing List
All students must sign up for the class mailing list. Send mail
with "subscribe cs443"
in the message body. Then, to send mail to the class,
send it to cs443 at cs.jhu.edu.
Important announcements will be maid via the mailing list, and students
will be responsible for any information posted to the list.
I will hold my scheduled office hours at 326 NEB after class
on Thursdays, 10:15 a.m. to 12:00 p.m. When needed, I will have
hours there on Fridays as well.
My office is at 416 Wyman Park, and we can meet there by appointment.
The TA for our class is David Friedman, email@example.com.
You can meet with the TA by appointment.
David Friedman has put together
a page containing all of the group reports for the project.
Book, chapters 1-2
Voydock and Kent (pdf)
Introduction to the course
Lecture topic: Introduction to cryptography
Discussion of project
Lecture topic: Introduction to Crypto (cont.)
Book, chapters 4-6
Diffie Hellman paper (pdf)
NSF voting paper (pdf)
Lecture topic: Wireless security
Lecture topic: Alternative authentication technologies
Caltech MIT report (pdf)
California report (pdf)
California report appendix (pdf)
CACM e-voting paper (pdf)
part 1 of project assigned, due 9 a.m. on 2/20
Discussion of project
Lecture topic: Voting systems and requirements
Lecture topic: Voting systems and requirements (cont.)
Book, chapters 10-11
Bro paper (ps.gz)
Turn in part 1 of project
Part 2 of project assigned, due 9 a.m. 3/6
In class: presentation of part 1 by each group
- Turn in part 1 of project
- Part 2 of project assigned
- Discussion of part 2 of project
Lecture topic: Guest lecture by Lorrie Cranor
- Homework #1 assigned, due 2/28 9:00 a.m.
Book, chapters 7-9, 12
Passport security paper (pdf)
Lecture topic: Network security
-Turn in Homework #1
Lecture topic: Web Security
part 2 of project turned in
part 3 of project assigned, due 3/20 9 a.m.
In class: Presentation of part 2 by each group
- Turn in part 2 of project
- Discuss part 3 of project
Lecture topic: viruses & worms
- Homework #2 assigned, due 3/21 9:00 a.m.
Graphical passwords paper (pdf)
smash stack for fun & profit (txt)
stackguard paper (pdf)
part 3 of project due
part 4 of project assigned
Lecture topic: Crypto (cont.), Viruses & Worms
- Turn in part 3 of project
Lecture topic: Secure Programming, guest lecturer, Gary McGraw
- Turn in homework #2
Lecture catchup and Midterm review
Lecture topic: Intellectual Property protection, guest lecturer Randy Sabbet
Lecture topic: Privacy
Assigned reading: none, work on your projects
progress report due 4/10, 9 a.m.
Guest lecture by Ari Schwartz Associate Director of the Center for Democracy and Technology
- Turn in progress report
Lecture topic: P3P
- Homework #3 assigned, due 4/25 9:00 a.m.
4/17 Passover, no lecture
4/18 Passover, no lecture
Book, chapter 13
CACM Chaum paper (pdf)
Crowds paper (pdf)
Umass paper (pdf)
Lecture topic: Anonymity technologies
- Turn in homework #3
Lecture topic: Anonymity technologies (cont.)
- Turn in final project report
Project presentation & demos
Project presentation & demos
Final exam: May 15 9:00 a.m.
Computer Science Department Academic Integrity Code
The strength of the university depends on academic and personal
integrity. In your studies, you must be honest and truthful. Ethical
violations include cheating on exams, plagiarism, reuse of
assignments, improper use of the Internet and electronic devices,
unauthorized collaboration, alteration of graded assignments, forgery
and falsification, lying, facilitating academic dishonesty, and unfair
Academic honesty is required in all work you submit to be graded.
Except where the instructor specifies group work, you must solve all
homework and programming assignments without the help of others. For
example, you must not look at any other solutions (including program
code) to your homework problems or similar problems. However, you may
discuss assignment specifications with others to be sure you
understand what is required by the assignment.
*If* your instructor permits using fragments of source code from
outside sources, such as your textbook or on-line resources, you must
properly cite the source. Not citing it constitutes plagiarism.
Similarly, your group projects must list everyone who participated.
Falsifying program output or results is prohibited.
Your instructor is free to override parts of this policy for
particular assignments. To protect yourself: (1) Ask the instructor
if you are not sure what is permissible. (2) Seek help from the
instructor or TA, as you are always encouraged to do, rather than from
other students. (3) Cite any questionable sources of help you may
Students who cheat will suffer a serious course grade penalty in addition
to being reported to university officials. You must abide by JHU's Ethics
Code: Report any violations you witness to the instructor. You may consult
the associate dean of students and/or the chairman of the Ethics Board
beforehand. For more information, see the guide on Academic
Ethics for Undergraduates (http://www.advising.jhu.edu/ethics.html)
and the Ethics Board web site (http://ethics.jhu.edu).