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
59597
Crypto U12, SSL
Description
IYM002 (Unit 12 - Crypto Systems) Mind Map on Crypto U12, SSL, created by jjanesko on 28/04/2013.
No tags specified
iym002
unit 12 - crypto systems
iym002
unit 12 - crypto systems
Mind Map by
jjanesko
, updated more than 1 year ago
More
Less
Created by
jjanesko
over 11 years ago
88
10
0
Resource summary
Crypto U12, SSL
background
sits on top of TCP
roughly equivalent to TLS
created by IETF
Internet Engineering Task Force
design
designed for open environments where entities do not have a security association
security association: having some relationship where communicating entities have agreed or exchanged security related info or cryptographic keys
security requirements
confidentiality
data origin authentication
entity authentication
can provide 2 types of authentication
client only
mutual entitiy
minimalizes public key operations
decryption of public key message is placed at the server and saves work for the client
crypotgraphic primitives: uses hybrid encryption
public key cryptography
enables symmetric key establishment
digital signatures
sign certificates and facilitate entity authentication
MACs
used to provide data origin authentication and entity authentication
hash functions
part of MACs, digital signatures, key derivation
algorithms used
Flexible standard. Supports many different algorithms and key lengths.
during exchange, entities agree upon a "cipher suite"
cipher suite - collection of algorithms that communicating entities agree upon
common
AES in CBC mode
HMAC using SHA-256
digital signature algorithms
RSA
DSA
protocols used
handshake
extablish agreements appropriate to secure communication
agree upon cipher suite
extablish entitity authentication
establish keys for secure channel
sometimes mutual entity authentication is needed in closed systems. basic handshake protocol does not provide this.
so, a "modified handshake protocol" can be used
record
implements secure channel
security issues
will not work if process failures
ex: client does not perform PKCS checks
implementation failures
relies on many cryptographic primitives
key mgt failures
usage failures
security features overestimated and gain a false sense of security
key management
generation
asymmetric keys
through PKMS
symmetric keys
derived from master secret
lightweight
allows many keys to be generated
reliant on client's ability to generate a random pre-master secret
establishment
pre-master key shared through public key encryption
storage
private keys must be stored in safe place
very sensitive, but short-lived
usage
key separation enforced
separate keys for communication between client & server and server & client
prevents reflection attacks
Show full summary
Hide full summary
Want to create your own
Mind Maps
for
free
with GoConqr?
Learn more
.
Similar
Crypto U12 (part 1), crypto for mobile telecom
jjanesko
Crypto U12, WLAN
jjanesko
Crypto U12 (part 2), crypto for mobile telecom
jjanesko
Crypto U12 GSM,UTMS Hierarchy Diagram
jjanesko
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 U3, Theoretical vs. Practical Security
jjanesko
Crypto U4, Stream Cipher
jjanesko
Crypto U4, Block Cipher, Electronic Codebook Mode (ECB)
jjanesko
Crypto U4, Block Cipher, Counter Mode
jjanesko
Browse Library