SSL Certificates
Comodo Digital Certificates
|
Comodo PositiveSSL |
Reissues |
Unlimited |
Encryption Level |
2048-bit |
Step-Up Functionality |
No |
Authentication |
Domain Check and Quick Validation |
Average Issuance Speed |
Within minutes |
Browser Compatibility |
Highest in the industry |
Securing Web domains |
Yes |
Securing gateways (e.g.. Citrix Secure Gateways) |
Yes |
Securing multiple hosts for a domain on the same server |
No |
Seal and Green Line |
Yes |
Annually |
$14.99 |
|
|
|
Thawte Digital Certificates
|
Thawte SSL 123 |
Thawte SSL Web Server |
Thawte SSL SGC Super Cert |
Thawte SSL Wildcard |
Reissues |
Unlimited |
Encryption Level |
256-bit |
Step-Up Functionality |
No |
No |
Yes |
No |
Authentication |
Domain Check and Quick Validation |
Comprehensive Business Verification and Authentication |
Comprehensive Business Verification and Authentication |
Comprehensive Business Verification and Authentication |
Average Issuance Speed |
Within minutes |
Less than 2 Days |
Less than 2 Days |
Less than 2 Days |
Browser Compatibility |
Highest in the industry |
Highest in the industry |
Highest in the industry |
Highest in the industry |
Securing Web domains |
Yes |
Yes |
Yes |
Yes |
Securing gateways (e.g.. Citrix Secure Gateways) |
Yes |
Yes |
Yes |
Yes |
Securing multiple hosts for a domain on the same server |
No |
No |
No |
Yes |
Seal and Green Line |
Yes |
Yes |
Yes |
Yes |
Annually |
$39.99 |
$89.99 |
$229.99 |
$499.99 |
Biennially |
$69.99 |
$159.99 |
$439.99 |
$799.99 |
|
Order Now |
Order Now |
Order Now |
Order Now |
|
GeoTrust Digital Certificates
|
RapidSSL |
QuickSSL Premium |
True BusinessID |
True BusinessID with EV |
True BusinessID Wildcard |
Reissues |
Unlimited |
Encryption Level |
256-bit |
Authentication |
Domain Check and Quick Validation |
Domain Check and Quick Validation |
Comprehensive Business Verification and Authentication |
Comprehensive Business Verification and Authentication |
Comprehensive Business Verification and Authentication |
Average Issuance Speed |
Within minutes |
Within minutes |
Less than 2 Days |
Less than 2 Days |
Less than 2 Days |
Browser Compatibility |
Highest in the industry |
Highest in the industry |
Highest in the industry |
Highest in the industry |
Highest in the industry |
Securing Web domains |
Yes |
Yes |
Yes |
Yes |
Yes |
Securing gateways (e.g.. Citrix Secure Gateways) |
Yes |
Yes |
Yes |
Yes |
Yes |
Securing multiple hosts for a domain on the same server |
No |
No |
No |
No |
Yes |
Seal and Green Line |
Yes / No |
Yes / No |
Yes / No |
Yes / Yes |
Yes / No |
Annually |
$24.99 |
$89.99 |
$149.99 |
$179.99 |
$599.99 |
|
|
|
|
|
|
|
SSL protocol allows client/server applications to communicate across a
network in a way designed to prevent eavesdropping and tampering.
Since most protocols can be used either with or without TLS (or SSL) it is
necessary to indicate to the server whether the client is making a TLS
connection or not. There are two main ways of achieving this, one option is to
use a different port number for TLS connections (for example port 443 for
HTTPS). The other is to use to the regular port number and have the client
request that the server switch the connection to TLS using a protocol specific
mechanism (for example STARTTLS for mail and news protocols).
Once the client and server have decided to use TLS they negotiate a stateful
connection by using a handshaking procedure.[3] During this handshake, the
client and server agree on various parameters used to establish the connection's
security.
The handshake begins when a client connects to a TLS-enabled server requesting a
secure connection and presents a list of supported CipherSuites (ciphers and
hash functions).
From this list, the server picks the strongest cipher and hash function that it
also supports and notifies the client of the decision.
The server sends back its identification in the form of a digital certificate.
The certificate usually contains the server name, the trusted certificate
authority (CA) and the server's public encryption key.
The client may contact the server that issued the certificate (the trusted CA as
above) and confirm the validity of the certificate before proceeding.
In order to generate the session keys used for the secure connection, the client
encrypts a random number with the server's public key and sends the result to
the server. Only the server should be able to decrypt it, with its private key.
From the random number, both parties generate key material for encryption and
decryption.
This concludes the handshake and begins the secured connection, which is
encrypted and decrypted with the key material until the connection closes.
If any one of the above steps fails, the TLS handshake fails and the connection
is not created