Re:Vulnerability in Microsoft TLS library could allow remote...
by mike_hearn on Tuesday November 11, 2014 @04:55PM
(#8592476)
One of the reasons websites have been slow to roll out SSL for everything is CPU load, so it's a legitimate concern for a high traffic website. However, most of the ways SSL was speeded up involved algorithmic / protocol level improvements and not micro-optimisations of the code. So I'm not sure that a safe language has a permanent disadvantage here.
[ Parent
| on HN ]
Re:Vulnerability in Microsoft TLS library could allow remote...
by bkeroack on Tuesday November 11, 2014 @05:16PM
(#8592605)
This was possibly true 10-20 years ago (SSL is that old). It is no longer reasonable and is usually just an excuse.
That said, in my experience, native SSL/TLS within IIS is incredibly slow/inefficient. Running on 2012R2 (so a modern version), terminating SSL at IIS resulted in me being able to trivially peg the server's CPU using Apache Ab on my laptop. So clearly you need a good implementation.
Re:Vulnerability in Microsoft TLS library could allow remote...
by lazyjones on Wednesday November 12, 2014 @07:45AM
(#8595170)
Another reason was/is that handshakes add noticeable latency (because several packets are sent in both directions), so web browsing experience and consequently, retention and conversion rates will suffer.
The worst barrier was probably the cost and hassle of obtaining browser-accepted certificates though.