Back in University some friends and I had joked about creating a “random” sortation algorithm that could be used in place of other fast, efficient and, well, better solutions like Quick Sort or the like. While cleaning up some files on my computer today I came across this monstrosity and decided what better place to put it than up on my GitHub page. So there you have it, now you too can have a sorting algorithm that may never actually succeed in sorting anything at all!

Here are some of my recent posts from over at The Linux Experiment: Cloud software for a Synology NAS and setting up OwnCloud Running a containerized media server with Ubuntu 14.04, Docker, and Plex Applying updates to Docker and the Plex container How to easily forward Firefox (PC & Android) traffic through an SSH tunnel Adding GTK+ 3 support and building CoreGTK using GObject Introspection CoreGTK now supports GTK+ 3 and is built from GObject Introspection Big distributions, little RAM 8 Taking a look at some Linux e-mail clients CoreGTK 3.

The next version of CoreGTK, version 3.10.1, has been tagged for release today. Highlights for this release: Added some missing (varargs) GTK+ functions. This makes it easier to create widgets like the FileChooserDialog. CoreGTK is an Objective-C language binding for the GTK+ widget toolkit. Like other “core” Objective-C libraries, CoreGTK is designed to be a thin wrapper. CoreGTK is free software, licensed under the GNU LGPL. You can find more information about the project here and the release itself here.

The next version of CoreGTK, version 3.10.0, has been tagged for release today. Highlights for this release: Move from GTK+ 2 to GTK+ 3 Prefer the use of glib data types over boxed OpenStep/Cocoa objects (i.e. gint vs NSNumber) Base code generation on GObject Introspection instead of a mix of automated source parsing and manual correction Support for GTK+ 3.10 CoreGTK is an Objective-C language binding for the GTK+ widget toolkit.

It has been quite a while since the first release of CoreGTK back in August 2014 and in that time I’ve received a lot of very good feedback about the project, what people liked and didn’t like, as well as their wishlists for new features. While life has been very busy since then I’ve managed to find a little bit of time here and there to implement many of the changes that people were hoping for.

I’ve finally gotten around to enabling SSL/TLS on this website. For now I’ve simply used a StartSSL free certificate which will expire in one year. I’m still testing things out for now but the goal is to keep the site 100% secure from now on.

If you are worried about your hard drive one day crashing and you losing access to your OpenPGP key (and thus the contents of your encrypted e-mails) then you should have been using a backup! That said an extra archival method of storing your key completely offline would be to use a program called paperkey to export the contents of your OpenPGP key to an easily printed file that you can then re-type into your PC if necessary.

It has been a while since I made any mention of my side project CoreGTK. I’m sure many people can relate that with life generally being very busy it is often hard to find time to work on hobby projects like this. Thankfully while that certainly has slowed the pace of development it hasn’t stopped it outright and now I am just about ready to show off the next update for CoreGTK.

More than a year ago I moved from my expiring OpenPGP key (0x1CD3E3D8) to my current key (0xFEEEFA8F) and for that process, in addition to signing my new key with my old key, I created a Key Transition notice signed by both keys as a way to inform those who trusted my old key that my new key was in fact still me. However it only recently occurred to me that I never actually posted any instructions on how I did that and deciphering gpg command line can be a bit of a pain.

While I am by no means a security expert the following are the current best practices for configuring your gpg.conf file as best as I can determine. Key usage options default-key <your primary key> Use as the default key to sign with. If this option is not used, the default key is the first key found in the secret keyring. hidden-encrypt-to <your primary key> Same as –hidden-recipient but this one is intended for use in the options file and may be used with your own user-id as a hidden “encrypt-to-self”.