|
Course Description - |
|||||||||
| Focus | |||||||||
|
Cryptography provides a critical foundation upon which much of
computer security is based. Cryptography is necessary to provide both
integrity and confidentiality of the data that is exchanged in a
computer network. There are many methods of encryption, and each has
its strengths and weaknesses in terms of performance, security, and
requirements for management of secret information used to hide or
disclose information.
This course will provide an intensive overview of the field of cryptography, providing a historical perspective on early systems, building to the number theoretic foundations of modern day cryptosystems. Students will learn how cryptosystems are designed, and to match cryptosystems to the needs of an application. Students will also study basic cryptanalysis and will be presented with real life breaches of common cryptosystems so that they better understand the dangers that lurk in cryptosystem design and in the design of systems that rely on cryptography. |
|||||||||
| Relationships to CS 530 and CS 556 | |||||||||
|
I have received many inquires regarding the difference
between this class and the
Cryptography
class (CS 556).
CS 556 should be considered as an "advanced" cryptography class with emphasis on the theoretic side of cryptography. The Applied Cryptograph class is a more "introductory" cryptography class with emphasis on the applied side of cryptography (less emphasis on mathetical proofs). There will be some overlap between the Applied Cryptograph class and CS 530. This course is meant to be taken either concurrently or before CS 530. Tentatively, starting in Fall of 2007, this course will be offered as CS 531. |
|||||||||
| Academic Integrity Policy | |||||||||
| Please make sure you read the Academic Integrity Policy of this course. | |||||||||
| Textbooks | |||||||||
Required:
|
|||||||||
| Syllabus / Topics Covered | |||||||||
The following schedule and topics are tentative and are subject to
change without notice. (The Handbook of Applied Cryptography is denoted
as HAC below.)
|
|||||||||
| Academic Calendar | |||||||||
| A link to the USC web site is provided here for your convenience. You can get information such as academic calendar there. | |||||||||
|
Most class related announcements will be done through e-mail via
an e-mail reflector setup by the instructor. Please see
instructions on how to get
on this list (you should do this as soon as possible).
Please do not ask the following types of questions in your e-mail (although they are appropriate for office hours):
|
|||||||||
| Lecture Slides from a Previous Semester | |||||||||
| Lecture slides from Spring 2006 are provided below for your information. Our class may not follow these slides exactly. | |||||||||
| Homework | |||||||||
| There will be 5-7 homework assignments consisting of small programming assignments. | |||||||||
| Exams | |||||||||
| A midterm and a final examination will be given. The date of the midterm examination will be posted near the top of the class home page. The date of the final examination is firm and it is also listed near the top of the class home page. Any schedule conflicts regarding the midterm exam date must be resolved with the instructor at least one week before the exam date. | |||||||||
| Grading | |||||||||
The grading breakdown is as follows:
Pleaes also note the following:
|
|||||||||
| Late Policy | |||||||||
|
All homeworks must be turned in on time.
Late submissions will receive severe penalties. Due to clock skews,
electronic submissions of homework assignments will
be accepted within 15 minutes after the specified deadlines without
penalties. If your submission is beyond the 15 minutes grace period,
you will receive 75% of your grade if your submission
is 15 minutes late beyond the grace period;
you will receive 50% of your grade if your submission
is 30 minutes late beyond the grace period;
you will receive 25% of your grade if your submission
is 45 minutes late beyond the grace period;
and you will receive a score of zero otherwise.
If you are unable to complete a homework assignment due to illness or family emergency, please see the instructor as soon as possible to get an extension. A doctor's note is required as proof of illness or emergency. |
|||||||||
| Regrading Policy | |||||||||
| All requests to change grading of homework or exams must be submitted in writing within one week of the time the initial grade was given. Requests must be specific and explain why you feel your answer deserves additional credit. A request to re-grade an assignment can result in the entire assignment being re-evaluated and as a result the score of any part of the assignment be increased or lowered as appropriate. | |||||||||
| Office Hours | |||||||||
| The instructor's office hours are held twice a week for one hour each. If you are not available during the designated time for office hours, you are always welcome to make an appointment (and reserve a timeslot) to see the instructor. | |||||||||
| Extra Credits | |||||||||
| No extra credit assignments will be given for this class. So, there is not need to ask. Try your best from the beginning! | |||||||||
| Class Newsgroup | |||||||||
|
A forum is setup on DEN for the purpose of students-to-students discussions.
The main purpose of this forum is for the students to
discuss things about homeworks and projects with each other.
Students may
not exchange answers here because it would violate academic
integrity policy of USC. Posting of small code segments
(no more than 5 lines) is allowed as long as it is meant to clarify discussions.
The instructor and the TA do not normally read this forum. Please do not post questions for them here. Please make sure that you have read the Academic Integrity Policy of this course. |
|||||||||
| Implicit Student Agreement | |||||||||
|
All work including homeworks, programming
assignments and exams must be that of the individual student. It is often
productive to study with other students. However, if any portions of homeworks
or programming assignments are found to be shared between two (or more)
students, zero credit will be given to all students concerned and all students
will be disciplined. This policy is in the interest of those students who
do their own work, which hopefully applies to all of you in this class.
This policy also holds for programming assignments. In this class, we will use sophisticated automated program checkers to detect cheating. Be aware that the program checkers have demonstrated very good results and are widely used within the academic community. Any student caught cheating will be given zero credit and will be disciplined. It is the students responsibility to submit their assignments to the TA in time. For students who satisfied the CSci402 prerequisite at other universities or through work experience, this course assumes that you understand concurrency, synchronization, and UNIX programming. You should be able to write large programs in C/C++. No special assistance or consideration will be offered if your background is inadequate. |
|||||||||
| Student Responsibilities | |||||||||
|
During the semester you are responsible for completing the assigned
readings, homeworks, programs, and exams.
You are expected to read all the papers in detail. Not all details will be covered in class. We will assume knowledge of material covered in EE450 and a C language programming proficiency from CSci402 or its equivalent. If you covered the introductory material at some other school it is YOUR responsibility to fill in any missing background. Feel free to ask me for advice on appropriate introductory readings if you feel your background is insufficient. We expect you to attend every class meeting. If you do happen to miss a session, you are responsible for finding out what material was covered and if any administrative announcements were made. You must do so BEFORE the next session (e.g., if there is an assignment given during the missed session, you are still responsible for completing it by the next week along with the other students). You are advised to read the papers for a particular lecture before attending the lecture. This will greatly enhance your understanding of the subject matter. |
|||||||||
| Fairness | |||||||||
| The instructor must treat all students equally and cannot give special treatment to any particular student. Therefore, please do not ask special favors from the instructor because of your circumstances. This may seem unfair to you because you believe that your circumstances are special (understandably, everone does). But the rule the instructor must follow is that whatever he offers you, he must offer to the entire class. | |||||||||
| Auditing | |||||||||
| Auditing is not permitted for this class. | |||||||||
| Additional Resources | |||||||||
Programming:
|
|||||||||