GPG Blues

So there’s a Mac version of GnuPrivacyGuard (aka GPG, which is quicker to type).

Sadly, the current GPGMail plug-in is, out of the box, not compatible with the current version (as of this writing) of the OS, 10.6.2. This is a problem in a society in which the government has decided that it’s OK to monitor communications as a matter of course.

Short tangent:
I feel strongly that my communication with others is strictly between myself and the other party; no third party should have the right or ability to snoop on that; if the State feels that my communications are interesting enough to warrant further investigation, it can fucking man up and get a fucking warrant. Which will be contested. I do not consent to being ruled by sniveling, secretive people who feel that it’s acceptable to pull weird shit behind my back.

I pay these peoples’ salaries and I would remind them of this!

Rant over.

This isn’t going to be a GPG tutorial; there are plenty of other resources for that. But what I’m going to do is document, in brief, the hoops I jumped through to get GPG and GPGMail working.

First off, quit Mail, ensure that your stuff is backed up and that your software is otherwise up to date; then say to yourself in the mirror, “I’m the architect of my own fate; this worked for the blogger at, but I’m not going to be a pansy or a litigous shitbag if it doesn’t work for me; I have backed up my data and I am confident that I can read.”

  1. Ensure that Apple’s Developer Tools are installed on your system, and current. The installer is located in the ‘Optional Installs’ folder on your 10.6 install DVD; double-click the Xcode.mpkg to set yourself up there.
  2. Follow the instructions here in order to download and install GPG from source.
  3. You should then install all the appropriate accessory software from the MacGPG website — this is just a quick writeup, so it’s up to you to figure out what you neet. Caveat Emptor.
  4. So far so good. Now get GPGMail.bundle from here. Drag it into your Mail Bundles folder, the path to which is generally: [~/Library/Mail/Bundles] (create this folder if necessary)
  5. The bundle will not work as-is; it needs to be patched. Follow the instructions here to patch the bundle to be compatible with version 4.2

Voilà! — you should be all patched, hacked and ready to go. If it breaks, it’s because you broke it by following instructions you found on some website about which you know next to nothing.

If this all seems scary, either take courage — you’ll need all the moral fortitude you can get in these ‘interesting’ times — or use a commercial encryption solution.

About lidlesseye

Mouthing off about photography, and occasionally important things too.

Posted on January 16, 2010, in Geekery and tagged , , , . Bookmark the permalink. 1 Comment.

  1. Word!
    Like your post!
    Everybody encrypt NOW! EVERY MAIL!
    (Just make sure the recipient has your public key, otherwise the answer needs some time… *G*)
    Greetz, Skinner08

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: