Term
|
Definition
| Many Apps use their own encryption. standards include SSL/TLS |
|
|
Term
|
Definition
| Not a common layer for encryption |
|
|
Term
|
Definition
| Not a common layer for encryption |
|
|
Term
|
Definition
| Neither TCP not UDP offer any encryption, little encryption happens here |
|
|
Term
|
Definition
| IPSec via software that encrypts enterything inside an IP packet but the IP Addy and a few other fields |
|
|
Term
|
Definition
| A common place for encryption using proprietary encryption devices. they scramble all data in Ethernet frames except MAC address info. encoded and decoded on the fly. |
|
|
Term
|
Definition
| No Common encryption done on this layer |
|
|
Term
| how Public Key cryptography works |
|
Definition
| 1-receiver creates 2 keys(pub-k offered to sender, private-k kept secret) 2-pub key sent to sender 3-sender encrypts message with pub-k. 4-encrypted message sent to receiver. 5-receiver decrypts message with private-k (!Non-repudiation!) |
|
|
Term
|
Definition
| Rivest Shamir Adleman: Diffie-Helman Key Exchange improved upon - fully functional algorithm - enables secure digital signatures |
|
|
Term
|
Definition
| Diffie-Hellman Key Exchange - introduced by whitfield Diffie, Martin Hellman, & Ralph Merke in the late 70's - Asymmetric-key Algorithm |
|
|
Term
|
Definition
| encrypted data in single "chunks" |
|
|
Term
|
Definition
| takes a single bit at a time and encodes on-the-fly |
|
|
Term
|
Definition
| Data Encryption Standard: by US gov late 70's - 64-bit blocks - 56-bit key - susceptible to brute force - evolved into 3DES, IDEA(International), and Blowfish |
|
|
Term
|
Definition
| Rivest Cipher 4: developed by Ron Rivest late 80's - stream cipher - still used but can fall to successful attacks |
|
|
Term
|
Definition
| Advanced Encryption Standard: Late 90's - 128-bit block - 128-, 192-, or 256-bit key - secure, practically uncrackable (for now) - able to sometimes compete with stream cipher |
|
|
Term
|
Definition
| Secure Socket Layer: combines digital certificates and RSA - server driven - HTTPS need SSL certificate |
|
|
Term
|
Definition
| 1-request made by client for server's pub-key and cert. 2-request sent to client. 3-encryption level negotiated. 4-session key generated by client using server's pub-key. 5-session key used for data encryption |
|
|
Term
|
Definition
| Transport Layer Security: similar to SSL, but not compatible |
|
|
