What does a reduction turn an attack into?
- A faster computer
- A longer secret key
- An algorithm for an assumed-hard problem
In a security game, what must you name?
- The brand of computer used
- The adversary's powers and what winning means
- The name of the programmer
A secure scheme leaves every efficient adversary with negligible advantage.
Circle one: True False
Breaking the scheme would break the assumption. What follows?
- The assumption becomes easy at once
- The scheme is as safe as the assumption is hard
- The scheme needs no keys
Sketch step one of a reduction. Where do you begin?
- Take an adversary that wins the game against the scheme
- Assume no adversary will ever try
- Change the hard problem first
The proof holds, yet the app leaks secrets through a bug. Does that contradict the proof?
- Yes, proofs cover all bugs
- Yes, the game models every deployment
- No, the proof never promised the implementation was correct
A vendor claims the proof means their code has no bugs. What is wrong?
- Proofs make code run faster
- The proof covers the scheme in the game model, not the deployed code
- Games remove the need for keys
An adversary wins with large advantage. What does the reduction give you?
- An efficient algorithm for the supposedly hard problem
- A proof that the problem is easy for everyone
- A new game with no adversary