4 ms·
As far as I know the expensive part is not the transmission of data (which is done via AES and extremely cheap), but the establishment of the SSL connection usi
by gst 16y ago
As far as I know the expensive part is not the transmission of data (which is done via AES and extremely cheap), but the establishment of the SSL connection using public key cryptography. Even though this only needs to be done once for each "incoming" user, due to persistent connections.
- drdaeman 16y agoWhat StatusNet said, that they have problem not with CPU power, needed for SSL handshakes, but with implementing load balancing. Unfortunately, linked discussion is non-informative on subject, just saying "...gets really complicated".
- xuhu 16y ago"Really complicated" is possibly related to having to decrypt/reencrypt to HTTP at every hop. Otherwise all but the last node are basic pipes.
- jrockway 16y agoUh, no? It's SSL from the user to the load balancer. It's cleartext from the load balancer to the backend servers. There is only one SSL hop; over the insecure internet from your frontend server to the user. Once you are on the physically-secure local network, you don't need SSL anymore.
- mfukar 16y agoHTTP and HTTPS are end-to-end, care to clarify what you meant by "at every hop"?