1 of 21

Lecture 1: Introduction and Preliminaries

Cryptography (CS 427/529)

Tue, Thu 2:00-3:50pm

COVL (Covell Hall) 221

2 of 21

Instructor: Jiayu Xu

  • Fourth-year assistant professor, research area: cryptography
  • Email: xujiay@oregonstate.edu
  • Office hours: Tue noon-1:50pm (before class), KEC 2021;�or by appointment/email

3 of 21

Teaching Assistant: Tingfei “Carlos” Feng

  • Second-year PhD student, research area: cryptography
  • Email: fengti@oregonstate.edu
  • Office hours: TBD

4 of 21

Logistics

  • 5 homeworks, 2-5 problems per homework
    • Lowest score dropped
  • Deadline in ~2 weeks
  • No exams!

5 of 21

  • Resubmission allowed
    • I will explain solution in class after deadline
    • After that, you can submit a correction of your previous submission (mistake you made + correct answer)
    • MUST BE DONE BEFORE THE SECOND-TO-LAST CLASS (03/10)
    • You can get up to 50% of your lost scores back
    • First submission graded by TA, resubmission graded by me
    • Resubmission will be graded more harshly (more rigor required)
  • Example:
    • You got 6/10 in 1st submission, then 8/10 in resubmission
    • Final score (for this homework) = 6+(8-6)×50% = 7/10

6 of 21

  • Can discuss with classmates, search solutions online, etc.
    • MUST CITE YOUR SOURCE (e.g., title of book/link to webpage)
  • Must write down your solution independently
    • Submissions of 2 students should never look similar
  • Use of generative AI (e.g., ChatGPT) allowed (but discouraged)
    • MUST INCLUDE PROMPTS
  • You must understand whatever you write
    • I may ask you to explain your (re)submission in my office

7 of 21

Textbook

8 of 21

What is Κρυπτογραφία?

9 of 21

Classical cryptography

  • Ancient Greek
    • κρυπτός (kryptós) = hidden / concealed / secret
    • γράφειν (graphein) = to write
    • “To write in a secret manner”
  • Maintain secrecy of message over an insecure channel (encryption)
  • Ad hoc construction of schemes (art)
    • Design an encryption scheme → scheme broken (“cryptanalyzed”) → design a new scheme → new scheme broken → …

10 of 21

Modern cryptography (since 1970s): from art to science

  • 1. Scope much broader
    • Encryption schemes
    • Message authentication codes
    • Hash functions
    • ……
  • Protect communication against an adversary
  • 2. Formal definitions of security
    • “A scheme is secure if no adversary can break it with significant probability”
    • “Break” is usually defined via a game (played between adversary and an imaginary challenger)
    • “A scheme is secure if no adversary can win the security game with significant probability”

11 of 21

  • 3. Formal proofs of security
    • Usually based on assumptions (number theoretical/security of underlying schemes)
    • “If assumption A holds, then scheme S is secure (per the security definition)”

12 of 21

From theory to practice

  • 1. Identify a need
    • “I need a secure encryption scheme”
  • 2. Propose a scheme
  • 3. Prove security of scheme
    • “Thm: If assumption A holds, then encryption scheme S is secure”
  • 4. Standardize scheme (by ISO, IETF, …)
  • 5. Implement scheme
  • This class: steps 1, 2, 3 (theoretical cryptography)
    • Steps 4, 5 → cryptographic engineering
    • It is possible that a “provably secure” scheme is broken in practice due to bugs in implementation

13 of 21

Warning: math

  • This class is about defining and proving security of cryptographic schemes, in an abstract, mathematically rigorous manner
  • NOT about implementing and applying such schemes (that’s for a course in “applied security”)
  • What we will do is defining and proving stuff (pen and paper)
  • NOT programming

14 of 21

Preliminaries

15 of 21

Bitstrings

  •  

16 of 21

Discrete probability theory

  •  

17 of 21

  •  

18 of 21

Basic facts

  •  

19 of 21

Independence of events

  •  

20 of 21

Conditional probability

  •  

21 of 21

Test your knowledge…

  •