Difference between revisions of "Cryptography"
Jump to navigation
Jump to search
| Line 33: | Line 33: | ||
;Signing: if you sign anything with private key, the only way to verify the signature is to decrypt with the matching public key. | ;Signing: if you sign anything with private key, the only way to verify the signature is to decrypt with the matching public key. | ||
= SSL and TLS = | |||
Communication via SSL | |||
'''FTP,SMTP, HTTP''' operate at Application Layer, but when we securing with '''SSL (SSL wrapper)''' we put cryptographic wrapper around the communication at the '''Transport Layer''' | |||
<source> | |||
HTTP,FTP,SMTP ----- 7.Application | |||
6.Presentation | |||
5.Session | |||
SSL Wrapper ------ 4.Transport | |||
3.Network | |||
2.Data Link | |||
1.Physical | |||
</source> | |||
Revision as of 12:02, 20 July 2019
Encryption protocols
| Symmetric | Asymmetric |
|---|---|
|
|
. System-1 System-2
#Encryption decryption
download
[data encrypted] -----> [data decrypted]
- with public2 key - with private2 key
#Signing
[data encrypted] -----> [data decrypted]
- with public2 key - with private2 key
- signed with private1 key - verified signature with public1 key
#Note, where needed the public key exchange happen, eg. via CA distribution process or protocol initialisation etc.
- Signing
- if you sign anything with private key, the only way to verify the signature is to decrypt with the matching public key.
SSL and TLS
Communication via SSL FTP,SMTP, HTTP operate at Application Layer, but when we securing with SSL (SSL wrapper) we put cryptographic wrapper around the communication at the Transport Layer
HTTP,FTP,SMTP ----- 7.Application
6.Presentation
5.Session
SSL Wrapper ------ 4.Transport
3.Network
2.Data Link
1.Physical