News for hackers. Stuff that matters.
Re:Google to prioritise secure websites by augustl on Thursday August 07, 2014 @09:19AM (#8147526)
Indeed. My static blog hosted on Linode behind Apache has survived a HN frontpage entry three times now. If I have to use HTTPS, does that mean I need a beefy server with lots of entropy?
Re:Google to prioritise secure websites by stephen_g on Thursday August 07, 2014 @09:24AM (#8147549)
Nope!

Google, from 2010: "On our production frontend machines, SSL/TLS accounts for less than 1% of the CPU load, less than 10KB of memory per connection and less than 2% of network overhead."

https://www.imperialviolet.org/2010/06/25/overclocking-ssl.h...

Entropy is a different matter, but I believe pretty much all virtualisation platforms have ways to ensure the VMs have enough entropy sources - so it should be fine.

Re:Google to prioritise secure websites by agwa on Thursday August 07, 2014 @09:23AM (#8147544)
No. My HTTPS blog hosted on Linode's smallest plan has survived a HN front page without any trouble. It's a myth that HTTPS causes significant resource overhead.

As for entropy, your server only needs a small amount of entropy to seed a CSPRNG, and the CSPRNG takes it from there.

Re:Google to prioritise secure websites by jgrahamc on Thursday August 07, 2014 @09:24AM (#8147551)
See "Is TLS Fast Yet?": https://istlsfastyet.com/