Re:Moving forward on improving HTTP's security
by pixelcort on Wednesday November 13, 2013 @07:29AM
(#6724745)
The cost usually isn't so much the cost of the cert, it's more the cost of the static IP.
[ Parent
| on HN ]
Re:Moving forward on improving HTTP's security
by johntb86 on Wednesday November 13, 2013 @07:38AM
(#6724794)
What browser would support HTTP 2.0 but not SNI?
Re:Moving forward on improving HTTP's security
by nfoz on Wednesday November 13, 2013 @10:32AM
(#6725781)
Lots of utilities that aren't conventional "browsers" but talk HTTP.
Re:Moving forward on improving HTTP's security
by mikeash on Wednesday November 13, 2013 @10:38AM
(#6725836)
The question is still completely valid. What tool would support HTTP 2 but not SNI?
Re:Moving forward on improving HTTP's security
by jalada on Wednesday November 13, 2013 @07:45AM
(#6724828)
I'd not heard of SNI before. Is this something that can be used now?!
Re:Moving forward on improving HTTP's security
by kijin on Wednesday November 13, 2013 @07:54AM
(#6724856)
Yes ... as long as you don't need to support IE on XP, Android 2.x, or Java 6.
Re:Moving forward on improving HTTP's security
by Macha on Wednesday November 13, 2013 @08:50AM
(#6725105)
> IE on XP, Android 2.x
That's still a lot of devices.
Re:Moving forward on improving HTTP's security
by Xylakant on Wednesday November 13, 2013 @09:06AM
(#6725184)
Neither of those browsers supports HTTP/2.0, so that's moot.
Re:Moving forward on improving HTTP's security
by acdha on Wednesday November 13, 2013 @04:25PM
(#6728668)
> IE on XP
In this case, that's also going away hard next year when Microsoft discontinues support for Windows XP. At that point it'd be really tempting to suggest switching to Firefox or Chrome, both of which do support SNI.
Re:Moving forward on improving HTTP's security
by wmf on Wednesday November 13, 2013 @02:56PM
(#6727999)
SNI is useful for hosting, but I don't think it helps embedded devices. Is any CA willing to issue me a cert for 192.168.0.1? Wait, don't answer that.
Re:Moving forward on improving HTTP's security
by Sami_Lehtinen on Wednesday November 13, 2013 @09:53PM
(#6730227)
Why do you want to use global CAs for internal services? Wouldn't it be better to use your own CA? I find out that identifying site by it's certfingerprint is much stronger authentication than the fact that it got valid cert. Actually it would be a good idea not to trust any other than company's internal CA for internal services. But as far as I know, bowsers aren't up to this challenge. Maybe AD allows this, but I haven't ever seen any post how to do it.
Re:Moving forward on improving HTTP's security
by acdha on Wednesday November 13, 2013 @04:24PM
(#6728664)
It'd be more interesting to see if a CA would issue a cert for something.local — sadly, you're probably right to fear the worst…
Re:Moving forward on improving HTTP's security
by jlgaddis on Wednesday November 13, 2013 @08:10PM
(#6729867)
They will -- but I believe that's to be phased out by 2015 or so.
Re:Moving forward on improving HTTP's security
by cpach on Wednesday November 13, 2013 @03:36PM
(#6728280)
You can solve this by setting up your own Certificate Authority.
Re:Moving forward on improving HTTP's security
by millerm on Wednesday November 13, 2013 @08:51AM
(#6725110)
If we'd get to it and get IPv6 up, the business of selling static IPs should become a very unprofitable as there would be a virtually unlimited supply of IPs. Why is this not happening?!?
Re:Moving forward on improving HTTP's security
by RobAley on Wednesday November 13, 2013 @10:30AM
(#6725767)
For the same reason that SSL adoption is currently lower than ideal, for many uses the increased cost (actual cost, and cost of time) is not perceived to be worth it. For many/most uses IPv4 works just fine and non-SSL is just fine.
Re:Moving forward on improving HTTP's security
by sophacles on Wednesday November 13, 2013 @10:34AM
(#6725802)
Don't forget the cost and barrier to entry of setting up the cert and SSL and learning to administer the extra steps well, without introducing more holes through complexity.
Re:Moving forward on improving HTTP's security
by IgorPartola on Wednesday November 13, 2013 @09:41AM
(#6725402)
IPv6 is free as in 4 billion ^ 4 addresses free.
Re:Moving forward on improving HTTP's security
by KMag on Wednesday November 13, 2013 @01:07PM
(#6727053)
Presuming you're noting exponentiation with ^, 4 billion ^ 4 billion addresses would mean 128 gigabits per address. IPv6 addresses don't take up half a gigabyte each in any sane encoding.
IPv6 has 128-bit addresses, which works out to about 4 billion ^ 4 addresses, not 4 billion ^ 4 billion addresses.
Re:Moving forward on improving HTTP's security
by IgorPartola on Wednesday November 13, 2013 @02:48PM
(#6727937)
My original comment said 4 billion ^ 4 addresses, as in 2^128. There is no second "billion" in that line.