We're working on it.
We're back up. We'll post more about the root cause soon.
Parse is down due to SSL certificate expiry
51–56 of 56 posts
Re: Parse is down due to SSL certificate expiry
#52This is why I think its always good to build your apps in the 'Good old way', instead of relying on a third party like Parse. It becomes a bottle-neck in situations like these, where in you are kind of stuck - Either, you will have to re-write your code from scratch, or wait for them to fix it, with a lot of uncertainty.
Is there any value in companies like Parse selling their software as installable on your own servers (i.e., GitHub Enterprise). I ask, rhetorically, because I built a somewhat competing service that isn't doing too well and I'm looking to make it so you can install it on your own servers.
It would be valuable for me.
We have a product that relies heavily on Parse. The model is a white labeled solution. We currently have a potential client that wants to host everything and we are kind of stuck with Parse. I could simply charge more if there was a customer hosted solution.
Re: Parse is down due to SSL certificate expiry
#53Hint: the web is one thing, but if you're deploying a library that talks to your own server, consider embedding your own root certificate. In addition to verifying the traffic isn't being proxied[1], you can also issue 10 or 20 year certs and be done. [1] Users can add their own root certs and watch your traffic (typically with the intent of breaking your app), or worse, companies can deploy roots to all their device…
If you have your own cert, wouldn't it be best to ignore expiration (and decide based on risk whether or not to implement revocation)? Unless you are saying to add the cert to the device/computer's list of trusted certs, which doesn't seem necessary to me.
All of Google's pinned certs are certainly evidence that this is a reasonable approach (I haven't looked at their expirations), though now it's kind of weird since it can't be MitM'd even to debug -- no one knows what is being shipped off to Google by Chrome anymore without reverse engineering binaries.
Re: Parse is down due to SSL certificate expiry
#54It costs $100 for a 5 year SSL certificate. Why do seemingly smart internet companies let this happen?
Where the hell are you buying your certs? I'd honestly love to know.
NameCheap resells domain-validated (basically, email the webmaster) Comodo PositiveSSL for $50/5 years.
http://www.namecheap.com/ssl-certificates/comodo/positivessl...
Re: Parse is down due to SSL certificate expiry
#55Hint: the web is one thing, but if you're deploying a library that talks to your own server, consider embedding your own root certificate. In addition to verifying the traffic isn't being proxied[1], you can also issue 10 or 20 year certs and be done. [1] Users can add their own root certs and watch your traffic (typically with the intent of breaking your app), or worse, companies can deploy roots to all their device…
Issuing inordinately long-lived certificates might not be the best security decision. To put it another way, "infinity" is not the appropriate lifetime for a 4096-bit cert.
Re: Parse is down due to SSL certificate expiry
#56They just fixed it. FYI, in case you did not look at the certificate details, the old certificate expired 5AM today.
And I am in the GMT-8 time zone and used Firefox.