Today was “I-hate-certificates” day. Four different people had ugly issues with SSL:
-
Sophie has finished cleaning the underway data in SQLShare and is ready to load it into Myria. However, she had problems using Myria’s Python client because her Mac did not trust Myria’s SSL certificate. (UW’s choice of Certificate Authority (CA), InCommon, has apparently not been blessed by Mac OS X.)
I should note that Sophie identified and fixed a bug in the Myria Python client, which she pushed to us on GitHub. That type of fluency with others’ code, being confident in your own diagnosis of the bug, and having the ability to push bug fixes back to open source projects is a key goal of this whole endeavor!
-
Brendan Lee has been working with the UW Database Group on MyMergerTree. MyMergerTree is powered by Myria, so after I enabled SSL yesterday, I asked him to fix the web service to use HTTPS instead of HTTP links. Well, great, InCommon has not been blessed by Ubuntu either.
-
Two different people came to Incubator office hours to learn about
git
. They brought older laptops with, you guessed it, older versions of Mac OS X installed. And, surprise surprise, GitHub’s current SSL certificate is not blessed by those old versions of Mac OS X, and the only way to fix it is to upgrade the OS. You know, because that’s a totally reasonable option.
Such a waste of time. Why do we make users jump through these hoops? We worked around these issues in a variety of ways, all of which involved disabling certificate verification. Ugh, that’s a fail. (In one case we were able to switch from HTTPS to SSH for GitHub — that, at least, made me moderately less sad at heart.)
I left at lunch for the airport. I’ll be at NYU in Brooklyn for the next week giving talks, making connections, and generally getting to know better our Moore-Sloan DSE collaborators across the country. I spent the entire flight working on slides for the various talks.
Comments !