Some security researchers from UCSD showed a proof of concept exploit via one of the dongles that appears to be also used by car insurance companies to monitor your driving "to give you discounts for good driving". I'm not really a fully paid up subscriber of the tin foil hat brigade but stuff like this makes me glad that I'm still opting for the old-fashioned way of paying for car insurance. Of course the fact that over half our fleet is too old to be OBD-II compliant may have some bearing on that as well...

Another metablogging post, but this may come in handy for people who like to produce blog posts in bulk and schedule them for publication in WordPress at a later date.

I've recently blogged about adding TLS support to Emacs 24.5 on Windows and improving git performance on Windows by installing an alternative git command line client. The reason I ended up investigating how to add SSL and TLS support to Emacs is that when I originally upgraded from the official git Windows client to the Git for Windows build, I ended up with non-working TLS support in Emacs.

Looks like Samsung and Google recognise that much like any other computing device, the smartphone in your pocket needs very regular security updates.

I've blogged about improving the performance of Git on Windows in the past and rightly labelled the suggested solution as a bad hack because it requires you to manually replace binaries that are part of the installation. For people who tend to use DVCSs from the command line, manually replacing binaries is unlikely to be a big deal but it's clunky and should really be a wakeup call for some people to include a newer base system.

The Windows build of Emacs 24.5 doesn't ship with SSL and TLS support out of the box. Normally that's not that much of a problem until you are trying to access marmalade-repo or have org2blog talk to your own blog via SSL/TLS.