As many of you probably are already well aware, Github recently was made aware of a mass-assignment vulnerability (1). If you aren’t caught up, you can find the info here on the Github blog (2, 3).
This afternoon, Github sent out an email to users that they had disabled all SSH keys for a users’ accounts and they would remain suspended until validated. You can validate your keys by visiting the SSH keys section under your account settings where you will then be able to reject or validate each of your stored keys. These are listed by machine ID and key fingerprint.
But how do you know the fingerprint of your SSH key to ensure it is the correct one for each machine ID? Simply SSH into each machine and run the following, replacing the location of the key to match where you have yours stored:
Keeping track of what branch you are using while in a git repository can be a bit of a pain. Adding the following code to your ~/.bashrc file can make it a bit easier since it will prepend your prompt with the current branch.
Stumpy has been updated to version 1.4.1 to fix a critical bug that was in all previous versions [Thanks, Erik!]. There was an issue with case-sensitivity in short url lookups that is now all patched up.
For general information on the newer v1.4+ Stumpy, see post here.
After endless peer pressure, Mutaku is finally on GitHub. I have to admit, initially I didn’t really see why I would need a version control system, let alone use something like GitHub. But 10 minutes into using, I was sold on both fronts.
So head on over to the Mutaku GitHub page and feel free to follow and subscribe to the activity feed.
I’ve already thrown up one project that I was starting to get together to post here at the site. I will be working on gathering together some of my other projects to post as well with the goal being to have snapshots of all the Mutaku code and projects accessible publicly on GitHub.