Block, SkipCaptcha, Upload, Automoderated users, Check users, delete, edit, Moderators, move, oversight, protect, rollback
19,320
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
cert. auth
However, there is still a flaw in this system alone. During the initial exchange, an attacker can intercept the server and client public keys, and send his own in their place. Neither party would ever know, but the attacker has essentially tapped into the entire exchange using this method, known as a "man-in-the-middle attack." To deal with this issue, servers using HTTPS have their public keys indexed by certificate authorities. When a client attempts to visit a site using HTTPS, he or she checks the supplied public key against the one on file with a certificate authority. If they match, the process continues and the key as saved on the client's device for future use. If not, the user is shown a security warning. An increasing number of browsers even block access altogether in case of a supplied key/certificate mismatch.<ref>http://www.helpwithpcs.com/jargon/http.htm</ref><br />
However, there is still a flaw in this system alone. During the initial exchange, an attacker can intercept the server and client public keys, and send his own in their place. Neither party would ever know, but the attacker has essentially tapped into the entire exchange using this method, known as a "man-in-the-middle attack." To deal with this issue, servers using HTTPS have their public keys indexed by certificate authorities. When a client attempts to visit a site using HTTPS, he or she checks the supplied public key against the one on file with a certificate authority. If they match, the process continues and the key as saved on the client's device for future use. If not, the user is shown a security warning. An increasing number of browsers even block access altogether in case of a supplied key/certificate mismatch.<ref>http://www.helpwithpcs.com/jargon/http.htm</ref><br />
Asymmetric encryption is very slow and inefficient, however, once connected, the host and client share a symmetric key which they use from then on. They can then communicate with reasonable certainty that their exchange is private.<br />
Asymmetric encryption is very slow and inefficient, however, once connected, the host and client share a symmetric key which they use from then on. They can then communicate with reasonable certainty that their exchange is private.<br />
==Certificate authorities==
There are many certificate authorities. The following is a list of some of the most popularly used ones, as reported in May 2017.<ref>https://w3techs.com/technologies/overview/ssl_certificate/all</ref>
{| class="wikitable"
|-
! Name !! Usage rate !! Market Share
|-
| Comodo || 15.3% || 41.4%
|-
| IdenTrust || 10% || 27%
|-
| Symantec Group || 5.4% || 14.6%
|-
|GoDaddy Group || 2.8% || 7.6%
|-
|GlobalSign|| 1.7% || 4.7
|-
|DigiCert || 0.8% || 2.2%
|-
|Certum || 0.2% || 0.6%
|-
|Entrust || 0.2% || 0.4%
|-
|StartCom || 0.1% || 0.4%
|-
|Secom Trust || 0.1% || 0.3%
|-
|Trustwave || 0.1% || 0.3%
|-
|Actalis || 0.1% || 0.2%
|-
|Let’s Encrypt || <0.1% || <0.1%
|-
|WISeKey Group || <0.1% || <0.1%
|}
==References==
==References==