I&#x27;m in a remote location where the only comms are via a satellite link.  This is what my internet connection looks like at the moment:<p><pre><code>    [ron@mighty:~] ping google.com
    PING google.com (4.35.21.152): 56 data bytes
    Request timeout for icmp_seq 0
    Request timeout for icmp_seq 1
    Request timeout for icmp_seq 2
    Request timeout for icmp_seq 3
    Request timeout for icmp_seq 4
    Request timeout for icmp_seq 5
    Request timeout for icmp_seq 6
    64 bytes from 67.201.56.75: icmp_seq=0 ttl=46 time=7264.039 ms
    64 bytes from 67.201.56.75: icmp_seq=1 ttl=46 time=6773.034 ms
    64 bytes from 67.201.56.75: icmp_seq=2 ttl=46 time=7007.539 ms
    64 bytes from 67.201.56.75: icmp_seq=3 ttl=46 time=6106.535 ms
    64 bytes from 67.201.56.75: icmp_seq=4 ttl=46 time=5740.475 ms
    64 bytes from 67.201.56.75: icmp_seq=5 ttl=46 time=5052.218 ms
    64 bytes from 67.201.56.75: icmp_seq=6 ttl=46 time=4352.883 ms
    64 bytes from 67.201.56.75: icmp_seq=7 ttl=46 time=3468.035 ms
</code></pre>
Under these circumstances I can just barely open a regular HTTP connection, but most HTTPS connections time out before they can be established.  So I can&#x27;t do a Google search :-(<p>(Even submitting this to HN required multiple attempts.)
Why SSL-everywhere is not necessarily a good idea in all circumstances