• Thursdays, 9:00-10:30 (sine tempore)
• Im Neuenheimer Feld 348, Room 013

First lecture: Thursday, October 17, 2002
Last lecture: Thursday, February 6, 2003
Final, written exam: Thursday, February 13, 2003

• After class
• or by appointment or chance
• Contact information:
  Dr. Christoph Schuba
  Christoph.Schuba@Sun.COM
  Sun Microsystems, Inc.
  Altrottstr. 31
  69190 Walldorf, Germany
  +49 (6227) 356-229 (voice)
  +49 (6227) 356-222 (fax)

The spectacular growth of electronic commerce on the Internet and frequent public reports of security breaches in highly visible computer systems have created an acute awareness of computer security issues. Daily activities, such as communicating with colleagues, banking, and retrieving grade reports are becoming increasingly reliant upon computer systems and communication networks.

This course offers an introduction to topics in computer and network security. The basics of the theory behind cryptography are covered. The course teaches how to use cryptography in support of security services. It explains the types of security services needed in distributed systems and computer networks and finally discusses selected practical aspects of and current public issues in computer security and cryptography.

The course is intended for students who are interested in learning the basic concepts, principles, and mechanisms that will allow them to identify, understand, analyze, and perhaps solve security problems in computer and distributed systems.

• Final, written examination: Thursday, February 13, 2003, in class
  (covering all material, unless explicitly excluded.)
  

No early or late exam will be given. The exam is closed book. There will be no makeup exams. If the exam is missed, it will score zero points.

Hints on how to study for exams will be provided closer to the exam date.

• [MB01] - Mel, H.X. and Baker, Doris, Cryptography Decrypted, Addison-Wesley, 2001.

• [Pfl97] - Charles P. Pfleeger, Security in Computing, Second Edition. Prentice Hall Inc., Upper Saddle River, NJ. 1997.
• [For94] - Warwick Ford, Computer Communications Security: Principles, Standard Protocols and Techniques, Prentice Hall, Englewood Cliffs, NJ. 1994.
• [Sta95] - William Stallings, Network and Internetwork Security - Principles and Practice. Prentice Hall, Englewood Cliffs, NJ. 1995.
• [KPS95] - Charlie Kaufman, Radia Perlman, and Mike Speciner, Network Security - Private Communication in a Public World, Prentice Hall, Engelwood Cliffs, NJ. 1995.
• [Amo94] - Edward Amoroso, Fundamentals of Computer Security Technology, Prentice Hall, Engelwood Cliffs, NJ. 1994.
• [Den82] - Dorothy Denning, Cryptography and Data Security, Addison Wesley Publishing Company, Inc. 1982.
• [Sch95] - Bruce Schneier, Applied Cryptography, Second Edition, Wiley. 1995.
• [Sti95] - Douglas Stinson, Cryptography - Theory and Practice, CRC Press Inc. 1995.
• [Smi97] - Richard Smith, Internet Cryptography, Addison Wesley Publishing Company, Inc. 1997.
• [ISV95] - David Icove, Karl Seger, and William VonStorch, Computer Crime: A Crimefighter's Handbook. O'Reilly & Associates. 1995.
• [AJP95] - Marshall Abrams, Sushil Jajodia, and Harold Podell(eds.), Information security: an integrated collection of essays. IEEE Computer Society Press. 1995.
• [GS96] - Simson Garfinkel and Eugene Spafford, Practical UNIX & Internet Security, Second Edition, O'Reilly and Associates, Inc., Sebastopol, CA. 1996.
• [CB94] - William Cheswick and Steven Bellovin, Firewalls and Internet Security: Repelling the Wily Hacker, Addison-Wesley. 1994.
• [Sta96] - William Stallings, Practical Cryptography for Data Internetworks, IEEE Computer Society Press. 1996.
• [Kah96] - David Kahn, The Codebreakers, Scribner. 1996.
• [Sto90] - Clifford Stoll, The Cuckoo's Egg: Tracing a Spy Through the Maze of Computer Espionage, Doubleday. 1989.
• [FM99] - Stefan Fischer und Walter Müller, Netzwerkprogrammierung unter LINUX und UNIX, 2. Auflage, Carl Hanser Verlag München Wien, 1999.
• UNIX manual pages
• Javasoft - Network programming web pages. Under http://www.javasoft.com

icns-0203@pvs.iwr.uni-heidelberg.de

• Address: icns-0203@pvs.iwr.uni-heidelberg.de
• Subscribe via http://pvs.iwr.uni-heidelberg.de/mailman/listinfo

Please use the mailing list for posting questions and answers that are of general interest to everybody. The instructor will send class announcements about homework, exams, etc. to this list, so it is important that you check your e-mail frequently, or you may miss an important announcement.

Homework assignments will consist of several written assignments (problem solving) and at least one programming assignment.

All written assignments are due at the beginning of class on the due date stated on the assignment (unless otherwise noted). Assignments will be graded as quickly as possible.

Please submit answers to your assignments type set. They must carry the student's name and ID number on each submitted page. If pages are stapled, name and ID on the first page are sufficient. All electronic submissions (program source code, make files, scribe notes, etc.) must have name and ID in a comment block at the beginning of each file.

Any assignment that cannot be read will score zero points. For example, variables, factors, and exponents must be distinguishable. A reasonable standard of English expression and grammar is also required.

Although this is not a software engineering course, programs must exhibit high standards of programming style, structure, layout, and documentation. Efficient algorithms and appropriate data structures should be used. It must be evident how the code was tested, either through documentation of code testing, or through the inclusion of test programs or self-checking code. Comments in the code should be helpful and enlightening. This is especially important if a submitted program does not run. Note that correct programs may lose points for failing to live up to the outlined programming standards.

See Handouts for an example assignment and solution.

• An electronic copy of your each program that needs to be submitted as source code (e.g., Crypto.java)
• A copy of your electronic test report

• A printout of your source code
• A short written document describing your program and its data structures.
• Your written answers to the problems.

Assignments may be discussed with classmates or with the instructor to get a critique of ideas and better understanding of the concepts behind assignments. Students are encouraged to consult the library or online resources as necessary. It is OK to seek help while debugging a program once it is written.

At the same time, programming assignments submitted for credit must be the student's own work. In particular, the solutions, ideas, and words submitted must not be shared with classmates. Homework solutions must be written by each student. Homework solutions may neither be read nor copied by other students. Programs must be created, typed, and documented by each student. Programs must be solely their creation. It is recommended to save all handwritten notes and printouts generated until the end of the semester. This is a protective precaution for the authors of work in the event of plagiarism or loss of submitted work. Any missing output should be reported to the instructor immediately.

Plagiarism and cheating are very serious offenses and will not be tolerated. Any cheating and will be dealt with according to University policies. The instructor is available to clarify these rules.

1. Consult the course Web pages.
2. Consult instructor postings from mailing list.
3. Students are encouraged to post questions and answers to other students' questions via the mailing list.
4. If none of the above helps: send e-mail to the instructor.
5. If none of the above helps: ask during class or talk to the instructor during office hours.