USC CSD Home
 

-

 
General Information
Time   :   MW 11:00pm - 12:20pm
Location : OHE 132
Instructor   :   Bill Cheng, Office Hours: MW 12:45pm - 1:45pm in SAL 342, E-mail: <bill.cheng@usc.edu> or <william@bourbon.usc.edu>   (Please do not send HTML e-mails. They will not be read.)
TA   :   Ho Chung, E-mail: <hochung@usc.edu>, Office Hours: Thu 10am - 12pm in SAL 339
Grader   :   Arti Khandelwal, E-mail: <khandelw@usc.edu>,    (The grader will hold office hours the week after the announcement of each programming assignment's grades.)
Midterm Exam   :   Wed, 3/2/2005 (firm), in OHE 132.
Final Exam   :   11am-1pm, Wed, 5/4/2005 (firm), in OHE 132.
Newsgroup   :   A forum is setup on DEN for the purpose of students-to-students discussions.
Msg Archives   :   messages from Bill, messages from Ho
 
Class Resources
Description   :   textbooks, topics covered, grading policies, additional resources, etc.
Papers   :   required technical papers.
Lectures   :   slides from lectures in HTML and PDF formats.
Homeworks   :   (4-5 homeworks will be assigned. Please also see important information about programming assignments below.)
Term Paper   :   one term paper to be turned in towards the end of the semester.
 
News
(in reversed chronological order)
  • 4/25/2005: The final exam is closed book, closed notes, and closed everything (and no "cheat sheet"). Also, no calculators, cell phones, or any electronic gadgets are allowed. a photo ID. Your ID will be collected at the beginning of the exam and will be returned to you when you turn in your exam. There will be assigned seating.

    The final exam is comprehensive. In addition to the topics covered by the midterm exam, the final exam will also cover the following topics:

    • Key Management
      • ...
      • key storage
      • key generation
      • group key management
        • rekeying group keys using batched digital signatures
    • Authentication: know, have, about you
      • Unix passwords
      • Kerberos and Directory Servers
      • public key
      • single sign on
      • some applications and how they do it
      • weaknesses
      • Lamport's hash chains
      • trust models for certification
      • GSS-API
      • applications (unix login, telnet, rsh/rlogin, ssh, http/https, ftp, Windows login, e-mail, NFS, Radius)
      • Microsoft Passport
      • Liberty Alliance
    • Authorization
      • Access Matrix
      • capability
      • agent-based
      • policy models
        • discretionary policy
        • mandatory policy
        • Bell LaPadula
      • distributed mechanisms
        • proxies
        • GAA-API
    • Modeling Strength of Security
      • current models and their weaknesses
      • bounds
    • Evaluation of Malicious Activity on the Internet
      • host based measurement
        • different scans
      • network based measurement
        • network telescope
        • backscatter
      • attack classification
        • single source vs. multiple source
    • Intrusions
      • detection - how
        • signature based
        • anomaly based
      • detection - where
        • network based
        • host based
        • application based
      • response
      • coordination of detection
        • CISL
        • IDMEF
    • Wireless
      • the real difference
        • devices and connectivity
      • some of the benefits
        • redundancy of aommunication paths
        • autonomy
      • WEP vulnerabilities
      • Bluetooth vulnerabilities
      • need for end-to-end security
    • Upload
      • real-time timestamp
      • low-latency commit
      • timely data transfer
      • security protocol
        • use of SHA1
        • use of digital signature
        • use of public key and secret key encryption
    • Privacy
      • transparent society vs. big brother
      • concent
      • authenticity-bit
    • Homeworks

  • 2/27/2005: The midterm exam will be closed book, closed notes, and closed everything (and no "cheat sheet"). Also, no calculators, cell phones, or any electronic gadgets are allowed. Please bring a photo ID. Your ID will be collected at the beginning of the exam and will be returned to you when you turn in your exam. There will be assigned seating.

    The midterm exam will cover the following topics:

    • Cryptography
      • basic building blocks
        • transposition/permutation
        • substitution
        • monoalphabetic substitution cipher
        • one-time pad
        • stream vs. block
      • conventional/symmetric/secret key
        • DES (and 3DES)
          • components (Fiestel Network, S-boxes, P-boxes)
          • modes of operation (ECB, CBC, CFB, OFB)
          • HW2
        • AES/Rijndael, others (UNIX password)
      • public key/asymmetric
        • RSA
          • private/public key
          • encryption/decryption
        • ElGamal, Elliptic curve cryptosystems
      • digital signatures
      • Diffie-Hellman key exchange
      • hash functions
        • one-time signature (signature using only hashes)
          • Lamport's one-time signature
          • Merkle's one-time signature and tree-based scheme
        • SHA-1 broken
        • message authentication code
    • Key Management
      • pairwise key management
      • conventional key management
        • KDC, Kerberos, Needham-Schroeder
      • public key management
        • certification authority

  • 1/20/2005: The TA's office hour on 2/3/2005 has been moved to 2/1/2005, 10am - 12pm.

  • 1/19/2005: A companion lab for this course will be offered as CSCI 590 (Directed Research). All students are encouraged to take this lab class. For more information, please see the web page for this class.


  • 12/14/2004: Watch this area for important announcements.
 
Prerequisites
 
Important Information about Programming Assignments
Some homework assignments will require you to write some code. You must write your code in C/C++. No other programming language will be accepted and your program must compile and run with a Makefile on nunki.usc.edu. (Sorry, no Java.) You must be familiar with the UNIX development environment (vi/pico/emacs, cc/gcc or g++/CC, make, etc.)

If a student signs up late for this class, he/she is still required to turn all projects and homeworks on time or he/she will receive a score of 0 for these assignments. No exceptions!

 

   [Please see copyright regarding copying.]