CSE 484 / CSE M 584: Computer Security -- Autumn 2015

Administrivia (Syllabus)


Class Mailing List and Forum



In-class Activities

Final Project

Extra Credit




Research Readings (CSE M 584)

Final Project

Slides and Scribe Notes

Section Slides

Administrivia (Syllabus)



Tadayoshi Kohno (Yoshi), Instructor

Gabriel Cadamuro, TA

Kiron Lebeck, TA

Adrian Sham, TA

Bo Wang, TA

Email Address, to reach all staff:


Office Hours

Yoshi:  Wednesdays, 11:30am-12:20pm, CSE 558

TAs:  Tuesdays, 2:00pm-3:00pm, CSE 006

         Fridays, 9:00am-10:00am, CSE 220

Class Time and Location:

MWF 10:30-11:20am, SAV 264

Map of SAV:  http://www.washington.edu/maps/#!/sav 

Section Times:  

Th 1:30-2:30 EEB 003 (map of EEB:  http://www.washington.edu/students/maps/map.cgi?EEB)

Th 2:30-3:20 ARC G070 (map of ARC:  http://www.washington.edu/students/maps/map.cgi?ARC)


(CSE 326 or CSE 332) and (CSE 351 or CSE 378).

You should have maturity in both the mathematics of computer science and in the engineering of computer systems. This means that you should: have a good understanding of data structures and algorithms; be comfortable writing programs from scratch in C and Java; be comfortable writing and debugging assembly code; and be comfortable in a command-line Unix development environment (gdb, gcc, etc). You should also have a good understanding of computer architecture, operating systems, and computer networks. Most importantly, you should be eager to challenge yourself and learn more!

Required textbook:        

Foundations of Security, Daswani, Kern, and Kesavan, ISBN 1-59059-784-2.

Examples for further reading:        

Handbook of Applied Cryptography, Menezes, van Oorschot, and Vanstone. Available online at http://cacr.uwaterloo.ca/hac/.  This is a reference book.

Cryptography Engineering, Ferguson, Schneier, and Kohno, ISBN 978-0470474242.

Security Engineering, Anderson. Available online at http://www.cl.cam.ac.uk/~rja14/book.html 

Security in Computing, Fourth Edition, Pfleeger and Pfleeger, ISBN 0-13-239077-9.

Network Security, Second Edition, Kaufman, Perlman, and Speciner, ISBN 0-13-046019-2.

Information Security, Stamp, ISBN 978-0-471-73848-0.

Writing Security Tools and Exploits, Foster and Liu, ISBN 1-59749-997-8.

No Tech Hacking: A Guide to Social Engineering, Dumpster Diving, and Shoulder Surfing, Long, ISBN 1597492159.

The Codebreakers: The Comprehensive History of Secret Communication from Ancient Times to the Internet, Kahn, ISBN 978-0684831305.

The Code Book: The Science of Secrecy from Ancient Egypt to Quantum Cryptography, Singh, ISBN 978-0385495325.

Class Mailing List and Forum


The class mailing list is multi_cse484a_au15@uw.edu. We will use this list to make official class-related announcements.

We will assume that all students in the class will be on this list, and furthermore, we will assume that everybody will be checking their mail regularly (at least once a day, during the week). It is conceivable that we will use the mailing list to announce assignments, or to make changes/fixes to assignments.

For discussions related to the class, please use this forum:  https://catalyst.uw.edu/gopost/board/kohno/40925/.

Subscribing to the Mailing List

If you're enrolled in CSE 484 or CSE M 584, then your @u.washington.edu email address should be automatically subscribed. If you just enrolled, you may have to wait a day before the system is automatically updated. You can verify your enrollment or join the mailing list by going to this page:  https://mailman1.u.washington.edu/mailman/listinfo/multi_cse484a_au15.

Mailing List Archives

All email sent to the class list is archived here:  https://mailman1.u.washington.edu/mailman/listinfo/multi_cse484a_au15.


CSE 484

CSE M 584


Unless otherwise specified, all submissions must be typed and submitted as PDF files; handwritten assignments and non-PDF files will not be accepted. Unless otherwise specified, submit homeworks online at the following URL:  https://catalyst.uw.edu/collectit/dropbox/kohno/36375.

At the top of your assignment, be sure to write your name, email address, UWNetID, the homework assignment number (e.g. "Homework 1"), due date, any references that you used (besides the course texts and assigned readings), and the names of any people that you discussed the assignment with.

Include your name and UWNetID on each page.

In-class Activities

In-class activities are just that -- worksheets or activities done in class.  Be sure to write your name, email address, UWNetID, and the date on each activity when you turn it in.

You are given at least three free in-class activity days, which you can use while you’re traveling, etc.  We will clarify this description in class.  The use of the words “at least” is because we currently do not know exactly how many days we’ll have in-class activities, and we may allow additional free days depending on the total number of days with in-class activities.

Final Project

For your final project, you will be asked to create a short video explaining a topic or concept in computer security in detail.  This is an opportunity to dive deeply into a topic that interests you.  Details forthcoming.  There may be project checkpoints along the way.  

Extra Credit

There will occasionally be opportunities for extra credit.

We will also award extra credit for forum participation.



(Many of these policies are taken verbatim from previous instances of this and other UW CSE courses.)

What to Bring to Each Class:

Bring at least a few sheets of blank sheets of paper and two pens or pencils (two, in case one breaks or runs out of ink) to each class.  The sheets of paper should be pre-separated leafs of paper (and, for example, not pages ripped from a spiral notebook).

Ethics Form

To receive a non-zero grade in the course, you must sign the security and privacy course ethics form by 5pm on October 9, 2015.  The form is available online at:  https://catalyst.uw.edu/webq/survey/kohno/281797.

Late Policy:

Please pay careful attention to the due dates of the assignments. For most labs, and possibly other assignments (but not in-class activities), if you hand in the assignment late, we will take off 20% for each day it is late. When computing the number of days late, we will round up; so an assignment turned in 25 hours late will be downgraded 40%. Please note, however, that some assignments cannot be turned in late; we will clearly specify when this is the case, but do also ask if the policy seems unclear. We will not consider granting Incompletes.


The "Reasonable Person Principle" applies throughout this course. This principle simply states that a reasonable request made in a reasonable fashion shall be reasonably handled by reasonable persons. Let's all be "reasonable people" working on the same team to make this a great learning experience.

Cheating vs. Collaboration:

Collaboration is a very good thing. On the other hand, cheating is considered a very serious offense. Please don't do it! Concern about cheating creates an unpleasant environment for everyone. If you cheat, you risk losing your position as a student in the department and the college. The department's policy on cheating is to report any cases to the college cheating committee. What follows afterwards is not fun for anyone.

So how do you draw the line between collaboration and cheating? Here's a reasonable set of ground rules. Failure to understand and follow these rules will constitute cheating, and will be dealt with as per university guidelines.

The Gilligan's Island Rule: This rule says that you are free to meet with fellow student(s) and discuss assignments with them. Writing on a board or shared piece of paper is acceptable during the meeting; however, you should not take any written (electronic or otherwise) record about the assignment away from the meeting. This applies when the assignment is supposed to be an individual effort or whenever two teams discuss common problems they are each encountering (inter-group collaboration). After the meeting, engage in a half hour of mind-numbing activity (like watching an episode of Gilligan's Island), before starting to work on the assignment. This will assure that you are able to reconstruct what you learned from the meeting, by yourself, using your own brain.

The Freedom of Information Rule: To assure that all interactions are on the level, you must always write the name(s) of who you talk with about your assignments (aside from course staff) on your assignment. These names should be listed in a prominent location at the top of the first page of your assignment.


https://courses.cs.washington.edu/courses/cse484/15au/homework/hw2.html [pdf version]

https://courses.cs.washington.edu/courses/cse484/15au/homework/hw3.html [pdf version]


Unless otherwise specified, submit labs online at the following URL:  https://catalyst.uw.edu/collectit/dropbox/kohno/36375.

        Please enter your group information in the Google Form posted on the class forum.

Research Readings (CSE M 584)

Research reading instructions available online here: http://courses.cs.washington.edu/courses/cse484/15au/CSEM584Readings.html .

CSE 484 students may read some papers for extra credit (see the research reading page for more details).

Final Project

Final project instructions

Slides and Scribe Notes

Slides and scribe notes will be posted here.

Section Slides

In class worksheets