SSL Certificate: Difference between revisions
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
* Authenticated- Asymmetric cryptography always authenticate the server endpoint of conversation while the client endpoint is optionally authenticated. | * Authenticated- Asymmetric cryptography always authenticate the server endpoint of conversation while the client endpoint is optionally authenticated. | ||
* Reliable- It uses Message Authentication Code (MAC) to check the message integrity and secure hash functions. | * Reliable- It uses Message Authentication Code (MAC) to check the message integrity and secure hash functions. | ||
==Versions== | |||
The SSL Protocol has the following version:<ref>[http://httpd.apache.org/docs/2.0/ssl/ssl_intro.html SSL/TLS Strong Encryption: An Introduction]</ref> | |||
* SSL Protocol v2.0- The first protocol implemented by Netscape | |||
* SSL Protocol v3.0- An improvement to SSL Protocol v2.0 to protect data transfer from specific security threats and to provide support to certificate chains and add non-RSA ciphers. | |||
* TLS v1.0- The current standard proposed by IETF. An improvement to the SSL Protocol v3.0. This version is an enhancement from MAC layer to HMAC, block padding for block ciphers, message order standardization and more alert messages were added. | |||
==References== | ==References== | ||
Revision as of 22:27, 2 November 2011
SSL is the acronym for Secure Sockets Layer. It was designed to use applications that will allow users to securely send and receive data over the internet. SSL was developed by Netscape in 1994 to provide security between communicating applications (client and server). The technology uses two protocols, the record protocol, which provides basic security to higher level protocols and handshake protocol, which allows client-server authentication.[1] SSL is integrated in web browsers e-mail and instant messaging applications and other programs with encryption key given by a Certification Authority (CA) in the form of a digital certificate also known as (SSL Certificate). The digital key is authenticated by the handshake protocol in one or both end points during the SSL session. The handshake protocol will then set-up a unique symmetric key to generate keys that will encrypt and decrypt data to maintain a secure communications and data transfers between computers during SSL connection.[2] During the SSL connection the record protocol maintains confidentiality and message integrity by encrypting applications data using the Message Authentication Code (MAC).[3]
Basic Properties of SSL Protocol Channel Security[edit | edit source]
Based on the Internet Draft submitted by Kipp E.B. Hickman of Netscape to the IETF, the SSL protocol channel security is:[4]
- Private- It uses Symmetric cryptography to encrypt data and define a secret key through a simple handshake.
- Authenticated- Asymmetric cryptography always authenticate the server endpoint of conversation while the client endpoint is optionally authenticated.
- Reliable- It uses Message Authentication Code (MAC) to check the message integrity and secure hash functions.
Versions[edit | edit source]
The SSL Protocol has the following version:[5]
- SSL Protocol v2.0- The first protocol implemented by Netscape
- SSL Protocol v3.0- An improvement to SSL Protocol v2.0 to protect data transfer from specific security threats and to provide support to certificate chains and add non-RSA ciphers.
- TLS v1.0- The current standard proposed by IETF. An improvement to the SSL Protocol v3.0. This version is an enhancement from MAC layer to HMAC, block padding for block ciphers, message order standardization and more alert messages were added.