null
US
Sign In
Sign Up for Free
Sign Up
We have detected that Javascript is not enabled in your browser. The dynamic nature of our site means that Javascript must be enabled to function properly. Please read our
terms and conditions
for more information.
Next up
Copy and Edit
You need to log in to complete this action!
Register for Free
35365
Crypto U3, Theoretical vs. Practical Security
Description
IYM002 (Unit 3 - Further basics of Crypto Design) Mind Map on Crypto U3, Theoretical vs. Practical Security, created by jjanesko on 31/03/2013.
No tags specified
iym002
unit 3 - further basics of crypto design
iym002
unit 3 - further basics of crypto design
Mind Map by
jjanesko
, updated more than 1 year ago
More
Less
Created by
jjanesko
almost 12 years ago
120
12
0
Resource summary
Crypto U3, Theoretical vs. Practical Security
perfect secrecy
Attacker gets no info about the plaintext by observing the ciphertext, other than what was was known before the ciphertext was cobserved.
Gordon's "flash math" version of perfect secrecy
Annotations:
[Image: https://lh5.googleusercontent.com/-bm3mNTn_vpY/UVf2zUjHt8I/AAAAAAAAAbM/2PH9xvxP4QQ/s582/flashymathdefinitionofperfectsecrecy.png]
in theory, there exists unbreakable cryptosystems
perfectly secret
one time pad
each letter of a plaintext is transformed with a randomly generated key that is the same length as the plaintext
practical problems
key establishment expensive (creating random sequences)
key distribution a challenge (key changes each time)
key length potentially very large
OTP
practical security
COVERAGE what is the covertimeneeded for the plaintext?
design system to protect against known attacks that would result in plaintext compromise in shorter than covertime
computational complexity
algorithm complexity
for each possible input to the algorithm, the amount of time it takes to run
length of input measured in bits
mathematical complexity - algorithms can be run in
polynomial time
a algorithm that can usually be run in real time with any sized input
"time taken to execute process for an input of size n is not greater than n^r for some number r"
example: multiplication, addition
expontential time
an algorithm that cannot be run in "real" time with most inputs
"if the time taken to execute the process for an input of size n is approximately a^n for some number a"
example: factorization
Just because an algorithm is exponentially hard, it does not mean that it is impossible to solve for all values.
computing exhaustive key search time
need
algorithm complexity
computer speed
example
general algorithm complexity forkey search is 2^n
our example key length is 30, so the complexity for this example is n^30
our example computer does 1,000,000 operations per second
So, 2^30 / 10^6 = roughly 1000 seconds
EVOLUTION when designing algorithms, take into consideration current and emerging state of processing power in computers
when designing cryptosystems, make sure that the implementation does not undermine the power of the algorithms used
practice good key management
Show full summary
Hide full summary
Want to create your own
Mind Maps
for
free
with GoConqr?
Learn more
.
Similar
Crypto U4, Block Cipher, Cipher Feedback Mode (CFB)
jjanesko
Crypto U4, Block Cipher, Cipher Block Chaining Mode (CBC)
jjanesko
Crypto U1, Basic Principles
jjanesko
Crypto U4, Stream Cipher
jjanesko
Crypto U4, Block Cipher, Electronic Codebook Mode (ECB)
jjanesko
Crypto U4, Block Cipher, Counter Mode
jjanesko
Crypto U2, Crypto design principles
jjanesko
Crypto U8, example dynamic password scheme
jjanesko
Crypto U10 (part 1), Key Management & Lifecycle
jjanesko
Crypto U10 (part 2), Key Management and Lifecycle
jjanesko
Crypto U8 (part 3), entity authentication
jjanesko
Browse Library