3 ms·
I thought this was a repost of the same story from last February related to expired certs: http://www.wired.com/wiredenterprise/2012/02/azure_outage/ http://ww
by yajoe 14y ago
I thought this was a repost of the same story from last February related to expired certs:
http://www.wired.com/wiredenterprise/2012/02/azure_outage/ http://www.wired.com/wiredenterprise/2012/02/azure_outage/
I'm pretty tolerant of mistakes (I make them all the time), but I have little patience for repeating mistakes.
- smarx 14y agoIn this case, an SSL certificate has expired. The leap year issue last year was a bug about date addition: 2/29/2012 + 1 year was calculated as 2/29/2013, which is a date that doesn't exist. The only similarity is that both involved certificates. (The invalid date was used internally as an expiration date for a certificate.)
- vyrotek 14y agoGlad to see you around these parts Smarx :) You maybe not remember me but I came to Redmond for an Azure bootcamp you hosted for a few companies a few years ago. (I'm sure you did lots of those) I was with IActionable. We've had a few 'encounters' on the MSDN forums too. Azure sure has changed since those days... Definitely for the better! I see you've been busy since you left MS. Somehow I missed all the news about Site44!