University of Virginia, Department of Computer Science
CS588: Cryptology - Principles and Applications, Fall 2001

Manifest: Monday 26 November 2001

Assignments Due

Project Presentations

Each presentation will be strictly limited to thirteen minutes. If you plan ahead and use your time wisely, this is plenty of time.

Your presentation need not involve all team members speaking, but all members of your team should contribute to developing it.

The goal of almost all presentations is to get your audience interested enough in what you are talking about that they will want to learn more. For your project presentations, the goal is to make your audience understand and remember the most important idea from your project. You cannot expect to convey a lot of technical information (that's what the report is for), but you should be able to motivate your work and convince your audience why it is important and interesting, make it abundantly clear to your audience what you actually did, and explain one nugget that came out of it.

Your target audience for this presentation is the other students in the class. You should assume your audience knows everything covered in CS588 (but perhaps remind them briefly of important things relevant to your presentation).

All talks should tell a story. Don't fall into the trap of reading a list. All good stories:

Your project presentation (and nearly all other presentations you give!) should follow this model.
Presentation Schedule

Wednesday 28 November

Team 1 - Timing Attacks
Team 3 - Group Communication System for Ad-hoc Wireless Networks
Team 5 - Video Steganography
Team 7 - UVa Healtcare System: Medical Privacy
Team 9 - Cookies for Authentication

Monday 3 December

Team 2 - CipherChess
Team 4 - SSH Keystrokes
Team 6 - De-Clawing Carnivore
Team 8 - National ID Card
Team 10 - Digital Watermarking for Music

Project Reports

Your project reports are due 5 December at the beginning of class. Except in the most dire of circumstances, I will be unwilling to accept any reports after 2:05 on Wednesday, 5 December.

You should turn in a paper printout of your report, and a URL for your report (which should be either .html or .pdf). I will read the paper you turn in, but make the web reports available from the course site.

Like talks, papers should also tell stories. Your reports should include substantial technical details, though.

The final report should motivate, describe and evaluate your work. You may organize your final report into sections as you see fit. It should include (but is not limited to):

There are no length constraints for the final report, but you should aim to be as concise, clear and organized as possible. The writing and presentation should be at a high quality. It would be highly worthwhile to exchange reports with a classmate and review each others reports before submitting them.

Note: I will be intolerant of sexist language in your reports and deduct 5 points from any report that carelessly or systematically uses sexist language. See Hofstadter's A Person Paper on Purity in Language if you don't think this is important.



CS 655 University of Virginia
Department of Computer Science
CS 588: Cryptology - Principles and Applications
David Evans