Setting up a Springloops Git Repository in Coda 2
The problem we ran into was that Springloops usernames are email addresses, and Coda only asks for your Git URL and password. This means your username needs to be included in the URL.
With a GitHub account, this isn't an issue - the URL will look something like https://github.com/yourusername/reponame.git
After some trial and error we determined that the trick with a username which is an email address is to URL encode it before inserting it into the repo URL.
Take note that with the Springloops URL the order is hostname, colon, URL encoded email address, rest of repo URL. For example:
Springloops Git URL: https://slsapp.com/git/yourspingloopsaccount/reponame.git
Coda URL: https://slsapp.com:youremail%40youremail.com/git/yourspingloopsaccount/reponame.git
OpenSSL Heartbleed Bug
If you are online at all you have heard about the bug in OpenSSL called Heartbleed. For the technical details you can visit OpenSSL's news release. If you are interested in an easier to understand write up, you can visit Heartbleed.com. In a nutshell, this bug in OpenSSL allows your encrypted data to be read.
Rest assured, that our security team had our servers patched within hours of this bug being made public. If we are hosting your domain, you are not at risk.
If we are not hosting your domain, you should ask your hosting provider if you are at risk. There are a bunch of versions of OpenSSL that do not have this bug, so it is possible that older infrastructure is running a version of OpenSSL that is immune.
Again, our hosting services are not at risk and have been updated via backporting. To find out more about backporting, you can check out https://access.redhat.com/site/security/updates/backporting/.