Dawn Song (675 Soda Hall)
John Bethencourt (firstname.lastname@example.org)
Todd Kosloff (email@example.com)
Rusty Sears (firstname.lastname@example.org)
MW 2:30pm-4:00pm, 306 Soda
101: Tu 11:00am - 12:00pm, 4 Evans
102: Tu 5:00pm - 6:00pm, 85 Evans
103: W 10:00am - 11:00am, 5 Evans
Song: W 5-6pm, 675 Soda
Bethencourt: F 2-4pm, 517 Soda
Kosloff: M 4-6pm, 711 Soda or 535 Soda
Sears: Tu 12-2pm, 711 Soda
(or by appointment)
Note: Please only contact the instructor or TA's directly by email if you have an issue that only relates to you personally. If you have a question about the course or material in general, please post to the newsgroup or send mail to the mailing list. That way the response will be visible to the entire class. Thanks!
Previous semesters: http://inst.eecs.berkeley.edu/~cs161/archives.html
The mailing list may be used for important announcements, so all students must be on it. If you missed the first lecture or didn't write your email address on the sheet that was passed around, be sure to subscribe yourself.
Server: news.berkeley.edu (from campus), authnews.berkeley.edu (off campus)
The course schedule includes information on lecture topics, readings, and assignment related deadlines.
This course will cover the most important features of computer security, including topics such as cryptography, operating systems security, network security, and language-based security. After completing this course, students will be able to analyze, design, and build secure systems of moderate complexity.
List of course topics (tentative):
You must have taken CS 61C (Machine Structures). Also, you must have taken either Math 55 or CS 70 (Discrete Mathematics).
The required textbook is Computer Security, 2nd Edition (Dieter Gollmann, Wiley, 2006). Reading assignments will be given from this book. The book Security Engineering (Ross Anderson, Wiley, 2001) is optional. It provides extra reading and background. The book can be accessed online here or you can purchase a copy. We will also provide lecture notes for most of the lectures.
From time to time, we may discuss vulnerabilities in computer systems. This is not intended as an invitation to go exploit those vulnerabilities! It is important that we be able to discuss real-world experience candidly; everyone is expected to behave responsibly. Breaking into other people's systems is inappropriate, and the existence of a security hole is no excuse.