News for hackers. Stuff that matters.

A comment on Intent to deprecate: Insecure HTTP. Parent comment

Re:Intent to deprecate: Insecure HTTP by FullyFunctional on Tuesday April 14, 2015 @02:57AM (#9372523)
That. I have managed to get through the steps but there was nothing simple about it and I wouldn't be able to replicate it without looking it all up again. Unfortunately, SSL isn't even an option on my el-cheapo shared webhosting service (as I understood it, it needs a dedicated precious IPv4 address).

Contrast this with Dan J. Bernstein's wonderful CurveCP. It's so simple to set up and requires no CA involvement; you just need to be able to add a NS server entry.

[ Parent | on HN ]
Re:Intent to deprecate: Insecure HTTP by yellowapple on Tuesday April 14, 2015 @10:24PM (#9378561)
> as I understood it, it needs a dedicated precious IPv4 address

A good webserver would actually be able to provide multiple SSL certs on a single IP address by using "Server-Name Indication" (SNI). This is definitely (as far as I know) supported on nginx, and probably supported by Apache's httpd.

[ Parent | on HN ]