[outages] Akamai Cert Issues today

[Jim Witherell]

Aside from finding ways to make it fail, my point is that casual users are complaining to the help desk about it. We can duplicate it externally at home and on mobile devices. 


Away from the debate about Akamai's issue that has evidently been out there awhile:

-We're wondering what happened yesterday to break all these disparate websites 

-We're wondering if anyone else is seeing the problem or are receiving unusually high volume of complaints about getting to certaincertain and unrelated https sites in the last 18 or so hours. 


Sent from Yahoo Mail on Android

From:"Jay Ashworth via Outages" <outages at outages.org>
Date:Wed, Sep 30, 2015 at 11:21 PM
Subject:Re: [outages] Akamai Cert Issues today

----- Original Message -----
> From: "Sean Donelan via Outages" <outages at outages.org>

> This is how Akamai has handled non-SSL customers for the last 15 years.
> It is the same error message, and the same action. You just noticed
> it.
> 
> If you use https for a non-SSL customer on Akamai, you will connect to
> a Akamai server using a "default" SSL certificate for all customers on
> port 443.
> 
> If you use https for a SSL customer on Akamai, you connect to different
> IP addresses listening for specific customers which return a customer
> specific SSL certificate.

Doesn't that interact rather badly with HTTPS-Anywhere?

Or, more to the point, would it not already have done so to date, rather
loudly?

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                      jra at baylink.com
Designer                    The Things I Think                      RFC 2100
Ashworth & Associates      http://www.bcp38.info         2000 Land Rover DII
St Petersburg FL USA      BCP38: Ask For It By Name!          +1 727 647 1274


_______________________________________________
Outages mailing list
Outages at outages.org
https://puck.nether.net/mailman/listinfo/outages

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20151001/071c13ee/attachment.htm>