Re:Even Akamai screws up their SSL certs
by agwa on Tuesday January 28, 2014 @09:08PM
(#7141357)
Actually, they probably don't intend for people to use www.akamai.com with HTTPS. If you add an override for the bad cert, you end up getting redirected to a non-HTTPS site anyways. I don't see anything like a login link on www.akamai.com so this is probably OK. (Of course it would be nice if everything were HTTPS...)
[ Parent
| on HN ]
Re:Even Akamai screws up their SSL certs
by slipangel on Wednesday January 29, 2014 @02:51AM
(#7142581)
The a248 cert is used for all SSL requests for properties delivered over Akamai's non-ssl network. It's useful to be able to serve SSL requests even if the cert doesn't have a the hostname in question on it.
Regarding the cipher sneering below: Akamai's default settings probably err on the side of acceptance. Not all of their customers are Amazon.coms - mom & pop ecommerce are unlikely to do anything that would cause a visitor's SSL connection to fail, and changing the ciphers back to the high-acceptance settings would increase their cost of implementation per cert. I'm guessing they manage more than a few of those.
> Of course it would be nice if everything were HTTPS...
Nice try, Certificate Authorities!
Re:Even Akamai screws up their SSL certs
by Shish2k on Wednesday January 29, 2014 @08:22AM
(#7143617)
It would be nice if everything were HTTPS, but the default behaviour for a self-signed cert was "accept it the first time, but don't show the lock icon or anything, and then warn if it changes" - ie self-signed HTTPS is the new HTTP
Re:Even Akamai screws up their SSL certs
by fragmede on Tuesday January 28, 2014 @09:23PM
(#7141423)
>> Of course it would be nice if everything were HTTPS...
> Nice try, Certificate Authorities!
Nice try, NSA.
Re:Even Akamai screws up their SSL certs
by richforrester on Tuesday January 28, 2014 @10:35PM
(#7141675)
>>> Of course it would be nice if everything were HTTPS...
>> Nice try, Certificate Authorities!
> Nice try, NSA.
Nice try, HN.