Authored by: Anonymous on Sunday, September 09 2012 @ 06:00 PM EDT |
Minimal operational overhead since the load is in the front end handshake. Might
cause slight CPU load. Administrative concerns and additional servers, however.[ Reply to This | Parent | # ]
|
|
Authored by: JamesK on Sunday, September 09 2012 @ 10:14 PM EDT |
Actually, some sites, including Wikipedia and Google already have an encrypted
version available. All you have to do is use https instead of http in the URL.
If you want to automate it, you can use an add on called "HTTPS
Everywhere" with Firefox and Seamonkey browsers. This will automatically
select the encrypted URL when available.
---
The following program contains immature subject matter. Viewer discretion is
advised.[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Monday, September 10 2012 @ 02:04 PM EDT |
Also (not relevant for Wikipedia), it screws with trying to
host multiple domains on one IP address.
In a basic sense, the domain name in the request (along with
all the other data and headers) is encrypted and the server
doesn't know which key to use to decrypt it without knowing
the domain name.
There are a few approaches to avoid this vicious circle, but
they don't have widespread adoption (they either need
widespread browser upgrades or IPV6 adoption)[ Reply to This | Parent | # ]
|
|